Photo by Oberon Copeland @veryinformed.com on Unsplash

It was a Saturday afternoon, kids were home, everyone wanted to play, and Minecraft just refused to connect. "Authentication servers are down for maintenance." No warning. No ETA. Just a wall. I spent the first fifteen minutes convinced I'd broken something with a router update the night before before I realized — oh, this is a Mojang problem, not mine.

The infuriating part is how generic the error is. It could mean the actual Mojang auth servers are on fire. It could mean your local DNS is doing something weird. It could mean an antivirus updated itself overnight and quietly decided to block the launcher. You genuinely can't tell from the message alone, and that's where most people waste an hour going in circles.

So here's what the error actually looks like, why it happens, and the fixes I've used — in order of how fast they work.

What the Error Looks Like

Failed to login: The authentication servers are currently down for maintenance.

Or sometimes you'll see this in the launcher itself:

Error: Failed to authenticate your connection.
Session ID: (null)

And occasionally this one, which shows up when the launcher can't even reach the auth endpoint:

Invalid session (Try restarting your game)

Restarting your game doesn't fix it. Restarting your game never fixes it. But they still put that message there. Classic.

Photo by Zulfugar Karimov on Unsplash

Why This Actually Happens

Mojang's authentication runs through authserver.mojang.com and session.minecraft.net. When your launcher tries to log you in, it's hitting those endpoints and asking for a session token. If those servers are genuinely down, nobody gets in. Full stop. You can check their status at https://status.mojang.com — if you see red or orange on "Minecraft session server," that's your answer and there's nothing to do but wait.

But here's the thing — sometimes those endpoints show green and you're still getting the error. That's when it gets interesting.

Your hosts file might have a stale or malicious entry redirecting Mojang's domains somewhere wrong. This happens more than you'd think, especially if you've ever used a cracked launcher (no judgment, but that's where it comes from), or if some "optimization" tool touched your network settings. Antivirus software is also a repeat offender here. I've seen Kaspersky and Avast both block session.minecraft.net after routine definition updates, no notification, no explanation.

And sometimes it's just a corrupted launcher cache sitting there with a bad session token that won't refresh itself no matter how many times you close and reopen the app.

Photo by Egor Komarov on Unsplash

Fix 1: Check the Hosts File First

This is the one most guides skip and it's the one that's saved me twice. On Windows, open Notepad as administrator and open this file:

C:\Windows\System32\drivers\etc\hosts

On Mac or Linux:

sudo nano /etc/hosts

Look for any lines that mention mojang.com, minecraft.net, or session.minecraft.net. If you see something like:

0.0.0.0 session.minecraft.net
127.0.0.1 authserver.mojang.com

Delete those lines. Save the file. That's a redirect entry, and it's blocking your connection completely. After you remove it, flush your DNS cache:

# Windows
ipconfig /flushdns

# Mac
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd)
sudo systemctl restart systemd-resolved

Then try logging in again. Honestly, if this was the problem, it works immediately.

Photo by Bernd 📷 Dittrich on Unsplash

Fix 2: Clear the Launcher Cache

The Minecraft launcher caches your session data, and sometimes that cache just goes bad. The launcher keeps holding onto a dead token and keeps sending it to the auth server, which keeps rejecting it, and you're stuck in a loop.

Close the launcher completely. Then delete the cache folder:

# Windows — press Win+R and paste this path
%AppData%\.minecraft\launcher_accounts.json

Actually, don't just delete that one file. Clear the whole launcher cache directory:

# Windows
%AppData%\.minecraft\

# Look for and delete these specifically:
launcher_accounts.json
launcher_profiles.json

On Mac:

~/Library/Application Support/minecraft/

Delete those JSON files, not the whole folder — you want to keep your saves and mods obviously. Reopen the launcher, log in fresh. It'll generate new auth files and pull a clean session token. This fixes probably 40% of cases where the status page shows everything as fine but you still can't connect.

Fix 3: Temporarily Disable Your Antivirus or Firewall

Look, I know this feels wrong. But if nothing else has worked and the Mojang status page is green, try disabling your AV for five minutes and testing the connection. Not forever. Just to diagnose.

If it works with AV off, you've found your culprit. Add exceptions in your antivirus for:

session.minecraft.net
authserver.mojang.com
api.mojang.com
textures.minecraft.net

And in Windows Firewall, make sure the Minecraft launcher executable has both inbound and outbound rules allowing it through. You can check this in Windows Defender Firewall under "Allow an app through firewall." The Java runtime (javaw.exe) needs to be on that list too if you're running Java edition.

Fallback: Play in Offline Mode While You Wait

If the servers are genuinely down and you just want to play singleplayer while Mojang sorts their stuff out, you can launch in offline mode. In the official launcher, go to your installation settings and look for "Play in offline mode" — it appears automatically when the launcher detects auth is unavailable. Your worlds are local, so everything you've built is still there. You just can't join multiplayer servers while offline.

And if you're running a local server for friends on the same network, set online-mode=false in your server.properties file temporarily. Just remember to set it back — leaving it off permanently means anyone can join without a real account.

One Last Thing

Mojang's auth infrastructure has gotten more reliable since Microsoft took over, but it still goes down. Usually not for long — most outages clear within an hour or two. The status.mojang.com page is actually decent now, so bookmark it and check there before spending an hour troubleshooting your own setup.

But if that page is green and you're still locked out, nine times out of ten it's the hosts file or the launcher cache. Start there. Save yourself the spiral. And if it's truly just Mojang being down, go touch grass for an hour. It'll be back up by the time you get home.