Fix Minecraft "Failed to Verify Username"

  • Failed to verify username
  • authentication servers are down
  • bad login
  • 6 min read
  • Updated 7 October 2026
  • ESAGAMES Team

"Failed to verify username" is a server-side message: the server tried to verify a player with Mojang/Microsoft auth and couldn't. Here's why and how to fix it, including the clock-skew cause admins often miss.

Quick answer

"Failed to verify username" means the server could not check a player with Mojang/Microsoft authentication. It is usually a temporary auth outage, a player on a cracked (offline) account joining an online-mode server, or a backend behind BungeeCord/Velocity that is not set up for player forwarding. A wrong system clock on the server can cause it too.

Cause 1: Mojang auth is temporarily down

With online-mode=true, the server checks each player against Mojang's auth servers. If those are down or flaky, verification fails. Check the Minecraft service status — if it's an outage, just wait it out.

Cause 2: players using "cracked"/offline accounts

An online-mode server rejects non-premium (cracked) accounts — that's the point of online-mode. Players must use legitimate accounts, or the server must run offline (not recommended).

Cause 3: behind a proxy without forwarding

If your backend server sits behind a proxy (BungeeCord/Velocity), the backend should be online-mode=false and rely on the proxy's IP/player forwarding. A misconfigured proxy setup causes verify failures.

Don't just disable online-mode

Setting online-mode=false to "fix" this on a standalone server removes all account security — anyone can join as anyone. Only do it for offline play, and always with a whitelist or a proxy that handles auth.

It's an auth check. Wait out Mojang outages, require legit accounts, and on a proxy network set the backend to offline with proper forwarding.

Cause 4: server clock is wrong

Mojang/Microsoft auth tokens are time-sensitive. If the server's system clock has drifted, session validation can fail even with a correct account and a working internet connection. Check the time with timedatectl status and enable NTP sync with timedatectl set-ntp true if it's off.

Cause 5: outbound access to Mojang's servers is blocked

A restrictive host or corporate firewall that blocks outbound HTTPS to Mojang/Microsoft's session servers will cause every join to fail verification, even though the server itself is healthy. Confirm outbound HTTPS isn't filtered.

Server settings like online-mode are quick to change from a web panel. Our Minecraft hosting in Frankfurt includes a file manager for server.properties and one-click restarts.

If players can't even reach the server before this point, see fixing "Connection refused: no further information". For a new server setup with online-mode configured correctly from the start, see how to make a Minecraft server.

Frequently asked questions

Why does my server say "Failed to verify username"?

With online-mode on, the server verifies players against Mojang's auth servers. The error means that check failed — usually a Mojang outage, a non-premium account, or a misconfigured proxy.

Is "failed to verify username" the player's fault?

Not necessarily. It can be a temporary Mojang auth outage, a cracked account on an online-mode server, or a proxy/forwarding misconfiguration on the server side.

Should I set online-mode=false to fix it?

Only on a proxy backend with proper player forwarding, or for deliberate offline play with a whitelist. On a normal public server, online-mode=false removes account security and invites impersonation.

Can a wrong server clock really cause this?

Yes — Mojang/Microsoft session tokens are time-sensitive, and clock drift on the server can make valid sessions fail verification. Sync the server's clock with NTP if this happens intermittently with no other clear cause.

How do I know if it's a Mojang outage and not my server?

Check Mojang/Microsoft's official service status, and see if other online-mode servers are also affected. If it's widespread, it's an outage — just wait; there's nothing to fix on your end.

Does a firewall on my server host cause this error?

It can, if outbound connections to Mojang's authentication servers are blocked. The server needs outbound HTTPS access to verify sessions — a restrictive firewall can silently break every login.

Go deeper on this

Guides and explainers that pair with this fix — from our guides and blog.

Related articles

Skip the troubleshooting

Managed, protected hosting in Frankfurt — we handle the Linux, the network and the DDoS so you don't have to.