[BUG] claude blocks on startup due to ignoring proxy settings
Open 💬 2 comments Opened Jul 1, 2026 by bbakker2
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 takes 6 minutes or longer to respond to the first prompt.
What Should Happen?
Claude should respond within seconds.
Error Messages/Logs
❯ hello
* Beaming… (16m 55s)
⎿ Tip: Use /btw to ask a quic
Steps to Reproduce
- install code on a linux server behind a firewall, with network access via
HTTPS_PROXYenv var - configure in .claude/settings.json
{
"env": {
"CLAUDE_CODE_USE_BEDROCK": "1",
"ANTHROPIC_DEFAULT_SONNET_MODEL": "global.anthropic.claude-sonnet-5",
"ANTHROPIC_BEDROCK_ENDPOINT_URL": "https://redacted.bedrock-runtime.us-east-1.vpce.amazonaws.com"
},
"autoUpdatesChannel": "latest",
"awsAuthRefresh": "rm -rf ~/.aws/cli/cache/* 2>/dev/null; aws sts get-caller-identity --profile ai_dev || aws sso login --profile ai_dev --no-browser"
}
- start claude
- enter a prompt
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.185
Claude Code Version
2.1.197
Platform
AWS Bedrock
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
An strace shows that if awsAuthRefresh is defined Claude will try to connect directly to portal.sso.us-east-1.amazonaws.com, bypassing the HTTPS proxy.
If it is not defined Claude will not try that connection and respond promptly.
The value of awsAuthRefresh does not matter, e.g. "echo dummy" will cause the same behavior".
Refreshing aws auth with the setting above worked correctly in version 2.1.185 (latest stable)
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗