Fix Minecraft "Failed to Login: Invalid Session"

"Invalid session" means the server asked Mojang/Microsoft to verify your account and the check failed — usually a stale login session. Here's the quick client fix and the server-side cause.

"Invalid session" is almost always a stale login token on the player's side, and it clears in seconds. If it hits every player at once, it's the server's online-mode instead. The fix in order:

1. Fully close Minecraft and the launcher (not just the game window).
2. Reopen the launcher and let it re-authenticate your Microsoft account.
3. Rejoin the server.
4. Still failing? Sign out of your Microsoft account in the launcher and sign back in for a fresh token.
5. If EVERY player fails at once, it's server-side — check online-mode (below).

The instant fix: restart the launcher

Nine times out of ten this is a stale session token. Fully close the Minecraft launcher and the game, reopen the launcher, and let it re-authenticate your Microsoft account. Then rejoin.

Still failing? Re-login your account

Sign out of your Microsoft account in the launcher and sign back in to force a fresh token. This clears a session that expired in the background.

The server side: online-mode

Servers with online-mode=true (the default) verify every player with Mojang. That's correct and secure. If the server runs online-mode=false (offline/cracked), authentication is skipped entirely — which has real downsides:

# server.properties
online-mode=true   # verifies accounts (recommended)

Other quick checks

• Check the Mojang/Minecraft services aren't down.
• If you just changed your username, wait — the change can take time to propagate.
• Make sure your system clock is correct (a wrong clock breaks auth).

"Invalid session" is a stale login. Restart the launcher to re-authenticate — it fixes it almost every time.

Why "Invalid session" keeps coming back

If restarting the launcher only fixes it briefly and the error returns, the usual culprits are a firewall, antivirus or VPN interfering with the launcher's connection to Microsoft's authentication servers, or a proxy that blocks the auth handshake. Test with the VPN/proxy off and add the launcher as an exception in your security software.

"Bad login" vs "Invalid session"

Both point at the same account-verification failure, but "Bad login" more often shows up on older/third-party launchers or when a server can't reach Mojang's session servers at all. On the server side, confirm outbound access to Minecraft's authentication endpoints isn't blocked by a firewall — a locked-down VPS can trigger this for every player at once.

How to prevent login and session errors

• Keep your launcher and game updated so token handling stays current.
• Keep the server's system clock synced with NTP — a drifted clock breaks authentication server-wide.
• Leave online-mode=true and add a whitelist rather than switching to offline mode to "solve" login errors.
• Ensure the server can reach Mojang/Microsoft auth servers outbound if you run a tightly firewalled VPS.

Related Minecraft join errors

If the server rejects your name specifically, see Minecraft failed to verify username. For version mismatches, read outdated server / client. If the connection drops rather than the login failing, see internal exception: timed out and io.netty connection refused.

Minecraft is a trademark of Mojang Synergies AB / Microsoft. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Mojang or Microsoft.