{"version":"2.1.273","anchor":"ssl-certificate-errors-now-include-a-docs-link-and-a-plainer","canonical_anchor":"ssl-certificate-errors-now-include-a-docs-link-and-a-plainer","heading":"SSL certificate errors now include a docs link and a plainer explanation","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/ssl-certificate-errors-now-include-a-docs-link-and-a-plainer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### SSL certificate errors now include a docs link and a plainer explanation\n\nSSL certificate errors now explain the likely corporate-proxy cause and link to setup docs\n\n**What**\n\nWhen Claude Code fails to connect because of a certificate verification error (such as an unverifiable or self-signed certificate), the error message now explains that this usually happens because of a corporate proxy that inspects TLS traffic, or a private certificate authority gateway. It points to the `NODE_EXTRA_CA_CERTS` environment variable as the fix, and links to the network configuration documentation page.\n\n**Why**\n\nThis makes it much easier to understand and resolve a common cause of connection failures on corporate networks, instead of just seeing a cryptic certificate error.\n\n- Area: Internals\n- Names: `NODE_EXTRA_CA_CERTS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}