Skip to main content
Two settings. Everything else comes from the proxy.
address is where this backend reaches the hub. Usually the proxy’s internal address, and it does not have to be one players can reach. If the proxy sets http.api_address, point this at that port instead. secret is copied from the proxy’s config.yml. Get it wrong and the log says Hub rejected the request: wrong hub.secret in config.yml. server_name is this backend’s name in your proxy’s server list. Left on auto the proxy tells it on the first player join and it is remembered.
On its very first start with auto a backend does not know its own name yet, so it pulls nothing and warns. It catches up on the first player join. Set the name by hand if you need the first boot to be complete.
Nexo’s Pack.server.type has to be HUB, and the bridge writes that for you on first start. It writes it once, so setting it back by hand takes this backend out of the network and the bridge leaves it alone from then on.

​
Overriding the hub on one backend

Any setting from the proxy can be written here too, and then this backend uses your value instead.
Handy while testing something on one server. Worth remembering you did it, because a change on the proxy will not reach a key you have set here. The backend lists them at startup:
A key only counts as yours once you change it. Upgrading adds new keys to your file at their defaults, and those are not treated as your opinion. Delete a line to hand it back.

​
Files the bridge writes

That is all a backend keeps, which is why retiring a server just means stopping it. The settings are remembered so a backend that boots while the proxy is down keeps behaving the way the network told it to.
The bridge runs on Folia as well as Paper with nothing extra to configure. Folia trails Paper by a release or two, so its Minecraft version is not always the newest one Nexo builds for. That is fine as long as your backends agree, and /nexohub status tells you if they do not.