How to Fix "The Authentication Servers Are Currently Not Reachable"

Failed to login: The authentication servers are currently not reachable. Please try again. means your Minecraft Java client couldn't get your session validated against Microsoft and Mojang — it has nothing to do with the server's address or game port. It shows up in two places: in the launcher while you're signing in, and at the moment you try to join any online-mode server. There are exactly two things behind it, and almost all of the fix is figuring out which one you've got: either the auth backend itself is down for everyone, or something on your own machine — DNS, a firewall, antivirus, a VPN — is quietly blocking the login endpoints while the rest of your internet works fine.

So lead with diagnosis, not random tweaks: check the official status pages first, since a genuine Xbox sign-in outage leaves nothing on your end to change, and work the local fixes only once the services report healthy. This is a different animal from "Can't connect to server" or a connection timeout, which point at the server's address and port 25565, not your login. A Failed to verify username! or an Invalid session kick are close cousins of this same handshake, with their own walkthroughs at Failed to verify username and Invalid session.

What the error actually means

When you sign in, the launcher talks to a chain of Microsoft and Mojang services — login.live.com for the Xbox account, then api.minecraftservices.com and sessionserver.mojang.com to mint and check your Minecraft session. The error fires when any link in that chain can't be reached or doesn't answer in time. The server you're joining never enters into it: an online-mode=true server (the default) hands verification off to Mojang, so if your client can't reach Mojang, the join fails before the server has any say.

It's a client-side auth failure both times, sitting with you and not the server. And it's specifically a Java Edition string — Bedrock words the same situation as "You need to authenticate to Microsoft services" with named error codes, so if you're reading this exact sentence, you're on Java.

First, check whether it's actually an outage

When this hits everyone at once, the cause is almost always the auth backend being down, and no setting you change will help. Before you touch anything, open the Xbox Live status page and the Minecraft Help status notes. If "sign-in" or account services are flagged with an incident or maintenance, stop right there — that's an outage, and the only fix is to wait and retry. You'll sometimes see the related wording The authentication servers are currently down for maintenance., which is the same situation said more plainly.

The tell is scale. If status pages show an incident, or friends and a quick search turn up lots of players hitting it at the same moment, it's the backend and you wait it out. If status is green and other people are logging in fine, the problem is your machine, and you move on to the local fixes below.

Relog and restart — the most common single-player cause

When it's just you, the usual culprit is a stale or expired auth token. Fully close the launcher (not just the game window), sign out of your Microsoft account, sign back in, and relaunch. That forces the launcher to fetch a fresh token, and it clears this error more often than any other single step. It costs you thirty seconds, so do it before anything more involved.

Fix your DNS

If a relog didn't do it, suspect DNS — your ISP's default resolver sometimes fails to look up the Microsoft and Mojang hostnames even while ordinary browsing works. Clear the cached lookups and switch to a resolver that handles them reliably.

On Windows, flush the cache from a command prompt:

ipconfig /flushdns

Then set your DNS to Cloudflare (1.1.1.1 and 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4) in your adapter's IPv4 properties. On macOS the cache flush is sudo dscacheutil -flushcache and you set DNS under Network settings; on Linux you change it through NetworkManager or your resolver config. After switching, restart the launcher and retry.

Let the launcher and Java through the firewall, and pause VPN/antivirus

The launcher needs outbound access to several Microsoft and Mojang domains, and an over-eager firewall, third-party antivirus, or VPN can block exactly those while leaving your web browsing untouched. That mismatch is what makes it confusing.

Work through it like this:

• Whitelist the apps. Allow the Minecraft Launcher and the Java runtime through Windows Defender Firewall, ticking both Private and Public. Add the same allow rules in any third-party antivirus that does its own network filtering.
• Turn off the VPN or proxy to test. A VPN can route you through a region or path where the auth endpoints are unreachable, so disable it and retry. (It occasionally does the opposite and gets you around an ISP-level block, so keep "try a VPN" as a fallback — but disabling it is the first move.)
• The domains that matter are api.minecraftservices.com, sessionserver.mojang.com, and login.live.com. You don't normally whitelist domains by hand, but if you run network-level filtering, those are the ones to permit.

Deeper local checks when it still won't sign in

A few rarer causes are worth a look if nothing above landed.

Your hosts file. Antivirus tools and old "cracked"-launcher utilities sometimes drop entries into C:\Windows\System32\drivers\etc\hosts that point Mojang domains at dead IPs, which produces this exact error. Open it and remove any lines referencing mojang.com, minecraft.net, or live.com — including the legacy authserver.mojang.com, retired for modern Microsoft accounts but still seen in stale blocklists. On macOS and Linux the same file lives at /etc/hosts.

Your clock. A wrong system date, time, or region breaks the TLS handshake to the auth servers, because the certificate check fails. Set the clock to update automatically and confirm the time zone is right.

IPv6. If your router only partially supports IPv6, the launcher can try an IPv6 route to the auth servers that goes nowhere. Disabling IPv6 on the adapter forces it back onto IPv4, which often connects.

As a last resort on Windows, resetting the network stack with netsh winsock reset and netsh int ip reset (then rebooting) clears a corrupted socket configuration that can block the login traffic.

Why "turn off authentication" isn't a player fix

A lot of forum advice tells you to "set online-mode=false," and that's a misunderstanding worth clearing up. online-mode=true lives in the server's server.properties and tells the server to verify every joining player against Microsoft and Mojang. Only the server owner can change it — a player can't disable authentication on someone else's server, and flipping their own server to offline mode doesn't fix this error for a legitimate account anyway.

It also carries real costs. Offline ("cracked") mode removes verification entirely, so anyone can join under any username — including impersonating your ops — and it changes how player UUIDs are generated, which can orphan inventory, homes, and rank data keyed to the old online UUIDs. That tradeoff is the owner's to weigh; for a player seeing this message, offline mode simply isn't your lever. Your fixes are the client-side ones above, and once you're back in, the live server rankings are waiting.

FAQ

Will reinstalling Minecraft or the launcher fix this?

Almost never — nothing about your game files is broken. The failure is a stale token or a blocked connection, so a reinstall spends an hour doing what a sign-out and sign-in does in thirty seconds. The one real exception is a launcher that won't open or update at all; if it loads far enough to show the sign-in screen, reinstalling lands you on the same auth result. Refresh the token, work the DNS and firewall checks, and only reinstall if the launcher itself is visibly broken.

Is Failed to verify username! the same problem?

It's the server side of the same handshake. Failed to login: The authentication servers are currently not reachable is your client failing to validate your session; Failed to verify username! is the server failing to verify you against Mojang during the join. They share root causes — a Mojang outage or your network blocking the session endpoints — so the diagnosis order is identical, and the dedicated Failed to verify username guide handles the server-kick angle.

After an outage clears, I still can't log in — what now?

A stale token is the usual reason. The launcher cached the failed state during the outage, so sign out of your Microsoft account completely, close the launcher, sign back in, and relaunch to mint a fresh session. If that still fails once status pages are green, flush DNS with ipconfig /flushdns, point your resolver at 1.1.1.1 or 8.8.8.8, and confirm your system clock is correct, since a wrong time keeps breaking the TLS handshake long after the servers themselves have recovered.