Claude "There Was an Error Logging You In": How to Fix It

If you see the message "there was an error logging you in" on Claude, it almost always comes from stale cookies, a Google or SSO hiccup, or being signed into the wrong account — not a broken password. Clear your claude.ai cookies, open an incognito window, sign in with one account, and the error usually clears within minutes.

Model lineup verified 31 July 2026 against Anthropic's model overview.

Few things are as annoying as typing the right email and password, waiting for the redirect, and landing back on a screen that reads "there was an error logging you in." Your credentials are fine. The problem is almost always in the handshake between your browser and Claude's login servers — the step that creates your session after you've already proven who you are. Having actually used it ourselves, we can point to where it delivers and where it falls short.

The good news is that this is one of the most fixable messages Claude throws at you. Below you'll get the causes in plain English, an ordered checklist of fixes, and a clear signal for when the problem is on Anthropic's side rather than yours. Work from the top and stop as soon as you're back in.

The login flow is the same whichever model you use — Claude currently spans models like Opus 5, Sonnet 5, and Haiku 4.5 — and these steps are reviewed regularly, so most people are back in within 10 minutes.

Why Claude says there was an error logging you in

Six causes account for nearly all of it: stale cookies and cache, a Google or SSO round-trip that fails, several signed-in accounts at once, a blocking browser extension, VPN or network filtering, and, rarely, an Anthropic outage.

Signing in is a multi-step conversation. Your browser sends a login request, Claude verifies it, hands back a session token, and stores that token in a cookie. If any link in that chain breaks, you get "there was an error logging you in" instead of your chat history. Here are the usual culprits, roughly in order of how often they're to blame:

• Stale or corrupted cookies and cache. Old session data from a previous login collides with the new one. This is the single most common cause.
• A Google or SSO hiccup. The OAuth round-trip to Google — or your company's identity provider — times out or returns to the wrong URL.
• Wrong or multiple accounts. Your browser is signed into several Google accounts and the sign-in silently picks the wrong one.
• A browser extension. Ad blockers, privacy tools, and script blockers can strip the cookies or scripts Claude needs to finish authenticating.
• VPN, proxy, or network filtering. Anthropic may flag traffic from shared VPN exit nodes, which breaks the token exchange.
• An Anthropic outage. Occasionally the login service itself is down, and nothing on your end will help.

Notice that only the last item is genuinely out of your hands. The first five you can fix yourself in a couple of minutes. If Claude is broadly not working — chats won't load, pages hang — that's a wider problem than the login screen alone, so check that guide too.

Causes and fixes at a glance

The table pairs each cause with the symptom that gives it away and the first fix worth trying, ordered from fastest and most common down to rarest. Start at the top if you cannot tell which one applies to you.

Use this table to jump straight to the fix that matches your situation. If you're not sure which applies, just start at the top and work your way down — the fixes are ordered from fastest and most common to rarest.

Fix 1: Clear cookies and cache for claude.ai

Corrupted cookies cause most login failures, so clear only claude.ai rather than wiping the whole browser. Delete its stored site data from privacy settings, or clear cookies and cached files, restart the browser, and sign in fresh.

Because corrupted cookies cause most login failures, start here. You don't need to wipe your whole browser — just clear the data for Claude.

In Chrome or Edge, open Settings > Privacy and security > Third-party cookies > See all site data, search for claude.ai, and delete its stored data. Or press Ctrl + Shift + Delete (Cmd + Shift + Delete on Mac), tick "Cookies and other site data" plus "Cached images and files," clear it, and restart the browser. Then return to claude.ai and sign in fresh. For a lot of people, the "there was an error logging you in" message simply never comes back after this one step.

Fix 2: Try an incognito or private window

A private window ignores stored cookies and disables most extensions, isolating the fault in seconds. Success there points at a bad cookie or an extension; failure there points at your account, your network, or Anthropic's servers.

An incognito window is the fastest diagnostic you have. It ignores your stored cookies and disables most extensions, so it isolates the problem in seconds. Press Ctrl + Shift + N (Cmd + Shift + N on Mac), open claude.ai, and log in.

If it works in incognito, you've confirmed the trouble is a bad cookie or an extension in your normal window — go back and clear cookies or disable extensions. If you still see "there was an error logging you in" even in a private window, the cause is deeper: your account, your network, or Anthropic's servers. That single test saves you from randomly poking at settings.

Fix 3: Sign in with a single account

With several Google accounts live in one browser, Continue with Google can hand Claude an address that was never registered. Claude never auto-creates accounts from Google, so choose the right account deliberately in a fresh private window.

This one trips up more people than they realize. If you're logged into two or three Google accounts in the same browser, the "Continue with Google" button may hand Claude the wrong identity — and if that address was never registered with Claude, sign-in fails. Claude does not auto-create accounts from Google, so the wrong email produces an error rather than a new profile.

The clean fix: open an incognito window (which starts with zero Google sessions), click "Continue with Google," and explicitly choose the exact account tied to your Claude subscription. Alternatively, sign out of every Google account, then sign back into only the correct one before returning to Claude. Getting down to a single account resolves a surprising share of "there was an error logging you in" reports.

We run Claude across the web, the desktop app, and Claude Code from one machine all day while working on this site, and this is the exact trap that has caught us more than any other. With a personal and a work Google account both live in the same browser, the "Continue with Google" button quietly picks whichever one Google saw last — and if that is not the address our Claude account is under, the login dies at the handshake every time. The incognito window is what we now reach for first, precisely because it forces us to choose the right account out loud instead of letting the browser guess.

Fix 4: Disable browser extensions

Ad blockers, anti-tracking tools, script blockers, and some password managers strip the cookies and scripts authentication depends on. Turn them off, reload, sign in, then re-enable one at a time and add an exception for claude.ai.

Privacy extensions are helpful right up until they block the very cookies and scripts a login needs. Ad blockers, anti-tracking tools, script blockers like NoScript, and some password managers are the usual offenders.

If Fix 2 showed that incognito works, an extension is almost certainly the cause. Turn your extensions off one at a time — or all at once — reload claude.ai, and sign in. Once you're in, re-enable them one by one to find the culprit, then add an exception for claude.ai so it doesn't happen again.

Fix 5: Turn off your VPN and check your network

Busy VPN and proxy exit nodes get flagged by Anthropic's security signals, which breaks the token exchange — Anthropic's own guidance advises against using a VPN with Claude. Disconnect, disable proxies, and retry on an ordinary connection.

Anthropic uses security signals to spot suspicious traffic, and busy VPN or proxy exit nodes often get flagged. When that happens the token exchange can't complete and you're bounced back with the error. Anthropic's own guidance on troubleshooting Claude login specifically suggests not using a VPN when you access Claude.

Disconnect your VPN, disable any proxy, refresh the login page, and try again. If you're on a strict office or school network, a firewall may be filtering the requests; switch to a normal home connection or your phone's mobile data to rule the network out. A flaky connection alone can also trigger "there was an error logging you in," so confirm the rest of the internet is working before you dig deeper. The same region mismatch derails Claude identity verification if you are ever asked to confirm a phone number, so it is worth leaving the VPN off for that step too.

Fix 6: Try another browser or device

Switching is a test as much as a fix. Working elsewhere proves the fault is local to your main browser; failing everywhere means the problem has moved server-side, and no amount of local cleanup will change it.

Switching browsers is both a fix and a test. If Claude logs you in perfectly on your phone or in a second browser but keeps failing in your main one, the problem is local — corrupted data or an extension you haven't caught yet — and you can go back and clean that browser with confidence.

But if every browser and every device shows the same wall, the issue has moved out of your control. That pattern is the clearest sign that "there was an error logging you in" is a server-side problem, not a you problem — which is exactly what the next section is about. It's a close cousin of not being able to reach Claude at all when the service is struggling.

Fix 7: Check whether Claude is down

Check the status page before spending more time on your own setup. A posted incident touching authentication means waiting is the fix. An all-green page with a persistent failure sends you back to the cookie, extension, and VPN checks.

Before you spend another minute troubleshooting your own setup, confirm the service is actually up. If login is failing for everyone, waiting is genuinely the only fix. Open Anthropic's status page and look for any active incident touching authentication, claude.ai, or the API.

If an incident is posted, you're done — save your work, grab a coffee, and check back once it's marked resolved. If the status page is all green but you still can't get in, cross-reference Anthropic's own troubleshooting guide for Claude error messages, which walks through the same cookie, extension, and VPN checks for stubborn cases.

Is it a Google or SSO problem specifically?

If the failure lands right after the Google screen, the OAuth link is the weak point. Retry once, reselect the account deliberately rather than letting the browser choose, and if it persists switch to the emailed magic link.

If the error appears right after the Google or single-sign-on screen — the page flashes back and forth, then fails — the OAuth link itself is the weak spot. First, simply retry: transient OAuth timeouts often clear on a second attempt. Reselect your account deliberately rather than letting the browser auto-pick.

If retrying doesn't help, unlink Google from your Claude account and switch to the emailed magic-link login instead. That sidesteps the OAuth handshake entirely and is the most reliable workaround when Google sign-in keeps throwing "there was an error logging you in." If the magic link then never arrives or reports as already used, our wider triage for Claude login not working explains why corporate mail scanners quietly burn those single-use links. Company SSO users who are stuck should loop in their IT admin, since the identity provider configuration may be the real blocker rather than anything on Claude's end.

When there was an error logging you in isn't your fault

If the failure survives cleared cookies, incognito, another browser, and another device, the fault sits server-side. Check the status page, then retry every 15 to 30 minutes instead of hammering the login button.

Sometimes you'll do everything right and still hit the wall. If the error survives cleared cookies, incognito, a different browser, and a different device, stop troubleshooting locally — the fault is on the server side. These login failures often travel with related backend errors: an OAuth error with status 500, an authorization failed / internal server error message, or a plain internal server error. All three point to Claude's backend rather than your browser.

In that case your job is simple: check the status page, wait, and retry every 15–30 minutes. Avoid hammering the login button, which can trip rate limits and make things worse. When the incident clears, your normal login will start working again without any further action from you.

For how Claude authentication works in the first place — and why there is no password to forget — see Claude login.

Seeing a code to paste? That is designed behaviour over SSH, WSL2 and containers — the Claude authorization code explains when it appears and why a paste gets rejected.