›_ Claude Code Issues
Claude Code Issues / #36004

[BUG] Authorization failed: “Internal server error” prevents Claude Code login

Resolved 💬 25 comments Opened Mar 19, 2026 by kennethkhoocy Closed Mar 19, 2026
💡 Likely answer: A maintainer (chrislloyd, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code fails during authorization/login. Instead of completing the auth flow, it shows:

Authorization failed
Internal server error

A Try again button is displayed, but clicking it does not resolve the issue. The result is that Claude Code cannot complete sign-in and is unusable.

What Should Happen?

Claude Code should complete the authorization flow successfully and return to a usable signed-in state, without showing an internal server error.

Error Messages/Logs

Authorization failed
Internal server error

Steps to Reproduce

Open Claude Code.

Start the authorization or sign-in flow.

Complete the browser-based login flow if prompted.

Return to Claude Code.

Observe the error screen showing: “Authorization failed” and “Internal server error.”

Click Try again.

Observe that the same error persists.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code v2.1.79

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

25 Comments

shyuuuuni · 3 months ago

I have same issue.

A0x01 · 3 months ago

I have same issue.

hodor · 3 months ago

Same issue

looeee · 3 months ago

Not to mention, I finally get through the whole process after many server errors and retries, and I get a code to paste into CC and I am presented with this

OAuth error: timeout of 15000ms exceeded

<img width="618" height="454" alt="Image" src="https://github.com/user-attachments/assets/1c4d1c96-a86a-42e4-8dcb-543501148894" />

I guess those seconds are expensive, they couldn't afford to give us even a minute to get through the multiple steps of the login flow.

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/33270
  2. https://github.com/anthropics/claude-code/issues/33260
  3. https://github.com/anthropics/claude-code/issues/28074

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

BGPark · 3 months ago

I have same issue.

brad0924 · 3 months ago

same issue

Juhee-Jang · 3 months ago

Same issue

paralin · 3 months ago

Same issue :)

parkindani · 3 months ago

Same issue

schugazi · 3 months ago

Same issue

zhimin-z · 3 months ago

same...

firesinger82 · 3 months ago

same

chickengir1 · 3 months ago

same..

ProtoErikS · 3 months ago

Same

BiFengJiang · 3 months ago

Same

rrgks6221 · 3 months ago

It appears to have been fixed in the Korean region, so I assume it’s being rolled out region by region.

ystgd07 · 3 months ago

I have same issue.(Korean region)

kennethkhoocy · 3 months ago

Seems to be working now--fingers crossed!

parkindani · 3 months ago

Now working in Korean region too

akiofujii-xp · 3 months ago

Workaround: You can avoid this issue by running Claude Code from Claude Desktop.

loshuliveros · 3 months ago

OS: Windows
Version: Claude Code v2.1.79
/login sends email, link returns invalid token
Reproducible repeatedly, multiple browsers (Chrome, Edge, incognito)

brad0924 · 3 months ago

seems fixed now

chrislloyd collaborator · 3 months ago

Incident is resolved: https://status.claude.com/incidents/6wlrxz9pqz8f

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.