[BUG] API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}} · Please run /login
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?
What Should Happen?
response
Error Messages/Logs
Steps to Reproduce
send hello
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.0.28
Claude Code Version
2.0.31
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
No response
Found 3 possible duplicate issues:
- https://github.com/anthropics/claude-code/issues/8747
- https://github.com/anthropics/claude-code/issues/2040
- https://github.com/anthropics/claude-code/issues/10591
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
cli same,
I have already tried executing the command irm https://claude.ai/install.ps1 | iex, but reinstalling and logging in still doesn't work on Windows 11.
The cause of the issue has been identified: this version of Claude's native binary does not read the proxy configuration in the setting.json file. It is a bug.
The npm version works, while native version doesn't
To resolve this issue, you can try the following steps:
- Uninstall the current npm version.
- Delete the Claude-related files in the user directory (or back them up).
- Install the native version.
- Re-login.
I tested and it works fine.
I'm facing the same issue with the native version v2.0.55.
The HTTP_PROXY and HTTPS_PROXY environment variables in ~/.claude/settings.json don't work.
However, the following command works for me with the native version:
HTTP_PROXY=<YOUR_HTTP_PROXY> HTTPS_PROXY=<YOUR_HTTPS_PROXY> claude
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.