Photo by Steve Barker on Unsplash

So there I was, just trying to hop on a server with some friends on a Friday night, and Minecraft hits me with that soul-crushing error: "Failed to verify username!" No warning, no explanation — just a hard block at the login screen. I've seen this error pop up a hundred times over the years, and every single time it catches someone off guard.

The good news? It's almost never your fault, and it's almost always fixable in under five minutes. Let me walk you through what's actually going on and how to get back in.

What the Error Actually Looks Like

When you try to connect to a Minecraft Java Edition server, you'll see something like this in the disconnect screen:

Failed to verify username!

Or sometimes it shows up as:

Failed to authenticate your connection.
Invalid session (Try restarting your game and the launcher)

Both are essentially the same problem. Minecraft's session servers couldn't verify that you are who you say you are. It's an authentication handshake failure between your client and Mojang's auth servers.

Why This Happens

Here's the thing — Minecraft Java Edition uses Mojang's (now Microsoft's) authentication servers every time you join an online server. Your game gets a session token when you log in through the launcher, and that token has to be validated server-side before you're allowed in.

That token expires. Or the auth servers hiccup. Or your launcher didn't properly pass the token to the game client. Sometimes it's Mojang's servers just having a rough day. Sometimes it's your local network doing something weird. Either way, the fix is usually straightforward.

Honestly, about 70% of the time this happens, it's either a session token issue or Mojang's auth servers are down. Worth checking that second thing before you start tinkering.

First Thing to Do: Check Mojang's Servers

Before you touch anything on your end, just go check status.mojang.com or downdetector.com and search Minecraft. If Mojang's authentication service is down, you can't fix this locally — you just wait it out. I've wasted 20 minutes troubleshooting before realizing the servers were just melting on their end.

Fix 1: Completely Restart the Launcher and Re-login

This sounds too simple, but it actually works most of the time. The session token that gets generated when you launch Minecraft can go stale, especially if your launcher was sitting open for a while.

Close Minecraft and the launcher entirely — don't just close the game window. On Windows, make sure it's not hanging in the system tray.

Then clear your launcher's cached session. On Windows, you can do this by navigating to:

%APPDATA%\.minecraft\

And deleting the launcher_accounts.json file. Don't worry — this just clears your cached login and you'll be prompted to sign in again fresh. Your worlds and settings stay completely untouched.

Reopen the launcher, sign back into your Microsoft account, and try joining the server again. Fresh token, fresh session.

Fix 2: Flush Your DNS and Reset Your Network Stack

Sometimes the issue is that your machine can't properly reach Mojang's auth endpoints because of a DNS caching problem or a funky network state. This is more common than you'd think, especially if you've been on a VPN recently or switched networks.

Open Command Prompt as Administrator on Windows and run these back to back:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

Restart your PC after the winsock reset — it won't take effect until you do. On macOS, the DNS flush command is:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Also — and I feel like I have to mention this every time — disable your VPN if you're running one. Mojang's servers can occasionally block or fail to verify sessions coming through certain VPN exit nodes. It's annoying, but it's real.

Fix 3: Check Your System Clock (Seriously)

This one trips people up all the time. Minecraft's authentication process uses time-sensitive tokens, and if your system clock is significantly off — like more than a couple minutes — the auth handshake fails because the token looks expired or invalid from the server's perspective.

On Windows, right-click your taskbar clock and hit Adjust date/time, then toggle "Set time automatically" off and back on. Or run this in an elevated Command Prompt:

w32tm /resync /force

On Linux:

sudo timedatectl set-ntp true

I know it sounds ridiculous that a clock would break your Minecraft login, but cryptographic auth tokens are picky like that. The server sees a timestamp that doesn't line up and just rejects the whole thing.

Fallback: Switch to an Offline-Mode Server (For Private Servers Only)

If you're running your own server with friends and none of the above worked, there's a quick workaround — though I want to be clear this only makes sense for private, trusted servers. Open your server.properties file and set:

online-mode=false

This disables the authentication check entirely. Your server won't verify usernames against Mojang's servers at all. Again — only do this on a private server with people you trust. Running a public server in offline mode is asking for trouble with impersonation and griefing.

For most people though, Fix 1 — clearing the launcher accounts file and re-logging — is going to be the answer. It was for me that Friday night. Took about 90 seconds and we were back in the game.

Hope this saves you from staring at that error screen for longer than you have to.