Forum Discussion
I think there is misunderstanding about client authentication. Also, your configuration is missing a client ssl profile, and because you are using a HTTP profile that is never going to work.
Looking the connection between the F5 and the backend server, F5 is the client and backend server the server. Majority of SSL/TSL connections don't use client authentication, so unless you need a certificate in your pc when you connect directly to the server, you don't need to do client authentication in the server ssl profile.
Resuming, add a client ssl profile that has the same certificate and key that the server uses, use the default server ssl profile (no configuration needed for this profile).
If you have a HTTP profile, the F5 must be able to decrypt the traffic to see HTTP data before it opens the server side connection. In your case, F5 only sees encrypted data, and never opens the server side connection.
If you still have problems with a client ssl and server ssl, remove HTTP/clientssl/serverssl profiles. With this configuration, the SSL handshake is between the client and the backend server. So, you can verify if there is any other problem like networking. Also, if you don't need to manipulate the HTTP data, like using cookie persistence, a configuration without these 3 profiles is a valid setup, with the advantage that changes to certificate does not requires change to F5 configuration.
If you want understand more about how this works, read this article:
https://devcentral.f5.com/articles/ssl-profiles-part-1