[BUG] Claude Code Won't Authenticate
Open 💬 27 comments Opened Apr 7, 2026 by tonyadamsmba
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 401's. Please run /login · API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"Invalid authentication
credentials"},"request_id":"req_011CZpbgSrn1Mizj8HRxuERB"}
I try logging on two different systems and accounts and neither authenticates.
What Should Happen?
Claude needs to check server auth. Seems to be down.
Error Messages/Logs
OAuth error: Request failed with status code 500
/sentry?o=1158394&p=4504646202490880:1 Failed to load resource: the server responded with a status of 405 ()
frame-modern.0a5dd965.js:1 [Intercom] The App ID in your code snippet has not been set. Set it to your App ID found in settings to complete installation: https://app.intercom.com/a/apps/_/settings/web
i @ frame-modern.0a5dd965.js:1
4511-836cf7d7c29971cf.js:12 POST https://claude.ai/v1/oauth/2a2ea6d3-aabf-4ade-a648-73e03f7c8ea3/authorize 500 (Internal Server Error)
(anonymous) @ 4511-836cf7d7c29971cf.js:12
(anonymous) @ 5741-7db25d1e8bdade8e.js:1
(anonymous) @ 5741-7db25d1e8bdade8e.js:1
mutationFn @ 5741-7db25d1e8bdade8e.js:1
fn @ 3402-131091089dd79cc0.js:1
m @ 3402-131091089dd79cc0.js:1
start @ 3402-131091089dd79cc0.js:1
execute @ 3402-131091089dd79cc0.js:1
await in execute
mutate @ 3402-131091089dd79cc0.js:1
(anonymous) @ 3402-131091089dd79cc0.js:1
(anonymous) @ 5741-7db25d1e8bdade8e.js:1
onClick @ page-6bec8de39cb19f2d.js:1
i8 @ 87c73c54-1748cec33284d13b.js:1
(anonymous) @ 87c73c54-1748cec33284d13b.js:1
nz @ 87c73c54-1748cec33284d13b.js:1
sn @ 87c73c54-1748cec33284d13b.js:1
cc @ 87c73c54-1748cec33284d13b.js:1
ci @ 87c73c54-1748cec33284d13b.js:1
n @ 4511-836cf7d7c29971cf.js:16
4511-836cf7d7c29971cf.js:12 [REACT_QUERY_CLIENT] QueryClient error: a: Internal server error
at n (5741-7db25d1e8bdade8e.js:1:96226)
at 5741-7db25d1e8bdade8e.js:1:101101
at async Object.mutationFn (5741-7db25d1e8bdade8e.js:1:101919)
(anonymous) @ 4511-836cf7d7c29971cf.js:12
error @ 2001-2cb39c522acd3961.js:1
e @ 4189-fe0c22b4928358ee.js:1
onError @ 4189-fe0c22b4928358ee.js:1
execute @ 3402-131091089dd79cc0.js:1
await in execute
mutate @ 3402-131091089dd79cc0.js:1
(anonymous) @ 3402-131091089dd79cc0.js:1
(anonymous) @ 5741-7db25d1e8bdade8e.js:1
onClick @ page-6bec8de39cb19f2d.js:1
i8 @ 87c73c54-1748cec33284d13b.js:1
(anonymous) @ 87c73c54-1748cec33284d13b.js:1
nz @ 87c73c54-1748cec33284d13b.js:1
sn @ 87c73c54-1748cec33284d13b.js:1
cc @ 87c73c54-1748cec33284d13b.js:1
ci @ 87c73c54-1748cec33284d13b.js:1
n @ 4511-836cf7d7c29971cf.js:16
Steps to Reproduce
/login in claude code.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.92
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
27 Comments
real af
+1
+1 this is urgent
that's not a claude code bug man: Status
+1
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1 - OAuth is broken. Reauthentication does not work. In the Webbrowser (Chrome) i press authorize and after a time i get redirected to: https://platform.claude.com/oauth/code/success?app=claude-code.
The console shows: OAuth error: timeout of 15000ms exceeded
The manual process with pressing c and copy the oauth code manually in the console also runs into a timeout.
SideInfo: Token still worked this moring (about 10 am Berlin Time) with v2.1.92.
going opensource it's not simple guys, let's understand them
Same, backup authentication methods are failing as well.
Yep. Can confirm that Auth appears broken for claude in vscode. I'm running vscode remotely on coder provisioned vm, and it was working before.
Entering the token doesn't work, and after few monents the error appears
timeout of 15000ms exceeded<img width="379" height="466" alt="Image" src="https://github.com/user-attachments/assets/7ad1cb59-a67c-4389-9dfe-0bf46f629f88" />
+1 - There is a workaround to get the token. Instead of letting the link automatically open when typing /login, copy and paste the link manually onto your browser. However, when you paste the token generated it does not do anything even if you click enter a few times. I am executing this on my terminal btw and I am on mac os.
+1
Claude is malfunctioning every day. What does it mean not to log in?
sigh... +1
+1 :(
Can confirm this on Mac CLI Claude Code v2.1.92. Manual c&p the code also runs in timeout.
wait.... how can they fix claude.... if claude does not work?
same issue as yesterday -_-
YO IT WORKED FOR ME JUST GO INTO THE PERMISSIONS FOR THE BROWSER AND JUST ALLOW EVERYTHING MY GUESS IT JUST TAKES TO LONG AND IT TIMES OUT WHEN ITS TRYING TO ASK FOR POP UPS OR WHATEVER I JUST SWITCHED TO EDGE THEN WENT ON THE PERMISSIONS FOR THE URL AND ALLOWED EVERYTHING AND IT WORKED
+1
Fixed. Working again (Y).
CLICK ON THE TUNE LOOKING BUTTON ON THE LEFT OF THE URL AT THE TOP OF YOUR BROWSER ITS THE 4TH BUTTON AT THE END OF THE URL CLICK IT, GO DOWN CLICK THE THIRD OPTION CALLED SITE SETTINGS THEN JUST ALLOW IT TO HAVE ALL THE PERMISSIONS ON ALLOW ON THE URL CLAUDE GIVES YOU THEN GO BACK TO THE TERM TRY IT AGAIN AND IT SHOULD WORK
I found a workaround to login via VS Code. If you have the Claude Code plugin installed, type /login and copy paste the link manually onto your browser to get the code. You might have to click authorize multiple times but if all is well you should be able to get your token. Once you have it, go back to VS Code and paste the token via the Claude Code plugin. You might encounter a timeout error and if so just try again until you successfully login.
I was able to login just now. I didn't do anything special.
On Tue, Apr 7, 2026 at 10:18 AM mcpolo78 @.***> wrote:
I can login now, it's working.
working now
Apologies for the disruption, folks! We believe this issue has been resolved.