I ran in what seems to see a case with little to no documentation.
I'm trying to serve content sitting behind Apache 2.2 via HTTPS. This Apache server is listening on two IP addresses, one static assigned to the node and a second "floating" IP used by the active node of the cluster.
The domain A record is pointing to this floating IP, in HTTP it's working fine.
The server is setup with NameVirtualHost *:443 and the section covers the cert info and SSL requirement.

But in HTTPS I can only access the server by requesting the IP of the server, not the domain or floating IP. Which of course leads to a certificate domain mismatch and by passes the redundancy of a floating IP.

It will be helpful to post your apache config.
–
KhaledSep 17 '12 at 9:46

2

When you say you can't access it, what exactly do you mean? What happens - do you get a timeout, do you get "connection refused", or anything else? Does anything appear in the logs - if so, what?
–
Jenny DSep 17 '12 at 10:02

Why are you using NameVirtualHost?
–
David SchwartzSep 17 '12 at 10:06

I'm getting an "Aborted" when trying https for the domain.
–
BenjaminSep 17 '12 at 10:34

I cannot use VirtualHost against a static IP since the domain is mapped against a floating IP which might be moved on the fly to another machine.
–
BenjaminSep 17 '12 at 10:36