How to Configure Velocity Server Order and try

Direct answer

The try list in velocity.toml defines which backend names Velocity tries when a player logs in or needs a fallback. It does not start those backend processes.

Step-by-step procedure

Declare each destination first in [servers], such as lobby = "127.0.0.1:25566".
Set try = ["lobby", "survival"] using declared names and a meaningful fallback order.
Start and verify both backends separately; confirm that the lobby accepts forwarded player information.
Test login when both are healthy, then deliberately stop the primary in staging and observe fallback behavior.

Common mistakes and trade-offs

A try entry pointing to an offline server can delay login or generate failed connection messages. It is not a health check or load balancer.

How to verify it worked

Inspect the proxy log for connection attempts and verify the actual backend chosen in each test case.

Version and platform differences

Forced hosts can provide hostname-specific ordering; test that behavior separately from the general try list.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.