Skip to main content

I work on BeeBEEP about 20 hours a week, and it is free for you. Support it

Quick start for administrators

Setting BeeBEEP up for an office: install it, open the firewall, set a policy and connect what BeeBEEP does not find by itself.

For: administrators · From BeeBEEP 6.0.0 · Updated on

This page is for whoever sets BeeBEEP up for an office. It goes through the steps in the order they are usually taken; each one leads to the page that says it in full. On a network where every computer sees the others, the first two steps are often all it takes.

Install it

On Windows, the setup program installs BeeBEEP for every account and writes the firewall rule by itself; the MSI package and a silent installation are there for a deployment to many computers (installing on Windows). On Linux, a .deb package, an AppImage and an archive are ready (installing on Linux).

If BeeBEEP 5.x is still installed, the Windows installer asks whether to remove it or keep both (BeeBEEP 5.x on the same computer); on Linux the package replaces BeeBEEP 5.x's as an upgrade, its data left as it was (BeeBEEP 5.x on the same computer).

Let it through the network

BeeBEEP needs one TCP port and two UDP ports, by default the same on every computer (which ports). Where the firewall is not the computer's own, or the office is joined by a VPN, let them through there too (what the network must let through).

Set a policy

The policy file, beebeep.rc, is read from one fixed place that only an administrator can write. With it you can:

  • put every account's data in a folder of your choice;
  • turn plugins, voice calls or a kind of plugin off;
  • keep BeeBEEP to a list of computers, or a search inside your own network;
  • give each team its circles;
  • set how long a sent message can be edited or deleted.

The policy file says where it is and how each of these is written.

When there is no policy file, no policy applies and every user chooses.

Choose a network password

A network password keeps apart the BeeBEEP users who do not share it: a device with another password does not find yours. It is off by default. To use one, every person turns on Use network password in Settings > Network and types the same password (network password).

Connect what BeeBEEP does not find

BeeBEEP finds the computers of its own network by itself. For another office, another subnet or a VPN, list the computers or the networks to contact in beehosts.ini, beside the policy file (connect a whole group). A Wi-Fi that keeps its devices apart has a page of its own (Wi-Fi with client isolation).

A computer with no desktop session

A server or a computer nobody logs into has no store for BeeBEEP's secrets; give it a master secret with --secret-file (where the secrets are kept).

Versions and size

Every version of BeeBEEP from 6.0 on works with every other, in both directions: users, groups, messages and files pass between any two, so the computers of an office need not be updated on the same day. Fixes go into the latest version only; updating is free and never cuts a computer off from one still on an older version.

BeeBEEP has been tried with up to 300 computers on the same network; if yours has more, tell us how it goes.

BeeBEEP 5.x users in the office

BeeBEEP talks to BeeBEEP 5.8.6 and 5.9.2, so people can move one at a time; Network/LegacyBridgeEnabled turns it off (network). On a computer, each person brings their contacts and chats over with the import (coming from BeeBEEP 5.x).

All the help pages