Forum Discussion
Hello, if curl and health check is working, but not server side connections, please debug this further with tcpdump/ssldump to see what's actually going on. Usually the fault lies within missing serverssl profiles (if ssl is used), or the fact that both curl and monitors will use a non-floating self-IP, while serverside connections by default will chose a floating self-IP.
In regards to non-floating Self-IPs, please check that you have a valid route on your internal interface towards 10.1.2.0/24, if not the BIG-IP will actually use the MGMT interface for curl and monitors, and that would most certainly fail for serverside connections.
Another thing to bear in mind is the growing use of SNI, and while curl passes this correctly, a https monitor does not support SNI, so you would have to use a external monitor for this.