Direct answer

This error happens after the connection reaches the login/authentication stage. First fully close Minecraft and the launcher, sign back into the official account session, and try again. If every player suddenly fails, check whether the server can reach Minecraft’s authentication services and whether a proxy is configured correctly.

If one player is affected

  • Close every Minecraft/launcher instance using that account.
  • Sign out and back in, then launch the correct account again.
  • Confirm the client is using a valid account and a normal authenticated session.
  • Try another known-good server; if authentication fails everywhere, this is not specific to your server.

If everyone is affected

A server with online-mode=true must reach Minecraft account/session services to verify joining players. Check server DNS, outbound HTTPS access, host firewall rules, and current service status before changing Minecraft configuration.

Do not “fix” it by turning online-mode off

Targeted diagnosis: Find out whether this is an authentication/session outage, a proxy forwarding mismatch or a local offline-mode setting. Check the exact server log at the failed login time; a single generic “auth failed” explanation is not enough.

Keep normal internet-facing servers authenticated.

Setting online-mode=false disables the normal identity check and changes how player identities are handled. That can enable username impersonation and break UUID-based data. The important exception is a correctly secured proxy backend, where the proxy performs authentication and forwards identity using the proxy’s documented forwarding mode.

Fix and verify: For a proxy network, verify the public proxy performs account authentication while backends use the documented forwarding settings and are firewalled. Do not toggle a public server to online-mode=false merely to bypass an authentication error.

Velocity networks are different

With Velocity modern forwarding, the proxy normally authenticates players while Paper backend servers use online-mode=false and validate the Velocity forwarding secret. Follow the Velocity documentation exactly; do not expose backend ports directly to the internet.

Official references

These references were checked while preparing this fix. Version-specific behavior can change, so use the project documentation for your exact release when a detail differs.

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