[BUG] OAuth Request Failed Internal server error

Resolved 💬 52 comments Opened Oct 31, 2025 by RogierKonings Closed Nov 10, 2025
💡 Likely answer: A maintainer (blois, 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?

When I try to authenticate my Claude CLI or VSCode extension, I get the following error.

OAuth Request Failed
Internal server error

The issue persists even after clearing local cookies/ initiating a /logout in the claude CLI

What Should Happen?

I should get redirected without an error message

Error Messages/Logs

OAuth Request Failed
Internal server error

Steps to Reproduce

  1. Try to login with Claude Code

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.30

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

52 Comments

oliska · 8 months ago

Same issue on macOS, CLI 2.0.30 / 2.0.24, Claude Max login → “Internal Server Error” after browser redirect. Tried incognito, cleared cache, no VPN — still broken.

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/9376
  2. https://github.com/anthropics/claude-code/issues/9534
  3. https://github.com/anthropics/claude-code/issues/8007

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

Dimonka2 · 8 months ago

I am not alone..
Auth failing in various ways. It was an error during pressing "Authorize" button. Then was an error during login via email (unable to send verification email). Then just "service unavailable". And in between something like "too many requests".

Timnoo · 8 months ago

Same here (just wanted to get started with claude code, so no previous installs here). I tried:

  • various browsers
  • clearing all cache
  • started the process without being logged in
  • tried the API key flow, redirect to console.claude.ai gave the same error
iRonin · 8 months ago

Same here FFS...

miladjafary · 8 months ago

I had the similar issue.
I have tried to re-install the claude code entirly,
I have tried different browser and other machine
I don't use any VPN or active firewall rule that preventing the Authentication.
sometimes I see the "Authorized" button but nothing will happen after clicking that
and I constantly get "OAuth Request Failed"

<img width="642" height="542" alt="Image" src="https://github.com/user-attachments/assets/42b5e288-a162-45bd-891c-9c6100ab310b" />

ninokth · 8 months ago

same here ubuntu 22.04

yaqoobhisbani · 8 months ago

Facing same issue - macOs

omersonc-ghost · 8 months ago

+1

Gloria00123 · 8 months ago

+1

licht1stein · 8 months ago

+1

rzimanTJY · 8 months ago

+1

illusivejosiah · 8 months ago

+1

bsifflard77 · 8 months ago

+1

rureirureirurei · 8 months ago

+1

crcc23 · 8 months ago

Same here. No way to OAuth claude code CLI or IDE. With or without VPN cleared cookies and cache, Windows or Linux. Dead! OAuth Request Failed Internal Server Error.

saiko-psych · 8 months ago

yea its still down i guess

SIGMACX · 8 months ago

+1

neverased · 8 months ago

+1

saiko-psych · 8 months ago

sometimes i get to the authorisation page, but then when i click the button nothing happens

stanvanheumen · 8 months ago

+1 still broken

mcmorry · 8 months ago

+1

aszabo314 · 8 months ago

same here

pratikpparikh · 8 months ago

+1

slothkins · 8 months ago

+1

ahoog42 · 8 months ago

as a work around to the TUI OAuth error, if you have the Claude Code for VSCode extension installed, I found you can still use that. I prefer the TUI but until the OAuth issue is fixed, this might work for other folks too.

<img width="381" height="82" alt="Image" src="https://github.com/user-attachments/assets/b60b4d1d-7570-40a3-9302-7d79f540cb19" />

k-f- · 8 months ago

+1

Shatnerz · 8 months ago

If it helps at all, I am seeing

{
    "type": "error",
    "error": {
        "type": "api_error",
        "message": "Internal server error"
    },
    "request_id": "req_011CUfHuB2Qc3y5rmMAh5tc9"
}

on the authorize/ call of the oauth process

princegaurav · 8 months ago

Facing a similar issue for the last 3-4 hours. Browser says "OAuth Error, Internal Server Error" . I am trying to log in using /login from Claude code. I am getting this error in Claude code: API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CUf4bZLpS3WWw8pZYKzkk"} · Please run /login.

Everything was working fine 2 days back when I was 98% on my Pro plan weekly limit, which reset today.

OS System: Mac, Claude Code v2.0.30

ammar-medify · 8 months ago

Same here...

  • I have 2 accounts (personal Max + team Premium)
  • Getting "OAuth Request Failed - Internal server error"
  • Already contacted support with no response

I have one terminal with the max account seems to be responding but the visual studio code is not

pankajknp1 · 8 months ago

+1. 😒. Can we bypass authentication

Narasimha-Code · 8 months ago

Same Here

Timnoo · 8 months ago

I slipped through, what worked for me:

  • Open Claude Code and try to authenticate as usual.
  • It will give an Internal Server Error.
  • Close Claude Code and re-open.
  • On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts)
  • From there on, be cautious. Spamming the button ruins the proces.
  • Turn on Browser inspect → Network and click the button.
  • Monitor the status for the call, it will give back a 500 error but the page was not showing anything.
  • Click the button again, wait every time for the 500 to appear before the next attempt.
  • Suddenly it went through.

After about 20-30 tries this worked for me, I'm not trying to reproduce this ;).

ramxv · 8 months ago
I slipped through, what worked for me: Open Claude Code and try to authenticate as usual. It will give an Internal Server Error. Close Claude Code and re-open. On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) From there on, be cautious. Spamming the button ruins the proces. Turn on Browser inspect → Network and click the button. Monitor the status for the call, it will give back a 500 error but the page was not showing anything. Click the button again, wait every time for the 500 to appear before the next attempt. * Suddenly it went through. After about 20-30 tries this worked for me, I'm not trying to reproduce this ;).

Surprisingly, this worked for me. After 35 attempts

Sy-D · 8 months ago

Same issue here. Opened a support ticket 4h in and still no reply from their end.

princegaurav · 8 months ago
I slipped through, what worked for me: Open Claude Code and try to authenticate as usual. It will give an Internal Server Error. Close Claude Code and re-open. On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) From there on, be cautious. Spamming the button ruins the proces. Turn on Browser inspect → Network and click the button. Monitor the status for the call, it will give back a 500 error but the page was not showing anything. Click the button again, wait every time for the 500 to appear before the next attempt. * Suddenly it went through. After about 20-30 tries this worked for me, I'm not trying to reproduce this ;).

This method worked for me to get the Authentication Code (the Network tab helps check the button-click status). But there is a next step, when you have to paste this code in Claude Code, and there it failed again, giving 500. And unfortunately, there you don't get a chance to try this code multiple times, so you need to start all over again, so very slim chance of going through completely.

tripa2020 · 8 months ago
> I slipped through, what worked for me: > > Open Claude Code and try to authenticate as usual. > It will give an Internal Server Error. > Close Claude Code and re-open. > On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) > From there on, be cautious. Spamming the button ruins the proces. > Turn on Browser inspect → Network and click the button. > Monitor the status for the call, it will give back a 500 error but the page was not showing anything. > Click the button again, wait every time for the 500 to appear before the next attempt. > * Suddenly it went through. > > After about 20-30 tries this worked for me, I'm not trying to reproduce this ;). This method worked for me to get the Authentication Code (the Network tab helps check the button-click status). But there is a next step, when you have to paste this code in Claude Code, and there it failed again, giving 500. And unfortunately, there you don't get a chance to try this code multiple times, so you need to start all over again, so very slim chance of going through completely.

this worked for me as well

bandarunagesh · 8 months ago

I am experiencing the same issue.

neprja · 8 months ago

+1

uzmasterdev · 8 months ago

Its almost more than an hour that I stuck in authorization, and its not working, sadly my subscription time is running, but I did not get served due to "Internal Server Error"

Shatnerz · 8 months ago

https://status.claude.com/ has today as only 37 minutes downtime. Login and oauth has been down for at least 7 hours now. The status page doesn't even acknowledge this current ongoing failure. Pretty frustrating to think that we can't even report this anywhere and that they may not even be aware of the issue.

PtitBreton3531 · 8 months ago
Je suis passé entre les mailles du filet, voici ce qui a fonctionné pour moi : Ouvrez Claude Code et essayez de vous authentifier comme d'habitude. Cela générera une erreur interne du serveur. Fermez Claude Code et rouvrez-le. De mon côté, l'écran avec la mention « autoriser » s'est affiché à plusieurs reprises (il m'a fallu de nombreuses tentatives). À partir de là, soyez prudent. Cliquer frénétiquement sur le bouton perturbe le processus. Activez l'inspection du navigateur → Réseau et cliquez sur le bouton. Surveillez l'état de l'appel ; il renverra une erreur 500, mais la page n'affichera rien. Cliquez à nouveau sur le bouton et attendez que le chiffre 500 s'affiche avant de faire une nouvelle tentative. * Soudain, ça a fonctionné. Après une vingtaine ou une trentaine d'essais, ça a fonctionné pour moi, je ne cherche pas à reproduire ça ;).

Works also thanks ! Need to wait for the button, then click on Authorize multiple time and its working !

500 x1, x2, x3... I've refresh the page many times (maybe 15 times) :
<img width="1899" height="857" alt="Image" src="https://github.com/user-attachments/assets/ad14b1dc-177e-4ab9-afac-741d4a2bf51e" />

And then it worked :

<img width="1899" height="735" alt="Image" src="https://github.com/user-attachments/assets/d4e0990c-13b2-4ebb-9541-daede2860a46" />

riisch · 8 months ago
I slipped through, what worked for me: Open Claude Code and try to authenticate as usual. It will give an Internal Server Error. Close Claude Code and re-open. On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) From there on, be cautious. Spamming the button ruins the proces. Turn on Browser inspect → Network and click the button. Monitor the status for the call, it will give back a 500 error but the page was not showing anything. Click the button again, wait every time for the 500 to appear before the next attempt. * Suddenly it went through. After about 20-30 tries this worked for me, I'm not trying to reproduce this ;).

worked for me

uzmasterdev · 8 months ago

yeah, in 4th try it worked and gave me code

fearoffish · 8 months ago

4th? I get Internal Server Error about 40-50 times with a long wait to find out. If it succeeds (it has 3 times) it redirects to the chat window and doesn't give me a code to authorise my cli.

[edit] Note: On Linux.

ShingWish · 8 months ago
I slipped through, what worked for me: Open Claude Code and try to authenticate as usual. It will give an Internal Server Error. Close Claude Code and re-open. On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) From there on, be cautious. Spamming the button ruins the proces. Turn on Browser inspect → Network and click the button. Monitor the status for the call, it will give back a 500 error but the page was not showing anything. Click the button again, wait every time for the 500 to appear before the next attempt. * Suddenly it went through. After about 20-30 tries this worked for me, I'm not trying to reproduce this ;).

Nice! It works perfect

pankajknp1 · 8 months ago

Working for me now 😊

slunkeh · 8 months ago
> I slipped through, what worked for me: > `` > * Open Claude Code and try to authenticate as usual. > > * It will give an Internal Server Error. > > * Close Claude Code and re-open. > > * On my end, it displayed the screen with "authorize" on multiple occasions (took me many attempts) > > * From there on, be cautious. Spamming the button ruins the proces. > > * Turn on Browser inspect → Network and click the button. > > * Monitor the status for the call, it will give back a 500 error but the page was not showing anything. > > * Click the button again, wait every time for the 500 to appear before the next attempt. > > * Suddenly it went through. > `` > > > > > > > > > > > > After about 20-30 tries this worked for me, I'm not trying to reproduce this ;). Surprisingly, this worked for me. After 35 attempts

This worked for me right now, thank you!

efreitasrj · 8 months ago

took me some 10 tries, but it worked. i used Claude Code from the terminal in VS Code

sammiykay · 8 months ago

Step 1: Initiate the Login Process
Open a Fresh Browser Session: Start a new or "fresh" browser profile (or use an incognito/private window). This ensures no existing sessions interfere.

Action: When the link shows in the terminal, copy it and open it in the fresh browser.

Step 2: Complete Web-Based Authentication
Enter Credentials: Input your email address associated with your Claude account and click Log In (or a similar button).

Check for Verification: The service will send a verification link or magic link to your email.

Verify Email: Open your email and click on the verification link in the same fresh browser you used in Step 1. This step confirms your identity.

Step 3: Retrieve and Use the Authentication Code
Receive the Code: After clicking the verification link, the browser page will typically display an authentication code or secret key.

Copy the Code: Copy this unique code from the browser window.

Paste into the Terminal: Go back to your Claude code terminal (or VS Code terminal) where you initiated the process.

Enter the Code: Paste the copied code into the designated input area in the terminal (or command prompt) and press Enter.

Confirm Login:

Success: You should receive a confirmation message like "Login successful!"

The terminal application is now authenticated to use your Claude account.

blois collaborator · 8 months ago

Transient issue, should be resolved.

github-actions[bot] · 8 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.