Unknown SSL protocol error in connection to [example.com]
This issue is often caused by your server failing to correctly negotiate TLSv1.1 - which is the default secure protocol used by our monitoring system and currently regarded as the most secure option for initiating HTTPS sessions.
When you see this error, your server (or an intermediary load balancer / proxy) is likely to instead require TLSv1.0 (SSLv3) and fails to correctly complete negotiation process with our TLS client.
This can be verified by using a recent versions of OpenSSL (>= 1.0.1) and disabling TLSv1.1:
openssl s_client -connect www.example.com:443 -no_tls1_1
connects successfully, whereas:
openssl s_client -connect www.example.com:443
This is often triggered by a bug in some reverse proxies / load balancers; for example some versions of "F5 Networks BIG-IP load balancer" are known to suffer from this issue.
Not what you were looking for? Try a search:
Also in this topic:
- Can I monitor the entire page, including images, CSS, Flash, etc?
- Can I perform an HTTP POST and monitor the results?
- Can I monitor a multiple page transaction (e.g. login)?
- Can I specify an username and password for a web page (HTTP Auth)?
- Can I verify that a specific phrase or text appears on my website?
- Can I monitor SSL certificate expiration?
- Can I monitor web servers behind a load balancer?
- What does "Operation timed out after x with y bytes received" mean?
- What does "couldn't connect to host" mean?
- What does "name lookup timed out" mean?
- What does "empty reply from server" mean?