{"version":"2.1.296","anchor":"gateway-reports-a-clearer-tls-error-for-certificate-name-mis","canonical_anchor":"gateway-reports-a-clearer-tls-error-for-certificate-name-mis","heading":"Clearer gateway error when a certificate is for the wrong name","tier":"notice","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/gateway-reports-a-clearer-tls-error-for-certificate-name-mis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Clearer gateway error when a certificate is for the wrong name\n\nGateway connections now say the certificate is for another name instead of showing a generic secure-connection error\n\n**What**\n\nTLS is the encryption used for secure connections, and it relies on a certificate that names the server. When a gateway connection fails because the certificate is for a different name than the address being contacted, Claude Code now says \"TLS connection not accepted: the certificate is for another name\". Before, this case showed a generic TLS message with the raw error included.\n\n**Why**\n\nThe message tells you plainly what went wrong, which makes a mistyped or misconfigured gateway address easier to spot.\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}