[BUG] Unable to Login

Same problem

Same here

+1

+1

same problem. I was. looking at DNS:

DNS Verification
accounts.anthropic.com returns NXDOMAIN from both local DNS and Google's public resolver:
$ dig accounts.anthropic.com

; <<>> DiG 9.10.6 <<>> accounts.anthropic.com
;; QUESTION SECTION:
;accounts.anthropic.com. IN A

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47159
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; AUTHORITY SECTION:
anthropic.com. 1800 IN SOA isla.ns.cloudflare.com. dns.cloudflare.com. 2398319840 10000 2400 604800 1800

;; SERVER: 192.168.1.1#53
$ nslookup accounts.anthropic.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find accounts.anthropic.com: NXDOMAIN
Note: claude.ai and api.anthropic.com both resolve and connect normally. Only accounts.anthropic.com is missing.

Same problem, tried several times, got a code to paste every 5th time but Claude Code always ran into timeout.

same

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/33239
2. https://github.com/anthropics/claude-code/issues/33214
3. https://github.com/anthropics/claude-code/issues/33246

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

+1

+1

+1

great shit antrhopic +1 thanks for wasting tokens.

+1

+1

https://status.claude.com/

lets solve ai incident quickly using ai

+1

Root Cause (Likely)

Claude Code CLI authentication uses an OAuth flow through the browser. The browser successfully authenticates the account, but the CLI fails when receiving or validating the OAuth callback token.

This mismatch usually occurs when:

1. The CLI is waiting for the OAuth callback on a local port but fails to receive it.
2. The callback token expires before the CLI processes it (often due to lag in the auth flow).
3. The CLI version introduces a regression in the OAuth callback handler.

Since the browser shows authenticated but the CLI throws an OAuth error, the failure likely happens after authorization, during token exchange or callback handling.

---

Proposed Fix

Improve OAuth callback handling in the CLI by:

1. Ensuring the CLI correctly listens for the OAuth redirect.
2. Adding retry logic for token exchange failures.
3. Increasing timeout tolerance for slow authentication flows.

---

Example Fix (TypeScript)

Improve OAuth Callback Listener

Ensure the local server waits long enough for the redirect.

const AUTH_TIMEOUT = 120000; // increase timeout to 120s

server.listen(port);

const timeout = setTimeout(() => {
  reject(new Error("OAuth authentication timeout"));
}, AUTH_TIMEOUT);
Handle Token Exchange Errors Gracefully

Add retry logic when exchanging the authorization code.

async function exchangeToken(code: string) {
  for (let attempt = 0; attempt < 2; attempt++) {
    try {
      return await requestAccessToken(code);
    } catch (err) {
      if (attempt === 1) throw err;
    }
  }
}
Ensure Redirect URL Matches Expected Callback

Verify the CLI registers the same redirect URI used during authorization.

Example:

http://localhost:PORT/oauth/callback

If the redirect URI differs, the OAuth flow will succeed in the browser but fail in the CLI.

Additional Defensive Handling

Add validation to detect the "browser authenticated but CLI failed" state:

if (!authCode) {
  throw new Error(
    "OAuth authentication succeeded in the browser but the CLI did not receive the callback."
  );
}

This prevents silent failures and gives a clearer error message.

Expected Result After Fix

/login opens the browser.

User authorizes successfully.

CLI receives the OAuth callback.

Access token is exchanged and stored locally.

Claude Code CLI finishes authentication successfully.

Impact

Fixes login failures in Claude Code 2.1.72.

Improves reliability of OAuth authentication.

Prevents timeout-related login errors during slower authentication flows.

+1

+1

+1

Same problem here

+1

+1

+1

Same issue on EndeavourOS (Arch-based), Lima, Peru. Claude Code 2.1.72, installed via npm + nvm.

Environment:

• OS: EndeavourOS / kernel 6.19.6-arch1-1
• Node: v22.14.0 (nvm)
• Shell: bash 5.3.9
• Can log in via claude.ai web browser ✅
• /login in CLI fails with OAuth error: timeout of 15000ms exceeded ❌

Workaround confirmed working for Linux/nvm users:

# Find the file
CLI=$(find ~/.nvm/versions/node -name 'cli.js' -path '*claude-code*')
echo "Patching: $CLI"

# Apply the timeout fix
sed -i 's/timeout:15000/timeout:45000/g' "$CLI"
sed -i 's/AbortSignal.timeout(15000)/AbortSignal.timeout(45000)/g' "$CLI"

After patching, /login completes successfully. This confirms the issue is not specific to Windows — it affects Linux users in Latin America as well, likely due to regional latency on the OAuth callback endpoint.

+1

The patch fix did not work for me on Ubuntu. As soon as the browser finally responds saying "Build something great..." the CLI reports OAuth error timeout exceeded even at 45000ms.

I was successful with:

1. npm install -g @anthropic-ai/claude-code@2.1.66
2. /login (Successful login)
3. npm install -g @anthropic-ai/claude-code

I don't know if it was a coincidence, but I'm logged in now

2.1.66 also worked for me, thanks @tpzub

I was successful with: 1. npm install -g @anthropic-ai/claude-code@2.1.66 2. /login (Successful login) 3. npm install -g @anthropic-ai/claude-code I don't know if it was a coincidence, but I'm logged in now

I did this (without -g) in conjunction to https://github.com/anthropics/claude-code/issues/33247#issuecomment-4040530566 (timeout adjust).. which worked well enough to get my login back and from there, I resumed on the latest version of claude code..

Setup claude token claude setup-token in your zshrc to avoid this oauth nonsense in the future

This sounds silly and it might not apply to everyone, but I had a stale auth token set in my start up config in my terminal. Since I use VSCode with my fish terminal, it was also loading this invalid Auth token.

VSCode requires a restart to reload environment variables so...

1. Ensure you've removed export CLAUDE_CODE_AUTH_TOKEN="...", set -x CLAUDE_CODE_AUTH_TOKEN "..." and the like from any of your terminal startup scripts.
2. Restart your computer
3. Re-authenticate through the typical means (VSCode login sequence, claude setup-token, etc

Had the same issue this morning. Mix of 500 and timeout errors. Must have tried more tha a dozen times.
What worked for me:

• Switch from Opus4.6 1M context -> Sonnet4.6
• Run /login -> select Claude account with subscription
• Close out auto Browser Tab open from OAuth flow before it can navigate
• Copy/Paste the URL and manually navigate -> Click "Authorize"
• Copy/Paste code into terminal

I got a timeout error on the first attempt, but second time finally succeeded.