TLS · Foundations
Read a TLS failure
TLS protects the connection before HTTP begins. A failure can concern the requested name, the certificate chain, protocol negotiation, or the endpoint selected by a proxy.
What the handshake establishes
The client and server choose cryptographic parameters, the server proves its identity with a certificate, and both sides derive session keys. Only after this succeeds can an HTTPS request be exchanged.
An open TCP port proves only that something accepted a network connection. It does not prove that TLS, HTTP, or the application works.
Four questions to answer
- Which name did the client request?Certificate validation is based on the hostname, not merely the destination address.
- Which certificate was presented?Check its subject alternative names, validity period, issuer, and full chain.
- Which protocol was negotiated?Client and server need a compatible TLS version and cipher suite.
- Which application protocol followed?ALPN commonly selects HTTP/2 or HTTP/1.1. The selected backend must actually support it.
SNI and ALPN are different
Server Name Indication (SNI) carries the intended hostname during the handshake so a shared endpoint can choose the right certificate or route. Application-Layer Protocol Negotiation (ALPN) chooses the protocol to use after TLS, such as h2 or http/1.1.
A router can therefore choose the correct virtual host by SNI and still fail later if the selected application protocol is unsupported downstream.
Avoid false fixes
Disabling certificate verification hides evidence and creates a security problem; it does not repair the endpoint. Changing DNS, certificates, and proxy routing together also destroys the comparison you need. Capture the presented certificate and negotiated parameters first, then change one layer.