What’s the point of a Max plan if you can’t use it?
At least git still works without GitHub. (I guess normal chat works so if paying for Claude Code, there is a conciliation prize?)
The funny part is that the support AI is terrible!
CC reports internal API errors, and the support AI can not let go of the idea that it must be a VPN on my side (no network API issues, really AI for real please please believe me).
Steven: no. this is an error between CC on web and api for provisioning a dev environment, and so the calls are entirely without anthropic not between me and anthropic like the app or cli might do
Steven • 16h
and the cli is fine
Steven • 16h
You’re right to call that out: in Claude Code on the web, the “API Error” you’re seeing is coming from the cloud session’s call to our API (not a direct browser-to-Anthropic request), so it’s not the same as a local CLI connection issue.
Since your CLI works, this is most likely either:
a network block (firewall, proxy, VPN) that prevents the cloud session from reaching api.anthropic.com, or
an organization IP allowlist that blocks cloud sessions because they call the API from our infrastructure (not your network).
Quick check: are you on a corporate network with IP allowlisting or a required proxy?
sroussey•1h ago
At least git still works without GitHub. (I guess normal chat works so if paying for Claude Code, there is a conciliation prize?)
The funny part is that the support AI is terrible!
CC reports internal API errors, and the support AI can not let go of the idea that it must be a VPN on my side (no network API issues, really AI for real please please believe me).
Steven: no. this is an error between CC on web and api for provisioning a dev environment, and so the calls are entirely without anthropic not between me and anthropic like the app or cli might do Steven • 16h and the cli is fine Steven • 16h You’re right to call that out: in Claude Code on the web, the “API Error” you’re seeing is coming from the cloud session’s call to our API (not a direct browser-to-Anthropic request), so it’s not the same as a local CLI connection issue.
Since your CLI works, this is most likely either: a network block (firewall, proxy, VPN) that prevents the cloud session from reaching api.anthropic.com, or an organization IP allowlist that blocks cloud sessions because they call the API from our infrastructure (not your network). Quick check: are you on a corporate network with IP allowlisting or a required proxy?