Why You See \"Failed to Verify Username\" on a Minecraft Server

When a server kicks you with "Failed to verify username!", it means the server runs in online mode and asked Mojang/Microsoft to confirm your account the moment you connected — and that check came back empty, so it dropped you. Almost every time, this is a temporary login glitch on your end, not a broken account or a broken server. The usual fix takes about thirty seconds: fully close the launcher and sign back in to refresh your login session. The rest of this is the short list of other things to check when that alone doesn't do it.

This is a Java Edition message, and it shows up right as you connect, during the login handshake. It's written for the player getting kicked, not the owner setting up the server. If you're hitting other connection errors too, how to join a Minecraft server is the companion piece for those.

What "Failed to verify username" actually means

Standard public servers — including every server in our rankings — run in online mode. The moment you connect, the server asks Mojang/Microsoft a simple question: is this a real, signed-in account, and does this username belong to it? That question is online mode, and it's on by default.

Here's how the kick happens. When you signed in at the launcher, you got a short-lived login token. Your client hands that token to the server, and the server passes it along to the auth servers to confirm it. If the auth servers can't confirm it — usually because the token's gone stale or the account got signed out — the server gets back "not verified" and drops you with this exact message. An auth outage or no real account behind the connection lands you here too, and both get their own section below.

Despite the word "username," this isn't a "your name is wrong" problem. It's a session and authentication problem, so you don't need to change your name. You might see close cousins like "Invalid session" or "Invalid token" instead, and those are the same family with the same fixes. The one ownership fact worth stating: owning a genuine, paid Minecraft account signed in through Microsoft is what lets you pass this check at all, which do you need to buy Minecraft to play on servers covers in full.

One thing to rule out so you know you're on the right page: this isn't a version mismatch ("Outdated client!" or "Outdated server!"), and it isn't a typo'd address or an offline server. Those throw different messages and live in the join guide.

The quick fix first: sign out and back in

Re-logging works because it forces the launcher to fetch a fresh login token, which replaces a stale or expired one — and a stale token is the single most common cause of this kick.

In the official Minecraft Launcher, quit the game and the launcher fully, not just the game window. Reopen the launcher. If it doesn't keep you signed in, sign back in with your Microsoft account. Then relaunch and reconnect.

What usually triggers a stale token is a launcher left open through a long session, or signing into your account on another device or launcher, either of which can quietly invalidate the token you're still holding. Re-logging clears that out. If reconnecting works now, you're done. If it still kicks you, the cause is one of the next three sections: an auth outage, your clock, or the account itself.

Check whether it's an auth-server outage (not you)

If re-logging didn't help and you're seeing other people report the same thing, the Microsoft/Mojang authentication service may just be down. When it's down, no online-mode server can verify anyone, so this isn't about your account.

To check without guessing, look at the official Mojang/Minecraft status channels — the Mojang status page and the @MojangStatus account — plus a quick scan of community reports. If auth is having trouble, it'll show up there. A good symptom tell is that an outage hits multiple servers at once and clears on its own, so trying a second known-good server from our list is a fast way to tell "it's the auth servers" apart from "it's this one server."

There's nothing to do on your end during an outage except wait, then re-log once it's resolved. Don't reinstall or start changing settings to chase a problem that isn't on your machine.

Fix a wrong system clock

The secure handshake that verifies your login leans on your computer's date and time being roughly correct. If your clock has drifted — wrong time, wrong date, or wrong time zone — the security certificates involved look expired or not-yet-valid, and verification fails even though your account is perfectly fine.

The fix is to set your date, time, and time zone to update automatically. On Windows, that's the Date & time settings, where you turn on "Set time automatically" and "Set time zone automatically." On macOS, it's the Date & Time settings set to update automatically. Then relaunch and reconnect.

This one's easy to miss because a clock that's off by even a few minutes can be enough, and a dead CMOS battery or a fresh OS install can reset it without you noticing. So it's worth checking even when the time looks right. Fixing the clock often clears more than just this one kick, since it tends to show up alongside other login and launcher errors.

Make sure you're using a genuine, signed-in account

Online-mode servers reject any connection that isn't backed by a real, authenticated account. A client that isn't properly signed in, or one that skips authentication entirely, gets this kick every time, on every listed server.

So confirm the launcher is signed into the Microsoft account that owns the game, and that you're launching the official client rather than an unofficial one. The do you need to buy Minecraft to play on servers guide has the full ownership picture and explains why offline or cracked clients can't pass an online-mode check.

What the pattern is doing tells you where to look. If it's intermittent and only just started, it's far more likely the token, an outage, or the clock from the sections above. A kick that's constant across every server you try points instead at the account or sign-in.

Still stuck? A short checklist before you give up

Run these top to bottom:

Fully restart the launcher and re-log.
Check auth status and try a second server.
Fix the system clock.
Confirm a genuine, signed-in account.

A couple of catch-all checks occasionally matter too. Update the launcher and the game to a current build, and make sure a firewall, antivirus, or VPN isn't blocking the launcher's connection to the auth servers — toggle the VPN off to test. None of this touches your saved servers or single-player worlds, since it's all about refreshing the login, so there's nothing to back up before you try it.

Once you can authenticate again, the monthly rankings and the full server list show which communities are live right now, and how to join a Minecraft server covers the non-auth connection errors like version, edition, and typos.

FAQ

Does "Failed to verify username" mean my account is banned or hacked?

No. It's a login-session check, not a ban or a security alert. A ban from a server shows a different message with that server's ban reason, and a hacked account would fail to sign in at the launcher entirely. This kick almost always means your login session needs refreshing — sign out of the launcher and back in. If it then happens on every server you try, the cause is an auth outage, a wrong clock, or an account that isn't properly signed in, none of which means your account was compromised.

Why does it kick me on one server but let me in on another?

The server that kicks you is running in online mode, which is the standard for the servers in our rankings — it verifies your account with Microsoft/Mojang before letting you in. A server that lets you in without that check is running in offline mode, which skips authentication. So getting in somewhere else doesn't mean your account is fine and the first server is broken; it means only the online-mode server is actually checking, and the verification is what failed. Refresh your login and the online-mode server should accept you too.

I run a server and my players get this error — is this the right guide?

This guide is written for players being kicked, so the fixes here are player-side. If it's happening to everyone joining your own server, you're usually looking at a server-side setting — typically the online-mode option, or, if you run a proxy in front of your server, the authentication arrangement between the proxy and the backend. That's an administrative configuration on the server rather than anything a joining player changes, so the steps above won't apply to you.

Do I need to reinstall Minecraft to fix this?

Almost never. Reinstalling doesn't refresh the login token that this error is really about, so it rarely helps and costs you a long download. Work through the quick fixes first: fully restart the launcher and sign back in, check whether the authentication servers are down, and confirm your system clock is set correctly. Those resolve the large majority of cases. Reinstalling is a last resort, and even then updating the launcher and game is the more useful step.