How to Set Up RedisBungee for Multi-Proxy Networks

When You Need RedisBungee

A single BungeeCord or Velocity proxy can handle several hundred players, but large networks eventually need multiple proxy instances behind a load balancer. The problem is that each proxy only knows about its own players. Without synchronization, /list shows partial counts, friend plugins break, and cross-proxy messaging fails. RedisBungee multi proxy minecraft networks use solves this by storing player sessions in Redis, giving every proxy a shared view of the entire network.

Prerequisites

• Two or more BungeeCord, Waterfall, or Velocity proxy instances
• A Redis server (version 6.0 or newer recommended)
• A TCP load balancer pointing at your proxy instances (HAProxy, Nginx, or a cloud provider's LB)

If you have not set up Redis yet, follow our Redis for Minecraft guide first.

Installing RedisBungee

We recommend using RedisBungee-Reloaded (the actively maintained fork) for both BungeeCord and Velocity. Download the correct build for your proxy type and place it in the plugins folder of every proxy instance. Restart each proxy.

Configuration

Open plugins/RedisBungee/config.yml on each proxy. The critical settings are:

redis-server: "redis.internal.example.com"
redis-port: 6379
redis-password: "your-redis-password"
server-id: "proxy-1"

Each proxy must have a unique server-id. Use proxy-1, proxy-2, and so on. All other settings should match across proxies so that the redisbungee multi proxy minecraft setup stays consistent.

Shared Server List

Every proxy in your redisbungee multi proxy minecraft cluster must list the same backend servers. If proxy-1 knows about lobby and survival but proxy-2 only knows about lobby, players transferred to survival from proxy-2 will get disconnected.

Load Balancing

Your load balancer should distribute new connections across proxies using round-robin or least-connections. For TCP-based Minecraft traffic, configure the LB to forward raw TCP on port 25565 to each proxy's port. If you use HAProxy, see our HAProxy guide for a Minecraft-specific config.

Verifying the Setup

1. Join the network through the load balancer from two different accounts.
2. Run /glist on both proxies. Both should show the total player count across all proxies.
3. Send a cross-proxy message if you have a messaging plugin. The message should arrive regardless of which proxy the recipient is on.

Common Pitfalls

• Redis latency: If Redis is hosted far from your proxies, player data updates lag. Keep Redis in the same datacenter or use a low-latency managed Redis service.
• Duplicate server-id: Two proxies with the same server-id will overwrite each other's player data. Double-check every config.
• Firewall blocking Redis: Redis listens on port 6379 by default. Make sure your proxies can reach it, but do not expose Redis to the public internet.

For player data synchronization on the backend side, read syncing player data across servers. A redisbungee multi proxy minecraft architecture scales well into the thousands of concurrent players when combined with proper backend design.

Need a proxy-ready network? Astroworld Hosting supports Velocity, BungeeCord, and multi-server setups on every plan.