Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

After recently upgrading Apache2 to version 2.2.31 I found a strange behaviour in SSL VirtualHost setup.

A few of the website I'm hosting were showing the certificate for the default host even if the client was Server Name Identification aware, and this happened only with a few of them. This shows as the common Firefox's/Chrome's passport-warning about you being possibly scammed if you're browsing your home banking, but that simply was not the case.

To be clear, if server has its own SSL, attempting to access reports certificate for, but a few reported the correct certificate.

All sites are hosted on the same IP address, on port 443. The truth is that VirtualHosting works on the HTTP side and redirects SNI-aware clients to SSL automatically, so it's backward compatible with SNI-unaware clients.

Examining error logs for the offending VirtualHosts shown the following text

[Tue Dec 25 16:02:45 2012] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] (/path/to/

and in fact the vhost was correctly configured with SSLCertificateFile.

The question is obvious: how to fix that?

share|improve this question
up vote 24 down vote accepted

It happens that it could be a bug in the most recent version of Apache.

Solution 1: downgrade to the latest stable

Solution 2: edit listen.conf

Replace Listen *:443 (or Listen 443 according to your setup) with Listen *:443 http


share|improve this answer
Thank you for pointing this out! You saved me a lot of wondering around... I wonder why apache is making life harder!? – tftd Mar 18 '13 at 22:20
Solution 2: should that be httpd.conf not listen.conf – zzapper Mar 17 at 15:00

Another solution for this is to ensure that all of your :443 vhosts include the TLS configuration.

This problem was recently introduced in Debian wheezy and I got the solution from

share|improve this answer

I had the same exact problem, and what worked for me was unbelievably simple

edit /etc/apache2/ports.conf (for ubuntu, or httpd.conf )

change "Listen 443" to "Listen 443 http" under ssl_module

share|improve this answer
This is already in the accepted answer. – Sven Jun 28 '15 at 8:13
The accepted answer seems outdated. This answer was more useful and accurate. +1 – P Magunia Mar 26 at 1:42
This answer is applicable for apache on my apache2.4 lamp stack, ubuntu. Other answer is "listen.conf" - should be ports.conf – Nick Jun 26 at 2:40

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.