Account and login

Failed to Verify Authentication (MinecraftClientHttpException)

What the log looks like

com\.mojang\.authlib\.exceptions\.MinecraftClientHttpException
Failed to verify authentication\s+com\.mojang\.authlib\.exceptions\.InvalidCredentialsException

How to fix it

  1. If your game froze on the loading screen or closed unexpectedly, look past this warning: check the crash-reports folder for a separate crash file, remove unsupported PvP/hack clients (such as Meteor Client with Sodium), or update your graphics drivers if the game hangs with no Java crash report.
  2. To fix the 401 authentication error itself so you can join online servers, open your launcher's account manager, remove or log out of your Microsoft account, and sign back in to generate a fresh session token.
  3. Ensure your launcher profile is set to launch with your online Microsoft account rather than Offline mode.
  4. If signing back in still fails to verify authentication, check your firewall, VPN, and system hosts file to make sure api.minecraftservices.com and sessionserver.mojang.com are not blocked or redirected.
LoadersVanilla, Fabric, Quilt, Forge, Neoforge
SeverityWorth checking
CategoryAccount and login

Check your own log

Related errors

Account and loginFailed to Verify Authentication (AuthenticationUnavailableException)If your game actually crashed or froze, scroll to the very bottom of latest.log or check the crash-reports folAccount and loginFailed to Verify Authentication (InvalidCredentialsException: Status: 401)If you cannot join online multiplayer servers ("Invalid session"), close Minecraft, log out of your Microsoft Account and loginFailed to Verify Authentication (MinecraftClientHttpException / Status 401)To restore online multiplayer access, open your launcher's account settings, log out of your Microsoft accountAccount and loginHMCL Microsoft Login Failed: Missing client_id (AADSTS900144)Remove your current source-built or CI snapshot copy of HMCL.