Direct answer

A login timeout occurs after connection begins but before the player is fully admitted. Identify whether the stall is authentication, plugin login work, proxy forwarding or server overload.

Identify the failing layer

Increasing timeout settings can mask a blocked database connection or plugin deadlock. Do not expose backend ports to bypass the proxy.

First checks and evidence

  • Record the login stage and timestamp from player, Velocity and backend logs.
  • Check that the proxy can connect to the backend and that authentication/forwarding settings match on both sides.

Admin diagnosis and repair

  1. Inspect login-event plugins for slow database queries or blocked connections during the failed join.
  2. Compare a fresh test account and a returning account; if only one fails, inspect account-specific plugin data before editing the world.

Verify the fix: A successful login should complete repeatedly on the same test path while proxy and backend logs show the expected authenticated identity.

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