Monitoring a BungeeCord or Velocity network

clan.me works the same way on a BungeeCord or Velocity network as it does on a single server, one plugin, one dashboard. The difference is that your network's backends, lobby, survival, minigames, whatever you run, roll up into a single public page and a single dashboard, while alerts still tell you exactly which backend needs attention.

How it works

A network is the server you already added through the dashboard, the root, plus one or more backends you add underneath it. The root keeps heartbeating as its own node (typically your lobby or hub), and each backend heartbeats independently with its own plugin install. clan.me combines all of them into one network view: one public page, one dashboard, one set of alert settings.

This is one level deep. A backend can't itself have backends, so BungeeCord-behind-BungeeCord setups aren't something clan.me needs to model.

Adding backends

From your root server's dashboard, go to Settings → Network and add a name for each backend, survival, creative, skyblock, whatever makes sense for your setup. clan.me generates a plugin token for it immediately. Install the plugin on that backend the same way you did on the root, and paste in its own token.

Backends aren't created from the add-server wizard, since they usually have no public hostname of their own, the proxy is the only thing players connect to directly. The Network section is the only place backends get created.

Tokens

Each backend gets its own plugin token, generated from a shared secret unique to your network. The token itself tells you which backend it belongs to, for example a token ending in -survival is the survival backend's. If one backend's token ever leaks, use Rotate shared token on the Network settings page to regenerate the secret and every derived token in one action. You'll need to re-copy each backend's new token into its config.yml, but the leaked token stops authenticating the moment you rotate.

Your public page

Backends are always private. They never appear in the directory and never get a public page of their own. Instead, your network's public page, the root server's page, shows an aggregate: online if any backend is up, total players summed across every backend, and a Network Backends card listing each one with its own status dot and player count. Your analytics dashboard gets the same treatment, plus a dedicated Network panel comparing TPS, MSPT, and memory across every backend side by side.

Alerts across backends

Alert settings, thresholds, delivery channels, webhook URL, maintenance window, all live on the root and apply to the whole network. A backend has no settings of its own to configure.

When something goes wrong on one backend, the alert still names it, for example “TPS drop on survival”, so you know exactly where to look. But if a whole-box event trips the same alert on several backends at once, say a restart or a host-wide lag spike, clan.me sends one alert for the network per cooldown window, not one per backend. In-game alerts still reach every backend that's currently connected, so players and staff on any backend see the notice.

Proxy detection

Backends behind BungeeCord or Velocity almost always run with online-mode: false, since the proxy handles authentication instead. The plugin detects this automatically, by reading spigot.yml for BungeeCord or paper-global.yml for Velocity, and reports it to clan.me. Your Configuration tab shows “Via proxy” instead of flagging the server as running in cracked mode, so a correctly configured network backend never looks like a security problem.

This detection is independent of the network feature itself, a standalone server sitting behind a proxy for other reasons gets the same treatment.

For the general setup flow, see Connect your server. For everything the plugin supports across server software, see Supported server software. For proxy-specific setup notes, see the BungeeCord or Velocity integration pages.