{"version":"2.1.311","anchor":"ca-certificate-handling-clearer-errors-and-dedupe-of-node-e","canonical_anchor":"ca-certificate-handling-clearer-errors-and-dedupe-of-node-e","heading":"Clearer certificate errors and no duplicate NODE_EXTRA_CA_CERTS entries","tier":"notice","area":"Network Proxy","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/ca-certificate-handling-clearer-errors-and-dedupe-of-node-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Clearer certificate errors and no duplicate `NODE_EXTRA_CA_CERTS` entries\n\nClaude Code now explains when no usable CA certificate is found, and stops re-adding `NODE_EXTRA_CA_CERTS` certificates that are already trusted\n\n**What**\n\nCA certificates tell Claude Code which secure connections to trust. Two new error messages appear when it cannot find one to use:\n\n- \"No certificate authority to trust: no usable CA certificate was found\"\n\n- that every CA certificate found is on the CLI's deny list\n\nIf every certificate in `NODE_EXTRA_CA_CERTS` is already in the trusted store, Claude Code no longer adds them again, and the log says each is listed once. Before, it always added them.\n\n**Why**\n\nIn setups without built-in trusted certificates, you now get an error that says what is wrong instead of an unexplained connection failure.\n\n- Area: Network Proxy\n- Names: `NODE_EXTRA_CA_CERTS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}