How to Fix “Your Server Did Not Send a Forwarding Request to the Proxy”

Direct answer

Velocity documents this exact message as an improper player-forwarding configuration. Make the proxy and backend use the same forwarding method and settings; for Paper modern forwarding, the backend secret and online-mode values must match Velocity.

What it means

Align Velocity and backend forwarding settings when the proxy cannot complete player information forwarding.

If you are a player

Copy the exact connection/kick message and note the timestamp; similar-looking login errors can have different causes.
Check the address, port, Minecraft version, and whether other players can connect at the same time.
Tell the owner whether the problem follows your account/device/network or affects everyone.

If you run the server

Choose one forwarding mode and configure the proxy and backend for the same mode.
For Paper modern forwarding, set Velocity player-info-forwarding-mode = "modern".
On the Paper backend, set online-mode=false in server.properties, disable legacy Bungee forwarding, enable proxies.velocity.enabled, match the forwarding secret, and make proxies.velocity.online-mode match Velocity.
Restart both sides and connect through Velocity, not the backend address.

References

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

Focused diagnostic check: Check that the backend is configured for Velocity modern forwarding, that the proxy is using the same forwarding secret and that the backend is reached only through the proxy. Modern forwarding still requires backend network protection; opening an offline-mode backend publicly to “fix” login errors creates an impersonation risk.

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.