Fix 'Failed to Verify Username' in Minecraft

Why This Error Happens

The failed to verify username minecraft error appears when the server cannot confirm your identity with Mojang's session servers. Every time you join an online-mode=true server, the server contacts sessionserver.mojang.com to verify that your account token matches your username. If that verification fails, you get kicked.

Cause 1: Mojang Session Servers Are Down

Mojang's authentication servers occasionally go down or experience slowness. Check status.mojang.com (or third-party status sites) to see if there is an ongoing outage. If the session servers are down, every online-mode=true server in the world is affected, just wait it out.

Cause 2: You Joined Too Quickly After a Disconnect

If you disconnect and immediately try to rejoin, your old session token may still be active on Mojang's side while the new login attempt generates a fresh one. The mismatch causes the failed to verify username minecraft error. Fix: wait 30 seconds before reconnecting, or fully restart your Minecraft client.

Cause 3: VPN or Proxy Interference

Some VPNs cause authentication issues because your client authenticates from one IP but connects to the server from another. Mojang's session server ties the token to the IP that requested it. Disable your VPN and try again. If you must use a VPN, ensure it was active before you launched Minecraft so the token is issued for the VPN IP.

Cause 4: Server-Side online-mode Misconfiguration

If you are a server admin and you have a proxy setup (BungeeCord / Velocity), make sure:

• The proxy has online-mode=true (it handles authentication).
• Each backend server has online-mode=false (it trusts the proxy).
• In spigot.yml, set bungeecord: true if using BungeeCord, or configure the Velocity secret in paper-global.yml under proxies.velocity.

If a backend server has online-mode=true while sitting behind a proxy, it will try to verify usernames itself and fail because the connection comes from the proxy, not the player's real IP.

Cause 5: Corrupted Launcher Profile

Occasionally your Minecraft launcher's authentication token becomes stale. Log out of the launcher completely, close it, then log back in. This forces a fresh token from Mojang's auth servers.

For Server Admins: Diagnosing the Issue

1. Check your server logs for the exact error message, it will indicate whether the issue is a timeout contacting Mojang or a token mismatch.
2. Test with curl https://sessionserver.mojang.com from the server machine. If it times out, the server cannot reach Mojang.
3. If your server is behind a firewall, ensure outbound HTTPS (port 443) is allowed.
4. Check your server.properties to confirm online-mode is set as intended.

Need reliable hosting that handles these issues out of the box? Astroworld Hosting runs optimised Paper servers on NVMe SSDs with 24/7 support.