Capturing the Source IP?

Site is https.

The problem you are having is that to apply an HTTP profile to an HTTPS site requires a client SSL profile. Otherwise all your connections will get reset. I would consider SSL offloading, but at a minimum you do need a client SSL profile. If you need end to end encryption you can add a server SSL profile.

Would the default clientssl work for SSL Profile (Client) I just added this one and site wont respond.

Yes, the default client SSL profile will "work", but you will get a cert error in the browser. Even with the cert error you can test the connectivity to the site after accepting the warning. In Production you will need to put certificate and private key for the site loaded on the Big-IP. Don't know if this is the forum to exhaustively explain SSL profiles, but the links below should help. If you are going to SSL offload(client SSL only) you backedend servers will need to listen on HTTP not HTTPS. If you want the connection to the backend servers to be HTTPS, you will also require a server SSL profile. https://support.f5.com/kb/en-us/solutions/public/14000/700/sol14783.html https://support.f5.com/kb/en-us/solutions/public/14000/800/sol14806.html https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ssl-administration-11-6-0/4.html

Thank you for all the help. Looks like the only way for the siteto work is to add the SSL Profile(client) and SSL Profile(Server) defaults. But I will start reading the links and start looking into adding the Cert and PK. Thanks again.