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

Actually, I Have looked around for a few hours now, but I can't get this to work. The main problem I'm having is that only one out of two sites works.

I have my website which will mostly be used for an app. It's called . will have three main sites:

  • <- Homepage for the app.
  • <- Login endpoint for my API (needs SSL)
  • <- Main endpoint for my API (needs SSL).

If you attempt to access it works. It will throw you a 403 error and a JSON output, but that's fully intentional.

If you try to access however, the site simply doesn't load. Chrome complains with:

The webpage at might be temporarily down or it may have moved permanently to a new web address. Error code: ERR_TUNNEL_CONNECTION_FAILED

But the website IS there.

If you try to access or any other HTTP site, it connects fine. It just doesn't like dealing with more than one HTTPS websites, it seems.

The VirtualHost for looks like this:

<VirtualHost *:443>
    DocumentRoot /var/www/
    SSLEngine on
    SSLCertificateFile /certificates/STAR_atajosapp_com.crt
    SSLCertificateKeyFile /certificates/star_atajosapp_com.key
    SSLCertificateChainFile /certificates/PositiveSSLCA2.crt
</VirtualHost> Looks very similar:

<VirtualHost *:443>
    DocumentRoot /var/www/
    SSLEngine on
    SSLCertificateFile /certificates/STAR_atajosapp_com.crt
    SSLCertificateKeyFile /certificates/star_atajosapp_com.key
    SSLCertificateChainFile /certificates/PositiveSSLCA2.crt

Now I have found many websites that talk about possible solutions. At first, I was getting a message like this:

_default_ VirtualHost overlap on port 443, the first has precedence

But after googling for hours, I managed to solve it by editing both apache2.conf and ports.conf. This is the last thing I added to ports.conf:

<IfModule mod_ssl.c>
NameVirtualHost *:443
    # SSL name based virtual hosts are not yet supported, therefore no
    # NameVirtualHost statement here
    NameVirtualHost *:443
    Listen 443

Still, right now only and are working. I still can't access When I check the error log, I see this:

Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)

I don't know what else to do to make both sites work fine on this. I purchased a Wildcard SSL certificate from Comodo that supposedly secures *, so after hours trying and googling, I don't know what's wrong anymore.

Any help will be really appreciated.

EDIT: I just ran the apachectl -t -D DUMP_VHOSTS command and this is the output. Can't make much sense of it...:

root@atajosapp:/# apachectl -t -D DUMP_VHOSTS
apache2: Could not reliably determine the server's fully qualified domain name, using for ServerName
[Thu Nov 07 02:01:24 2013] [warn] NameVirtualHost *:443 has no VirtualHosts
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:443                  is a NameVirtualHost
         default server (/etc/apache2/sites-enabled/
         port 443 namevhost (/etc/apache2/sites-enabled/
         port 443 namevhost (/etc/apache2/sites-enabled/
*:80                   is a NameVirtualHost
         default server (/etc/apache2/sites-enabled/000-default:1)
         port 80 namevhost (/etc/apache2/sites-enabled/000-default:1)
share|improve this question
Does your browser's connection use a proxy server? – Shane Madden Nov 7 '13 at 2:08
No proxy configurations that I am aware of. I just tried to access from two different devices though (one of them with a different internet line), and now chrome gives ERR_NAME_NOT_RESOLVED – Andy Ibanez Nov 7 '13 at 2:12
Is that name set up in DNS? Does it resolve to the correct IP with a command line nslookup? – Shane Madden Nov 7 '13 at 2:16
... Oh my god I should have check that before anything. Hold on a sec, checking now... – Andy Ibanez Nov 7 '13 at 2:18
Aaand as of right now, I'm the biggest idiot in the planet, haha! Thanks for pointing that out. For whatever reason it didn't occur to me that may be the problem. I completely forgot to set auth in my DNS settings. I will add it now and see how it goes. – Andy Ibanez Nov 7 '13 at 2:20

Your Answer


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

Browse other questions tagged or ask your own question.