{"version":"2.1.323","anchor":"name-constraint-tls-certificate-errors-now-explained","canonical_anchor":"name-constraint-tls-certificate-errors-now-explained","heading":"Clearer help for certificate name-limit errors when connecting","tier":"notice","area":"Certificates","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/name-constraint-tls-certificate-errors-now-explained","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer help for certificate name-limit errors when connecting\n\nFour certificate errors about name limits now come with a plain explanation and a suggested fix instead of a generic SSL error\n\n**What**\n\nClaude Code checks the security certificate of the server it connects to. Some certificates carry name constraints, rules about which website names they are allowed to vouch for. Four errors about these rules now come with a plain explanation and a suggested fix:\n\n- `PERMITTED_VIOLATION`\n\n- `EXCLUDED_VIOLATION`\n\n- `NAME_CONSTRAINTS_WITHOUT_SANS`\n\n- `UNSUPPORTED_CONSTRAINT_TYPE`\n\nBefore, these showed only a generic \"Unable to connect to API: SSL error\" message.\n\n**Why**\n\nThese errors often show up behind corporate networks that inspect secure traffic. The new message helps you see what went wrong and what to do about it.\n\n- Area: Certificates\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}