NewSchokr 13 is here. A whole new UI, seven locations, snapshots and more. Read more →

Fix "If you wish to use IP forwarding" BungeeCord error

Fix the BungeeCord IP forwarding kick message and related errors by matching ip_forward on the proxy with bungeecord: true on each Paper backend.

Updated · 2 min read

The message "If you wish to use IP forwarding, please enable it in your BungeeCord config as well!" means your Paper backend expects forwarded player data, but the proxy is not sending it. Turn on ip_forward in the proxy's config.yml and restart the proxy.

Why it happens

In a BungeeCord network, the proxy authenticates players and forwards their real IP and UUID to the backend servers. Two settings must agree:

WhereSettingValue
Proxy config.ymlip_forwardtrue
Each backend spigot.ymlsettings.bungeecordtrue
Each backend server.propertiesonline-modefalse
Proxy config.ymlonline_modetrue

If the backend has bungeecord: true but the proxy has ip_forward: false, the backend rejects the player with the IP forwarding message.

Fix

  1. Stop the BungeeCord server.
  2. Open its config.yml in the file manager.
  3. Set:
ip_forward: true
  1. Save and start the proxy.
  2. Reconnect through the proxy's address.

Connecting directly to a backend

If you join a backend's own address instead of the proxy, you also get the IP forwarding message, because no proxy forwarded your data. Always connect through the proxy. This is also why you should protect backends with a plugin like BungeeGuard so direct connections are blocked.

"You are not logged in" or skins missing

If players end up with default skins or new UUIDs, forwarding is off on one side. Check both ip_forward on the proxy and bungeecord: true on every backend.

Players are disconnected as soon as the proxy sends them to a backend

The backend most likely still has online-mode=true. Set it to false in that backend's server.properties and restart it. The proxy handles authentication, so the backend must not try to do it again.

"Failed to verify username"

This is an authentication problem between the player and the proxy, usually an invalid or expired launcher session. Ask the player to restart their launcher and log in again. Keep online_mode: true on the proxy.

Checklist after changes

  1. Proxy: ip_forward: true, online_mode: true.
  2. Each backend: bungeecord: true in spigot.yml, online-mode=false in server.properties.
  3. Restart all backends, then the proxy.
  4. Connect only via the proxy.