Direct answer

This message means a backend expects legacy BungeeCord IP forwarding but is not receiving it in the expected way. Check the proxy–backend forwarding configuration rather than changing DNS.

What it means

Legacy BungeeCord forwarding passes player information from the proxy to Bukkit-compatible backends. Velocity modern forwarding is a different mechanism and must not be mixed with legacy settings blindly.

If you are a player

  • Connect through the advertised proxy address rather than the backend address.
  • Tell staff whether the problem affects all players or only a specific entry point.

If you run the server

  1. Confirm whether the running proxy is BungeeCord/Waterfall or Velocity and select that project’s documented forwarding mode.
  2. For a legacy BungeeCord configuration, inspect proxy ip_forward and the backend forwarding setting applicable to the exact backend release.
  3. If using Velocity modern forwarding, use Velocity/Paper modern forwarding instructions instead of enabling legacy Bungee settings.
  4. Restrict backend listeners with firewall/private networking so players cannot bypass the proxy.

Confirm the fix: Reconnect only through the proxy and verify player UUID, skin and permissions. Never treat forwarding as a replacement for backend network isolation.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000