[BUG] Request failed with status code 403" error. Claude Max

[rbrinkke]

Environment

• Platform (select one):
  • Anthropic API
  • AWS Bedrock
  • Google Vertex AI
  • Other:
• Claude CLI version: 0.2.103 (Claude Code)
• Operating System: Linux (based on your terminal prompt showing "appuser@ubuntu-8gb-nbg1-1")
• Terminal: Bash terminal
• Node version: v18.19.1
• npm version: 9.2.0
  ip 91.99.25.251

Bug Description

When trying to authenticate with Claude Code CLI, the browser authentication flow fails with a 403 error. After entering the authentication code, I receive a "Request failed with status code 403" error.

Steps to Reproduce

1. Run the claude command to start Claude Code
2. Authentication flow begins and provides URL
3. After entering the authentication code, receive: "OAuth error: Request failed with status code 403"
4. Pressing Enter to retry results in the same error

Expected Behavior

Authentication should complete successfully and Claude Code should launch.

Actual Behavior

Authentication fails with "OAuth error: Request failed with status code 403" after entering the authorization code.

Additional Context

The exact error message is:

[losspamerianos]

Seems to be an broader issue with claude auth right now. Having the same problem with allready running installations (Max only, API Installation works) wich can not connect anymore to claude at all, only throwing:
`╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code research preview! │
╰───────────────────────────────────────────────────╯

Unable to connect to Anthropic services

Failed to connect to console.anthropic.com: Request failed with status code 403

Please check your internet connection and network settings.

Note: Claude Code might not be available in your country. Check supported countries at https://anthropic.com/supported-countries`

Even fresh installs did not change that.

[notnullxyz]

Same on API. I See #984

[webcodes-cz]

I tried using a proxy (without success), and after some experimentation, the command that finally worked for me was:claude config set --global env '{}' I’m not completely sure whether this was the actual fix or if the service had been updated by that point, but it was my last attempt before it started working. If you’re still seeing a 403 error (I was originally getting a 503 due to a mistaken HTTP_PROXY export, which might be a related but separate issue), give this command a try. Hopefully it helps!

[ozfrenz]

I'm still getting a 403 error on my Max plan after trying all suggested fixes. I'd appreciate assistance in finding a solution. This is occurring on a Hetzner cloud VM, accessed via SSH.

[rbrinkke]

Mee to Hetzner,

[hannes-marais]

Same issue, it was working fine via API from Hetzner Finland before transitioning to Claude Max, now it is just 403 all the time. Tried work arounds, no luck.

[Luowaterbi]

You can see . I solved the problem like you follow these instructions. But after that, I get " OAuth error: Request failed with status code 403".

Seems to be an broader issue with claude auth right now. Having the same problem with allready running installations (Max only, API Installation works) wich can not connect anymore to claude at all, only throwing:现在似乎是 claude auth 的一个更广泛的问题。在所有已经运行的安装（仅限 Max，API 安装有效）时遇到同样的问题，根本无法再连接到 claude，只能抛出： `╭───────────────────────────────────────────────────╮ │ ✻ Welcome to Claude Code research preview! ││ ✻ 欢迎来到 Claude Code 研究预览！│ ╰───────────────────────────────────────────────────╯

Unable to connect to Anthropic services无法连接到 Anthropic 服务

Failed to connect to console.anthropic.com: Request failed with status code 403无法连接到 console.anthropic.com：请求失败，状态代码为 403

Please check your internet connection and network settings.请检查您的互联网连接和网络设置。

Note: Claude Code might not be available in your country. Check supported countries at https://anthropic.com/supported-countries`注意：Claude Code 可能在您所在的国家/地区不可用。在 https://anthropic.com/supported-countries' 查看支持的国家/地区

Even fresh installs did not change that.即使是全新安装也没有改变这一点。

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.