Bug Description
HTTPS_PROXY, https_proxy, http_proxy, <- none of these are used by antigravity claude proxy. These are configured in environment variable as shown in steps in reproduce.
Steps to Reproduce
- export HTTPS_PROXY=http://127.0.0.1:8891
- antigravity-claude-proxy start
Expected Behavior
All network requests should go via http proxy.
Actual Behavior
http proxy is identified but not actually used. See below logs. Direct network connections to google servers without using http proxy are blocked.
INFO [Proxy] Using proxy: http://127.0.0.1:8891
INFO [WebUI] Mounted at /
SUCCESS Server started successfully on port 8079
INFO [AccountManager] Loaded 2 account(s) from config
INFO [AccountManager] Using Hybrid (Smart Distribution) selection strategy
SUCCESS [Server] Account pool initialized: 2 total, 1 available, 0 rate-limited, 0 invalid
INFO [HybridStrategy] Using account: xxxx@gmail.com (2/2, score: 801.0)
WARN [AccountManager] Failed to refresh token for xxxx@gmail.com due to network error: fetch failed
ERROR [API] Error: Error: AUTH_NETWORK_ERROR: fetch failed
at getTokenForAccount (file:///opt/homebrew/lib/node_modules/antigravity-claude-proxy/src/account-manager/credentials.js:94:23)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async file:///opt/homebrew/lib/node_modules/antigravity-claude-proxy/src/server.js:740:27
WARN [API] Returning error response: 500 api_error - AUTH_NETWORK_ERROR: fetch failed
ERROR [POST] /v1/messages 500 (92ms)
Environment
- antigravity-claude-proxy version: 2.8.4
- Operating System: MacosX
- Node.js version: v26.0.0
Checklist
Please confirm:
- [ x] I've updated antigravity-claude-proxy to the latest version
- [ x] The bug exists in the latest version
- [ x] I'm using this proxy for personal development only
- [ x] I have an active Google Cloud project with Antigravity enabled
- [ x] This issue is not related to attempting commercial use or TOS violations
- [ x] I've reviewed the README troubleshooting section
Bug Description
HTTPS_PROXY, https_proxy, http_proxy, <- none of these are used by antigravity claude proxy. These are configured in environment variable as shown in steps in reproduce.
Steps to Reproduce
Expected Behavior
All network requests should go via http proxy.
Actual Behavior
http proxy is identified but not actually used. See below logs. Direct network connections to google servers without using http proxy are blocked.
INFO [Proxy] Using proxy: http://127.0.0.1:8891
INFO [WebUI] Mounted at /
SUCCESS Server started successfully on port 8079
INFO [AccountManager] Loaded 2 account(s) from config
INFO [AccountManager] Using Hybrid (Smart Distribution) selection strategy
SUCCESS [Server] Account pool initialized: 2 total, 1 available, 0 rate-limited, 0 invalid
INFO [HybridStrategy] Using account: xxxx@gmail.com (2/2, score: 801.0)
WARN [AccountManager] Failed to refresh token for xxxx@gmail.com due to network error: fetch failed
ERROR [API] Error: Error: AUTH_NETWORK_ERROR: fetch failed
at getTokenForAccount (file:///opt/homebrew/lib/node_modules/antigravity-claude-proxy/src/account-manager/credentials.js:94:23)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async file:///opt/homebrew/lib/node_modules/antigravity-claude-proxy/src/server.js:740:27
WARN [API] Returning error response: 500 api_error - AUTH_NETWORK_ERROR: fetch failed
ERROR [POST] /v1/messages 500 (92ms)
Environment
Checklist
Please confirm: