Skip to content
Tickwise
CriticalNetworkSIG-NW-005

No servers available to join the network

Platforms
Velocity · whole network
Verified
Verified
Confidence
Confidence 95%

What it looks like in the log

Any one of these lines is enough. The agent matches them locally, on your server.

logs/latest.log
  • There are no available servers to connect you to

Symptoms

  • Players are disconnected right after joining the proxy: “There are no available servers to connect you to. Try again later or contact an admin.”

Cause

The proxy could not find an initial server for the player: the try list is empty, or none of its servers suits this connection (a forced host with no servers, a balancing/lobby plugin did not pick a server).

Possible causes

  • The try list in velocity.toml is empty or contains only unregistered servers; forced-hosts has no servers for the connection's hostname
  • A balancing/lobby plugin (a PlayerChooseInitialServerEvent handler) did not pick a server — e.g. all backends are marked unavailable for it
  • noteThe text is translatable and can be overridden; the signature only catches the default English text — the primary source is the Velocity agent's API event

How to fixLow risk

  1. Open velocity.toml: under [servers], the try parameter must contain at least one registered server; check [forced-hosts] for the domain players connect through.
  2. Check that the backends listed in try are running and responding (the /server command on the proxy, the status in the Tickwise panel).
  3. If a lobby/balancing plugin is in use, check its config and log: it may have excluded every server.
  4. After editing velocity.toml, run /velocity reload or restart the proxy.

Translated from the Russian original; log lines are quoted verbatim.

Sources