Managed infrastructure for SMBs
Proxy and Lobby Layout for Game Networks: Keep Backend Servers Private
The short answer
A multi-server game network works best when players connect to one front door and everything behind it stays private. Put a proxy such as Velocity or BungeeCord on the public address, send new players to a lobby or hub server, and keep every backend server (survival, minigames, events) reachable only from the proxy. Use the proxy's secure forwarding so backends trust only the proxy, lock the backend ports with a firewall, and plan for monitoring, backups and DDoS protection on the one address players actually see. This guide walks through the layout, the settings that matter and a checklist for your next network change.
1. What the proxy and the lobby each do
The proxy is the only part of the network players connect to directly. It accepts the connection, handles login and moves players between servers without making them reconnect. The lobby (or hub) is the first real game server they land on: a light, fast world with server selectors, rules, announcements and a safe place to wait. Behind them sit the backend servers that hold your actual game modes. Keeping these roles separate means you can restart a minigame server, update a plugin or move a backend to new hardware without players ever seeing a different address.
2. A simple layout that scales
Most networks start with three layers: one proxy on a public address, one or two lobby servers, and a backend server for each game mode. As the network grows you add more lobbies so a single crash does not strand everyone, and you split busy game modes onto their own machines. The proxy stays small and stable; it does not need much CPU, but it does need a reliable network connection, because every player's traffic passes through it. Treat it as the most important server in the network, even though it runs no game.
3. Keep backend servers private
This is the rule that protects the whole network. Backend servers behind a proxy usually run with their own login check turned off, because the proxy has already verified each player. That is safe only when nobody can reach a backend except the proxy. If a backend port is open to the internet, someone can connect to it directly, claim to be any player, including staff, and bypass every protection on the proxy. Bind backends to a private network or to the local machine where possible, and close their ports to the public internet in every case.
4. Use secure player forwarding
The proxy needs to pass each player's real identity and address to the backend. With Velocity, use modern forwarding: the proxy and each backend share a secret, and the backend accepts forwarded players only when the secret matches. Keep that secret file private and change it if it ever leaks. Older BungeeCord style forwarding does not check a secret on its own, so if you run BungeeCord or a fork, add a token plugin that does, and rely even more heavily on the firewall. Whatever you run, confirm that a direct connection to a backend is refused before you open the network to players.
5. Firewall rules that match the layout
Write the firewall from the layout, not the other way round. The proxy's game port is open to the world. Each backend's game port is open only to the proxy's address. Admin panels, databases, remote console and SSH are open only to your staff network or a VPN, never to everyone. Review the rules after every new server is added, because the most common mistake is a fresh backend launched with default settings and a port left wide open. A quick port check from outside the network after each change catches this in seconds.
6. Plan the lobby for crowds and failures
The lobby takes the full rush when you launch an update, run an event or recover from a restart. Keep it light: few plugins, a small pre-generated world and no heavy farms or redstone. Run at least two lobbies when you can and let the proxy spread players across them, so a crash in one sends players to the other instead of kicking them off the network. Set a fallback on the proxy so players on a backend that goes down are moved to a lobby rather than disconnected.
7. Protect the one address players see
Because every player connects through the proxy, its address is the one attackers aim at. Host the proxy on a network with DDoS filtering suited to game traffic, keep backend addresses out of public DNS records and server lists, and avoid leaking them in plugin messages, error screens or old records. If the proxy's address is attacked, filtering at the network edge keeps players connected, and backends hidden behind it are left alone. Some networks also run a second proxy in another location for players in other regions.
8. Shared data, permissions and chat
A network feels like one place when ranks, bans, friends and chat follow players between servers. That usually means a shared database or a messaging service that the proxy and backends all use. Keep it on the private side with the backends, give each server its own database login with only the access it needs, and back it up on its own schedule. Losing this data is often worse than losing a single game world, because it holds purchases, punishments and staff permissions.
9. Monitoring, backups and updates
Monitor each layer separately: the proxy for connection counts and errors, lobbies for tick rate and player counts, backends for performance and crashes, and the shared database for health and disk space. Back up worlds, configuration and the shared database off the server, and test a restore before you need one. Update the proxy and backends in a planned window, keep the proxy and backend versions compatible, and change one layer at a time so you know which change caused a problem.
Network layout checklist
- Players connect only to the proxy's public address.
- At least one lobby, ideally two, with a fallback set on the proxy.
- Every backend port is closed to the public internet and open only to the proxy.
- Secure forwarding is on: Velocity modern forwarding with a private secret, or a token plugin for BungeeCord style proxies.
- A direct connection to each backend has been tested and refused.
- Admin panels, databases, remote console and SSH are reachable only by staff or over a VPN.
- The proxy sits behind DDoS filtering and backend addresses are not published anywhere.
- The shared database uses separate logins per server and is backed up off the server.
- Each layer is monitored, and restores and updates have been rehearsed.
Next steps
GlassHosting is a managed service and infrastructure provider: we run your servers on our own network, so you can run your business. For commercial game networks that means the proxy, lobbies, backends and the private links between them laid out with you, with firewall rules, monitoring and backups handled alongside. If you are running a community server instead, Glass Gaming, powered by GlassHosting, has supported games ready to go. Related reading: dedicated server vs VPS for a commercial game network and running a store next to your game servers. See plans.
Host with GlassHosting
Order a plan or browse the knowledgebase for deeper how-tos.