If Minecraft stops at “Invalid session,” “Failed to verify username,” or a message mentioning Yggdrasil, start by checking whether the problem affects one server or every server. Then check for a service incident, refresh your Microsoft sign-in through the official launcher, test another network, and try a clean vanilla profile. A Minecraft Yggdrasil authentication error can come from an expired local sign-in, a blocked connection, a temporary service issue, or a server that cannot complete its account check; the wording alone does not identify the cause.
What a Minecraft Yggdrasil authentication error means
Yggdrasil is a name associated with Minecraft: Java Edition authentication and appears in some older client and server messages. For players, Minecraft sign-in now uses a Microsoft account. That means a Yggdrasil-related message is best treated as an authentication or session failure to diagnose, not as an instruction to visit a separate “Yggdrasil login” site. Minecraft’s official help recommends signing out and back in to reset the connection to authentication servers and other game services. The migration period for Mojang accounts ended on December 18, 2023, so an old account-migration link is not a current fix.
The exact meaning depends on where the message appears. An “Invalid session” message after leaving the launcher open may point to a stale sign-in. If only one server rejects you, the server or its authentication setup may be involved. If many players cannot sign in at once, a broader service problem becomes more likely. Use the checks below to narrow it down before changing files or settings.
Match the symptom to the next check
| What you see | Start here |
| One server fails, but other online servers work | Check that server’s status, version compatibility, and owner announcements. |
| Several servers report “Invalid session” for your account | Close the game and launcher, then refresh the Microsoft sign-in. |
| Friends on different networks also cannot sign in | Look for official Minecraft service notices and wait if an incident is reported. |
| The problem happens only on one Wi-Fi network | Temporarily compare with another trusted network and review VPN, proxy, or filtering settings. |
| Your own server log mentions a failed authentication or public-key request | Check the server host’s outbound connectivity and authentication configuration. |
How to fix Minecraft authentication errors
1. Check the scope and service notices
Write down the complete error text and note whether you are using Java Edition or Bedrock, which launcher you opened, and whether one or multiple servers are affected. Ask a friend on a different connection to try the same service if practical. Check Mojang Status on X for incident updates and use Minecraft’s official sign-in help for account guidance. A status post may not mention every short disruption. If several people are affected, wait and retry later instead of repeatedly changing account or network settings.
2. Sign out and back in through the official launcher
- Exit the game completely, then close the Minecraft Launcher.
- Reopen the launcher, select the account menu, and choose Log out.
- Select Microsoft Login and sign in with the Microsoft account that owns Minecraft or has the required PC subscription.
- Launch the game again and retry the server.
These are the steps in Minecraft’s sign-in reset instructions. On Windows, if the launcher says you do not own the game or the Play button is missing, confirm that the Minecraft Launcher and Microsoft Store are using the account with the license; Minecraft’s launcher access guide explains how to check this. On console or mobile, follow the platform-specific sign-out and sign-in instructions in Minecraft Help. Do not share a verification code with anyone who contacts you.
3. Test the network without weakening security
If a clean sign-in does not help, briefly test whether the connection is the difference:
- If you use a VPN, proxy, or filtering service, turn it off temporarily only if it is safe and allowed on your network, then retry. Turn it back on after the test.
- Try a trusted alternate connection, such as a phone hotspot. If that works while your usual network does not, investigate the router, DNS filtering, proxy, or network firewall with its administrator or provider.
- Check that your computer’s date, time, and time zone are set correctly. A badly incorrect clock can interfere with secure sign-in connections.
- Allow the official Minecraft Launcher and Java game process through your firewall if they were blocked. Keep the firewall enabled; do not create broad allow rules or disable security protection to test a game login.
Change one thing at a time so you can identify what made a difference. Avoid copying old lists of authentication hostnames from forum posts: service infrastructure and launcher behavior can change, and a hostname should only be allowed when current official guidance or your network administrator confirms it is needed.
4. Test a clean game profile and separate client from server
Update the launcher from the official Minecraft download page, then start a current vanilla release with no mods. This is a diagnostic test: it helps show whether a mod, loader, custom launcher profile, or authentication-related add-on is involved. If vanilla works, add components back one at a time and check their maintainers’ documentation for versions compatible with your game. Back up worlds before making changes, and do not delete your saves to fix a sign-in problem.
If the error occurs on just one server, note whether the server is online, whether it supports your game version, and whether other players can join. A client sign-in refresh will not repair a server outage or a broken server-side authentication check. Send the owner the exact message and the time it occurred, but remove personal information and never include access tokens, refresh tokens, passwords, or session data.
Server-owner checks for Yggdrasil log errors
For a Java server you administer, first confirm that the server is running a compatible, current server build from the official Java server download page. Review the full log around the failure and determine whether the server process can reach the services it needs through the host’s DNS, firewall, and outbound network rules. If only the server host reports authentication or public-key request failures while players can sign in elsewhere, that points toward a host-side connection or configuration problem; it does not prove that a player’s account is invalid.
- Keep
online-mode=true on a normal public authenticated server. Setting it to false is not an authentication repair and can let users connect under names they do not own.
- If you use a proxy, forwarding layer, or authentication plugin, check its current documentation and compatibility with your server version. Test configuration changes carefully and keep a backup.
- Do not edit
launcher_profiles.json, manually replace tokens, or run unofficial token-refresh utilities. Use the launcher’s account controls instead.
When to contact Minecraft Support
If the error continues across networks and a clean official launcher sign-in, contact Minecraft Support. Include your edition, operating system, launcher type, exact error text, and the steps you already tried. For a server-only issue, give the server owner the time of failure and the relevant sanitized log lines. These details help distinguish an account sign-in problem from a local network or server configuration issue.
For most players, the safest order is simple: check service notices, refresh the Microsoft sign-in, compare networks, and test vanilla. This approach addresses the common causes of a Minecraft Yggdrasil authentication error without risking saved worlds, account credentials, or server security.