SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
TLS 24 errors

TLS & SSL Certificate Errors

Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Understanding TLS errors

TLS errors have a small number of root causes: the certificate is expired, the hostname does not match any SAN entry, the chain is incomplete (the server did not send its intermediates), the issuing CA is not trusted by this client, or the two sides share no cipher or protocol version. The incomplete-chain case is the most deceptive, because browsers often paper over it with cached intermediates while curl, Java and Go fail.

How to debug TLS errors

  1. Inspect the live handshake: openssl s_client -connect host:443 -servername host -showcerts. It shows the full chain the server actually sends.
  2. Check dates and SANs: openssl x509 -noout -dates -subject -ext subjectAltName. The Common Name is ignored by modern clients: only SANs matter.
  3. If browsers work but curl or your language runtime does not, suspect a missing intermediate. Browsers cache intermediates; other clients do not.
  4. Verify the trust store the failing client uses. Containers frequently ship without ca-certificates installed, and Java, Node and Python each have their own store.
  5. For protocol or cipher errors, check the negotiated version and the server's supported list. TLS 1.0 and 1.1 are disabled by default in current clients.

Tools worth reaching for

  • openssl s_client
  • openssl x509 -noout -text
  • curl -vI
  • testssl.sh
  • sslyze

All 24 TLS errors

Other categories