Back to Articles
Troubleshooting2026-06-18•4 min read•CSR.plus Team

SSL Handshake Failed: Causes and How to Fix It

SSL Handshake Failed: Causes and How to Fix It

An SSL/TLS handshake failure (the industry still commonly says "SSL") means the client and server could not agree on the parameters needed to open an encrypted connection. The most common causes are a missing intermediate certificate, a cipher-suite or TLS-version mismatch, an incorrect hostname/SNI, or a network device dropping the handshake. In most cases the problem is fixed within minutes by deploying the full chain, enabling TLS 1.2/1.3, and confirming port 443 is reachable. Use the SSL Checker to see exactly what the server sends.

What a TLS handshake does

During the handshake the client and server negotiate the protocol version, cipher suite, and certificate chain. If any step cannot be agreed, the connection is terminated. The handshake completes parameter negotiation before certificate validation, so a handshake failure is often about protocol, cipher, or network mismatch rather than the certificate itself.

Why handshakes fail

Failures usually fall into five buckets: an incomplete chain (the server sends only the leaf), no shared cipher suite, a TLS version the client does not support, a hostname/SNI mismatch, or a firewall/NAT silently dropping the ClientHello. Diagnose in the order expiry → hostname → chain → protocol/cipher → network for the fastest result.

How to read the error

On the server run openssl s_client -connect yourdomain.com:443 -servername yourdomain.com and read the output: Verify return code: 0 means the chain is fine; unable to get local issuer certificate points to a missing intermediate; no peer certificate available or an empty line after CONNECTED means the server never finished the handshake — usually a protocol or cipher issue. Browser console errors add the client-side view.

Step 1: Run a quick diagnostic with openssl

Run openssl s_client -connect yourdomain.com:443 -servername yourdomain.com and watch the Verify return code and whether a certificate is returned. Compare it with the SSL Checker so the server and the public view agree.

Step 2: Check and deploy the full chain

Download the CA's full chain bundle and concatenate the leaf and intermediates in the correct order. Most failures are simply the intermediate not being sent with the leaf. Verify completeness with the Certificate Decoder.

Step 3: Align TLS versions and cipher suites

Enable TLS 1.2 and TLS 1.3 on the server and disable anything below 1.2 (TLS 1.0/1.1 were deprecated by browsers at the end of 2020). Offer common suites such as TLS_AES_256_GCM_SHA384 (TLS 1.3) or ECDHE-RSA-AES256-GCM-SHA384 (TLS 1.2).

Chain bundle = leaf + intermediates only; do not append the root certificate.

Step 4: Verify hostname and SNI

Confirm the certificate covers the exact hostname in its SAN and that SNI is enabled on the server. An error on a single hostname usually means an SNI/hostname mismatch.

Step 5: Rule out network and firewall issues

Confirm port 443 is open and that a load balancer or CDN is not terminating TLS with its own settings. Test from another network or capture packets to see whether the ClientHello is being dropped.

Troubleshooting checklist

SymptomLikely causeFix
Verify return code: 20/21 or unable to get local issuer certificateMissing intermediate certificateDeploy leaf + intermediates in order; re-check with the Certificate Decoder
No certificate returned / empty line after CONNECTEDServer never finished the handshake (protocol/cipher)Enable TLS 1.2/1.3 and add common cipher suites
Works with curl but fails in an old browserClient lacks the negotiated TLS versionSet TLS 1.2 as the minimum; retire TLS 1.0/1.1
Fails only for one hostnameSNI / hostname mismatchEnsure the cert covers that hostname and SNI is on
Intermittent, on-and-off failuresFirewall/NAT dropping large ClientHello or blocking 443Allow 443; test from another network; capture packets if needed

Related articles

FAQ

Why does the handshake fail in a browser but work with curl?

Different clients support different TLS versions and cipher suites. If curl works but an old browser fails, the client cannot speak the negotiated TLS version — set TLS 1.2 as the minimum to cover virtually all modern clients.

Can a firewall cause a handshake failure?

Yes. Some firewalls and NAT devices silently drop large ClientHello packets or block the TCP port. Test on a non-standard port or capture packets to confirm the handshake is interrupted before it reaches the server.

Are TLS 1.0/1.1 still usable?

Not recommended. TLS 1.0 and 1.1 were deprecated by major browsers at the end of 2020 and are no longer negotiated by modern clients by default. Enable at least TLS 1.2, and prefer TLS 1.3.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles