{"version":"2.1.311","anchor":"connection-errors-append-network-hints","canonical_anchor":"connection-errors-append-network-hints","heading":"Connection errors now suggest what to check","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/connection-errors-append-network-hints","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Connection errors now suggest what to check\n\nWhen Claude Code cannot reach Anthropic's API, the error now points to your proxy, your ANTHROPIC_BASE_URL gateway, or a VPN or firewall\n\n**What**\n\nWhen Claude Code fails to connect to Anthropic's API, the error message used to show only the raw error. It now adds a hint:\n\n- If you have set a proxy, or a gateway through `ANTHROPIC_BASE_URL`, it tells you to check that.\n\n- Otherwise it says: \"A VPN, firewall, or security software can cause this. Check those or switch networks, then try again.\"\n\nA gateway is a server placed between Claude Code and the API. The hint is added to general connection errors when Claude Code talks to Anthropic directly. It is not added when Claude Code connects through a Unix socket, which is a local connection between programs on the same machine.\n\n**Why**\n\nA bare connection error gives you nothing to act on. The hint names the likely causes, so you know where to look first.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}