Direct answer

A Velocity proxy can connect to Paper backends on different machines. Unlike same-host setups, backends must bind to a reachable private interface, but should not be publicly accessible.

Step-by-step procedure

  1. Put proxy and backend hosts on the same private VLAN/VPN where possible, and record each backend’s private IP and game port.
  2. In velocity.toml, add backend entries under [servers] using addresses that the proxy host can reach.
  3. Configure compatible forwarding on both sides, using the same protected shared secret where Modern Forwarding is supported.
  4. Firewall backend ports so only the intended proxy host can connect; test the proxy route before admitting players.

Common mistakes and trade-offs

Binding remote backends to 127.0.0.1 makes them unreachable from a proxy on another host. Making them public to “fix” that defeats network isolation.

How to verify it worked

From the proxy host, verify TCP reachability to each backend; then join via Velocity and confirm player UUID/skin and server switching work.

Version and platform differences

Vanilla, Fabric, Paper and modded backends have different forwarding support; check the exact software before selecting a forwarding mode.

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.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000