Direct answer
Velocity and Paper backends can run on one computer if each process has a distinct port and the backend is not publicly exposed.
Recommended procedure
- Bind Velocity to the public-facing Java TCP port, and choose distinct local addresses/ports for each backend in
server.properties. - Register those endpoints under Velocity
[servers], set a suitabletryorder and configure matching modern forwarding secrets where supported. - Use loopback or firewall rules to restrict backend traffic. Keep proxy/plugin files separated from backend JARs and data folders.
Why this matters
A proxy becomes the public entry point while backend servers should normally trust only that controlled path. Forwarding and network security must be configured together.
Important limitation: Backend offline mode under a proxy is only safe with proper identity forwarding and network restrictions.
How to verify the result
- Join through the proxy, switch between test backends, and confirm players cannot connect directly to backend ports.
Version and compatibility notes
- When a setting, command, or file name differs from this guide, stop and check the documentation for your exact Minecraft/server-software version instead of forcing an old example.
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.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.