{"version":"2.1.317","anchor":"fetching-the-servers-certificate-chain-to-repair-tls-verifi","canonical_anchor":"fetching-the-servers-certificate-chain-to-repair-tls-verifi","heading":"Claude Code can repair some certificate errors by checking the server's certificates","tier":"notice","area":"Network","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/fetching-the-servers-certificate-chain-to-repair-tls-verifi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code can repair some certificate errors by checking the server's certificates\n\nOn certain certificate errors, Claude Code reads the server's certificate chain and restores a missing system certificate if one is needed\n\n**Unclear.** It is not clear whether this repair is switched on for everyone or depends on a setting.\n\n**What**\n\nA secure connection relies on a chain of certificates, digital credentials that prove a server is who it says it is. When checking that chain fails with one of these errors, Claude Code can now read the certificates the server presents:\n\n- `UNABLE_TO_GET_ISSUER_CERT_LOCALLY`\n\n- `UNABLE_TO_VERIFY_LEAF_SIGNATURE`\n\n- `UNABLE_TO_GET_ISSUER_CERT`\n\nIt checks whether the chain needs a certificate from your system that Claude Code's list of trusted authorities left out, and adds that certificate back if so. If you use an HTTP CONNECT proxy, it reads the certificates through it. It does not do this through an `https:\/\/` proxy. The check is skipped when `ANTHROPIC_UNIX_SOCKET` is set.\n\n**Why**\n\nThis may fix certificate errors on corporate networks where connections used to fail.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}