Authentication Servers Are Not Reachable Minecraft | Fix

What This Minecraft Authentication Error Really Means

When you try to join a multiplayer server, Minecraft sends a quick check to online login services run by Mojang and Microsoft. That check proves that your account is valid and that your username can be trusted on the server you picked. If that step fails, the game shows messages such as “Failed to login,” “authentication servers are not reachable,” or “authentication servers are down.”

Most players first assume that Mojang’s entire login system has stopped working. Sometimes that happens, and status pages will show an outage. In many cases, though, the login service is fine and the blockage sits between your device and those servers. That gap can come from a local network problem, a launcher glitch, a firewall rule, a broken DNS setting, or a misconfigured modded install.

The good news is that this error rarely means your world or account data are lost. The handshake fails before you even reach the server world. Once the connection path is clear again, you can join with the same profile and pick up where you stopped.

Authentication Servers Are Not Reachable Minecraft Fix Steps

This section lays out a practical path that starts with quick checks and ends with deeper network fixes. You can walk through the list in order until the game lets you join servers again.

1. Check Mojang Service Status — Confirm whether login or session services are down for everyone.
2. Restart Game And Launcher — Fully close the launcher, wait a moment, and start it fresh.
3. Log Out And Back In — Refresh your Microsoft account session inside the launcher.
4. Test Your Internet Connection — Try other websites, games, or a different network to rule out a local outage.
5. Apply Network Fixes — Flush DNS, review firewall rules, remove bad entries from the hosts file, and try without VPN or proxy.
6. Review Launcher And Mods — Update the launcher, confirm you use an official account, and check modded profiles for IPv6 or Java argument issues.
7. Check The Server Side — Make sure the server is online, uses the right version, and runs in online mode.

Before you start changing many settings, it helps to run a few quick comparisons so you know whether the problem sits with Mojang, with your own network, or with a single server.

Fast Triage Checks

Check	How To Do It	What It Tells You
Mojang status	Visit the official Minecraft help or status pages in a browser.	Shows whether login or session services are listed as down.
Another device	Try signing in and joining a server from a second PC, console, or phone on the same network.	If the second device works, the problem sits with your main device or launcher.
Different server	Join a well-known public server as well as a smaller one.	If only one server fails, the issue is likely on that server’s side.

Quick Checks Before You Dig Into Settings

Start with actions that change very little on your system, yet often clear stuck sessions. Many “authentication servers are not reachable” reports end here without any advanced work.

• Restart The Launcher — Close Minecraft, close the launcher itself from the taskbar or system tray, wait ten to twenty seconds, then start it again.
• Fully Reboot The Device — Restart your PC, console, or phone so any cached connection data and background tasks reset.
• Log Out Of Your Account — In the Minecraft launcher, click your profile picture, choose log out, close the launcher, then open it and sign in again with the correct Microsoft account.
• Check Date And Time — Open your system clock settings and turn on automatic time and time-zone sync so login tokens line up with Mojang’s servers.
• Test Singleplayer And Realms — Load a local world or Realm. If singleplayer works but every external server fails, the issue sits in the online handshake layer.

If these simple steps do not change anything, watch the exact wording of the error. Screens that mention being “down for maintenance” or “not reachable” often point toward either general service issues or network path problems between you and the authentication endpoint.

Network And DNS Fixes For A Reliable Login Path

Minecraft relies on your operating system’s DNS and routing settings to reach authentication services. When those settings point to the wrong place, block domains, or fall back to an inactive route, you can see the same error even while other websites still load.

Flush DNS And Try A Different Resolver

• Flush DNS Cache On Windows — Open Command Prompt as an administrator and run ipconfig /flushdns, then restart the launcher.
• Switch DNS Servers — In your network adapter settings or router, change DNS to a public resolver such as 8.8.8.8 and 1.1.1.1, then test Minecraft again.

If a stale entry or slow local resolver caused the issue, these steps often restore the ability to reach Mojang and Microsoft login endpoints.

Review Hosts File And Firewall Rules

• Check The Hosts File — On Windows, open C:\Windows\System32\drivers\etc\hosts in a text editor run as administrator and remove any lines that mention Mojang or Minecraft domains, then save and restart your device.
• Test With Firewall Disabled Briefly — Temporarily turn off third-party security suites or strict firewall rules, then try to join a server. Turn protection back on once you finish the test.

Some VPN clients, antivirus tools, and privacy add-ons insert entries into the hosts file or intercept traffic to certain domains. Removing those entries and letting the system use normal DNS again can clear the login path.

VPN, Proxy, And IPv6 Edge Cases

• Try Without VPN Or Proxy — Disconnect from VPN apps and remove proxy entries in your system network panel, then retry the connection.
• Check IPv6 Behavior On Modded Setups — Forge and other mod loaders can prefer IPv6 when it is turned on in the system, even if the router does not route IPv6 traffic. Some players fix the error by disabling IPv6 on their Wi-Fi adapter or by adding the Java argument -Djava.net.preferIPv4Stack=true to the launcher profile.

If the account suddenly stopped working when you moved to a modded profile or a new network, these routing details deserve a close look. Clearing them often brings the login prompt back to normal.

Launcher, Version, And Account Problems That Trigger The Error

Even with a stable network, the “authentication servers are not reachable Minecraft” message can appear when the launcher fails to handle your account session correctly. Recent changes to Microsoft account login and the end of Mojang account support add more room for confusion.

• Use The Official Launcher — Make sure you are running the current Minecraft launcher from Microsoft Store or the official website, not an old third-party launcher.
• Update To Current Version — In launcher settings, let it update itself and reinstall any missing game files if prompted.
• Re-Add Your Account — Remove the existing profile from the launcher account list, close the launcher, open it again, and log in fresh with your Microsoft account.
• Avoid Cracked Clients — Non-official launchers that skip online account checks will always fail on servers that require real authentication, no matter what you change on your network.
• Watch For Version Mismatches — If the server runs a different major version, the launcher might appear to fail auth when the real conflict is the game version.

If you migrated from a Mojang account to a Microsoft account recently, confirm that the launcher shows the correct email address and profile. A mismatch here can leave the client in a half-signed-in state where it thinks you own the game but cannot complete the online validation step.

When The Problem Lives On The Server Side

Sometimes everything on your end is fine and the error still appears for a single world or host. In those cases the login request reaches Mojang, but the destination server does not handle the response correctly or cannot be reached in time.

• Confirm The Server Is Online — Check its status page, Discord, or panel and see whether other players can join at that moment.
• Check The Address And Port — A typo in the hostname or a missing port number can route your traffic to a dead endpoint.
• Online Mode Settings — For self-hosted servers, verify that online-mode in server.properties fits your use case. If it is set to true while the box cannot reach Mojang, you will see auth errors until routing is fixed.
• Proxy Or Bungee Layers — If the server uses a proxy layer, that layer might lose its own connection to authentication services and show the message even when the base node is fine.

Public hosts often announce planned downtime, migration work, or DDoS protection changes on their status channels. If you only see the error on one network, wait a while or reach out to the server owner through their normal contact routes.

Practical Checklist When Authentication Servers Fail

At this point you have seen how many moving parts sit behind a single line of error text. To keep things simple during the next outage, keep a short checklist nearby so you can move through fixes without guesswork.

• Look At Service Status First — Visit official Minecraft status or help pages and a trusted outage tracker to see whether login trouble is global.
• Restart Launcher, Device, And Router — Clear stuck sessions and refresh your local network.
• Re-Sign Into The Launcher — Log out, close the launcher, then sign in again with the correct Microsoft account.
• Flush DNS And Remove Hosts Entries — Reset the name lookup path so Mojang and Microsoft domains resolve cleanly.
• Test Without VPN, Proxy, And Extra Security Tools — See whether any of them stand in the way of the login flow.
• Adjust IPv6 Or Java Network Flags If You Use Mods — Turn off unused IPv6 on your adapter or add the IPv4 preference flag for modded instances that show this error.
• Confirm Server Health — Try more than one server and, for private worlds, check that the host has a working path to Mojang services.

When you follow this path, most cases of the “Authentication Servers Are Not Reachable Minecraft” error clear without reinstalling the game or wiping data. The steps give you a repeatable routine you can use every time multiplayer login starts to misbehave, whether you play on a small private world or on busy public servers.