Configure Velocity as a proxy Minecraft

Configure Velocity as a multi-server proxy Minecraft

Velocity is a modern proxy to connect several Minecraft servers (lobby, survival, minigames) behind a single IP address. More efficient and secure than BungeeCord Legacy, it is suitable for networks hosted at Anthony IT Solutions with several Minecraft instances.

Difference with the BungeeCord guide: Velocity uses modern forwarding (Player Info Forwarding) and async architecture optimized for Paper 1.13+.

Prerequisite

• At least 2 Minecraft servers (1 proxy + 1 backend, ideally 3+)
• Egg Velocity or installation jar proxy on dedicated instance
• Same ecosystem: Paper recommended in backend
• Open ports : 25565 (public proxy), backend internal ports (25566, 25567...)

Step 1: Prepare the Velocity proxy

1. Order an instance with egg Velocity or Bungeecord according to panel
2. Note the public port of the proxy (e.g. 25565)
3. Generate a forwarding key: file forwarding.secret (long random chain)
4. Configure velocity.toml :
   • bind = "0.0.0.0:25565"
   • online-mode = true (Mojang premium mode)
   • player-info-forwarding-mode = "modern"
   • forwarding-secret-file = "forwarding.secret"

Step 2: Report Backend Servers

In velocity.tomlSection [servers] :

lobby = "127.0.0.1:25566"
survie = "127.0.0.1:25567"
minigames = "127.0.0.1:25568"
try = ["lobby"]

If backends are on other machines, replace 127.0.0.1 by the internal or public IP of each server.

Step 3: Configure Paper (backend)

On each server backend Paper:

1. Edit config/paper-global.yml (or paper.yml according to version)
2. Section proxies :
   • velocity.enabled: true
   • velocity.online-mode: true
   • velocity.secret: "MÊME_SECRET_QUE_forwarding.secret"
3. settings.bungeecord: false, do not mix BungeeCord and Velocity
4. Restart each backend

Step 4: Proxy plugins (lobby)

• MiniMessage / Adventure, modern messages
• LuckPerms Velocity, global network permissions
• MinimoTD or equivalent, MOTD and favicon
• Server switcher, NPC or GUI for /server survie

Controls and switch

• /server <nom>, toggle backend defined in velocity.toml
• /glist, players list (plugin Velocity or Paper)
• Maintenance: Remove a backend from the try list or use a maintenance plugin

Security forwarding

• Firewall: allow 25565 public, backend internal IP or whitelist
• Without correct forwarding, UUID/skin can be spoofed

Network performance

• Light Proxy: 512 MB-1 GB RAM is enough
• Allocate RAM to backends depending on load, TPS optimization
• Colocate proxy + backends even datacenter (Equinix PA5) for minimum latency

Troubleshooting

• "Unable to connect to server", backend offline or bad port in velocity.toml
• UUID different between servers, forwarding wrongly configured, different secret
• « If you wish to use IP forwarding... », velocity.enabled missing on Paper
• Login circle, try list points to down server

Frequently Asked Questions

Velocity or BungeeCord ?
Velocity is recommended for new Paper 1.13+ projects. See also BungeeCord/Velocity.

Is only one server sufficient?
No, a proxy requires at least one additional backend.

Related guides

• BungeeCord/Velocity network
• Multiverse multi-world
• Ports & firewall

Hosting Minecraft · Wiki games