HTTPS health monitoring on rackspace cloud load balancer

Solution 1:

When you create a Rackspace Cloud Load Balancer you configure the protocol and port to be balanced:

Now you need to edit the configuration to support your new protocol (HTTPS). You have a couple of options:

Serving HTTPS directly from the servers

If you are serving HTTPS on port 443 from the servers themselves and just using the LB to pass the traffic, rather than offloading SSL to the LB, you need to edit the load balancer to use that port and protocol.

You should also look at your node list for the node IP addresses and test from one node to the other to make sure your site is indeed reachable on the expected port.

Serving HTTPS from the Load Balancer

If instead of hosting your certificate directly on your servers you want to host it on the LB, set your protocol on the LB back to HTTP on port 80, and edit the Secure Traffic (SSL) setting in Optional Features:

Your load balancer will cost a bit more if you do this, but it may also serve to solve your issue if you are having trouble configuring your servers to serve HTTPS over port 443 directly.