Forum Discussion
Handshake SSL failed for the HTTPS monitor
I've seen this before. It may be an issue with openssl on BigIP or the SSL stack on your server. In this case, the SSL stack on your server doesn't like the version differences in the handshake envelope. Even though it is "complaint" by RFC standards, I've seen more than one server fail handshakes with this behavior. As you can see the monitor is sending a version TLS 1.2 handshake inside of a Client Hello mark with version TLS 1.0. Your server probably wants those to match. Unfortunately, I'm not sure if there's a way on your end to change that behavior in the monitor.
- Adrian_PJul 03, 2015
Nimbostratus
Hi Brad, I am having the same issue while configuring HTTPS monitor. The Client Hello from the F5 monitor have mismatched TLS version on the Handshake (TLS 1.0) and Handshake protocol (TLS 1.2) and the server send a RST, ACK straight away. Is this behaviour is going to be fixed in the next release ? We are running 11.6.0 Engineering Hotfix Version 4.107.420 - DMA_95966May 21, 2016
Nimbostratus
Hi Brad , Just checking if there is any solution for this, i am also facing same issue .
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com