How to Add Backend Servers to Velocity

Direct answer

Register each destination in Velocity’s [servers] section as a name-to-address mapping. Configure secure player forwarding and private network access before opening the proxy to players.

Step-by-step procedure

1. Stop the proxy or take a controlled maintenance window; back up velocity.toml.
2. Add a unique key such as survival = "127.0.0.1:25566" under [servers] when the backend is on the same host.
3. Ensure forwarding mode and the secret match the backend’s supported configuration, and prevent direct public access to that backend port.
4. Start the backend and proxy, then use /server survival with a test account to verify routing.

Common mistakes and trade-offs

For a backend on a different host, replace localhost with a private reachable address; localhost on the proxy points back to the proxy machine.

How to verify it worked

A successful switch should preserve the authenticated player identity. Check both logs if the proxy can connect but the backend rejects forwarding.

Version and platform differences

Velocity config uses TOML, not YAML. Modded or Vanilla backends may need additional forwarding support.

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.

• Velocity getting started
• Velocity configuration

Related guides