{"version":"2.1.319","anchor":"ca-cert-chain-read-now-reports-an-unsupported-proxy-configur","canonical_anchor":"ca-cert-chain-read-now-reports-an-unsupported-proxy-configur","heading":"Certificate check now skips proxies it cannot use and says how to fix it","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/ca-cert-chain-read-now-reports-an-unsupported-proxy-configur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Certificate check now skips proxies it cannot use and says how to fix it\n\nIf only unusable proxy variables such as ALL_PROXY are set, Claude Code skips reading the server's certificates and logs how to fix the setup\n\n**What**\n\nClaude Code can read the chain of certificates a server presents, which helps work out why a secure (TLS) connection is failing. Before, this read went through whatever proxy variable was set. Now it first checks whether any proxy variable is one it can actually use.\n\nIf the only proxy variables set are ones the read cannot use, for example `ALL_PROXY`, Claude Code skips the read and writes a note to its log. The note suggests either:\n\n- setting `https_proxy` to a complete `http:\/\/` URL\n\n- adding the extra certificate to `NODE_EXTRA_CA_CERTS`\n\nThe read can also now run after a request to the model.\n\n**Why**\n\nBehind a company proxy, secure connections often fail because of certificates the proxy adds. The log note points to the two settings that usually fix this, instead of the read failing quietly.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}