Why does a TLS handshake fail?
A TLS handshake fails when the client and server can't agree on how to encrypt, or one doesn't trust the other. The side that gives up sends a fatal alert, such as handshake_failure, protocol_version, or unknown_ca, and the alert name is the best clue to the cause.
What it looks like in the packets
- A Client Hello, then a fatal alert (level 2) instead of encrypted application data.
- The alert name and which side sent it.
- The app shows a security or SSL error.
Common causes
- No shared TLS version: an old server (TLS 1.0/1.1) or an old client.
- No shared cipher suite.
- An expired, self-signed, or wrong-name certificate (alerts like bad_certificate or unknown_ca).
- A proxy or security product intercepting the connection.
What to check
- Read the alert name and who sent it: the server rejecting the client, or the client rejecting the server.
- Compare the versions offered in the Client Hello with what the server supports.
- Test the server with: openssl s_client -connect host:443 -servername host.
Wireshark display filters
tls.alert_message.level == 2tls.handshake.type == 1
How Blame Finder flags it
High when no connection to that server succeeded in the capture; Warning when some did. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.