Photo by Patrik Kernstock on Unsplash

So you sit down to play some Minecraft, probably after a long day, maybe you've got friends waiting in a server lobby, and you get smacked with this:

Failed to connect to the server.
Error: Authentication servers are down for maintenance.

Or sometimes it shows up as:

Failed to login: Invalid session (Try restarting your game and the launcher)

Yeah. The Mojang session servers are down, or at least they're not talking to your game properly. I've seen this come up constantly in forums and Discord servers whenever there's a Mojang outage, and the frustrating part is — half the time people don't even realize it's not their fault.

Here's what's actually going on.

Why This Happens

Minecraft doesn't just let you waltz into a multiplayer server. Every time you connect, your client reaches out to Mojang's session servers at session.minecraft.net to verify your account. It's basically an authentication handshake. If Mojang's servers are having a moment — whether it's scheduled maintenance, an unexpected outage, or just general cloud infrastructure weirdness — that handshake fails and you're locked out.

The error can also show up even when Mojang's servers are technically "up" but running slow. A timeout is treated the same as a full refusal, so the game just throws the auth error and moves on.

Honestly, it's one of those things that feels like your problem but usually isn't. Before you spend 45 minutes reinstalling Java or deleting your .minecraft folder, do yourself a favor and check the status first.

Step 1: Actually Check If Mojang's Servers Are Down

Go straight to the official Mojang status page:

https://www.minecraft.net/en-us/community-standards

Wait, wrong link — the one you actually want is:

https://help.minecraft.net/hc/en-us

Or better yet, use a third-party tracker that updates faster:

https://downdetector.com/status/minecraft/

If the outage map is lighting up red and hundreds of people are reporting issues in the last hour, congrats — it's not you. The Minecraft authentication servers are down and the fix is just... waiting. I know that's not what you want to hear, but messing with your system while Mojang's backend is on fire won't help anything.

That said, if the status looks fine on their end, then something local might be interfering. Let's check those next.

Fix 1: Force Re-authenticate Through the Launcher

This is the first thing I try, and it works more often than you'd expect. Sometimes your local session token gets stale — it expires or gets invalidated — and the launcher is just sitting there trying to use a dead token.

Close Minecraft completely, then open your launcher and log out of your Microsoft/Mojang account entirely:

Launcher → Click your profile name (top right) → Sign Out

Then sign back in. The launcher will grab a fresh auth token and that usually clears up the "Invalid session" error fast. If you're on the legacy Minecraft Launcher, it looks slightly different but the idea is the same — sign out, sign in, relaunch.

Fix 2: Flush Your DNS Cache

Here's where it gets a little more technical, but stick with me — this one actually matters. Your computer caches DNS lookups, which includes the address for session.minecraft.net. If that cached entry is stale or corrupted, your requests might be going nowhere even though Mojang's servers are fine.

On Windows, open Command Prompt as administrator and run:

ipconfig /flushdns

On macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Linux (Ubuntu/Debian):

sudo systemd-resolve --flush-caches

After that, restart your browser and launcher, then try connecting again. I've personally fixed this exact issue on a friend's machine after he swore up and down that "the game is broken." DNS cache. Four seconds to fix. Sometimes it really is that simple.

Fix 3: Check Your Firewall and Antivirus

This one's less common but worth checking — especially if you recently installed a new security tool or your antivirus pushed an update. Some overzealous firewalls will block outbound connections to session.minecraft.net or authserver.mojang.com without telling you anything useful.

Temporarily disable your antivirus or third-party firewall (Windows Defender is usually fine), then try to connect. If it suddenly works, you've found your culprit. Add Minecraft and the launcher as exceptions:

Windows Security → Firewall & network protection → Allow an app through firewall → Add Minecraft Launcher

Also worth checking if you're on a school or work network — those environments sometimes block gaming-related domains at the router level and there's basically nothing you can do about it from your end without a VPN. Speaking of which...

Fallback: Try a VPN (Temporarily)

This sounds weird, but hear me out. If the session server issue is regional — meaning Mojang's infrastructure is struggling in your geographic area but not everywhere — routing your traffic through a VPN can bypass that entirely. I've seen this work during partial outages where some regions couldn't authenticate but others could.

Use any VPN you trust, connect to a US or EU server, and try launching Minecraft again. You don't need to keep the VPN running during gameplay, just for the initial authentication handshake. Once you're in, you can disconnect the VPN and your session stays valid.

Free options like ProtonVPN work fine for this. You're not doing anything sketchy, just routing your auth request through a different path.

One More Thing

If you're running Minecraft through a third-party launcher like MultiMC, ATLauncher, or Prism Launcher — and you're getting auth errors specifically on those — make sure the launcher itself is updated. Mojang occasionally changes their auth endpoints (especially after the Microsoft account migration a while back), and older launcher versions sometimes haven't caught up yet. Updating the launcher to the latest version takes care of it 90% of the time.

Alright, hopefully one of these got you back into your world without too much hassle. If Mojang's session servers are genuinely down though, the DNS flush and VPN tricks can only do so much — sometimes you just gotta wait it out and blame the cloud. Hope this saves you some time.

Related: How to Fix "Failed to Verify Username" in Minecraft (2024)