Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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.

Any suggestion would be greatly appriciated.

Relevant httpd conf for this:

Listen 443
NameVirtualHost *:443
<VirtualHost *:443>
ServerName XXX
SSLEngine on
SSLProtocol -all +TLSv1 +SSLv3
SSLCertificateFile "..."
SSLCertificateKeyFile "..."
SSLCertificateChainFile "..."
share|improve this question
It will be helpful to post your apache config. – Khaled Sep 17 '12 at 9:46
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 D Sep 17 '12 at 10:02
Why are you using NameVirtualHost? – David Schwartz Sep 17 '12 at 10:06
I'm getting an "Aborted" when trying https for the domain. – Benjamin Sep 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. – Benjamin Sep 17 '12 at 10:36
up vote 1 down vote accepted

Well it was fairly obvious once looking down to network: the network guys only opened 8181 (web service over SSL) but not 443. With that taken care of, Apache is working as expected.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.