Linux – Apache2 Startup warning: NameVirtualHost :80 and NameVirtualHost :443 has no VirtualHosts

apache-2.2linux

I have a super simple Apache setup on a SUSE box that is giving me the error in the title. Any ideas what it could be? I have checked all the conf files and found no duplicate NameVirtualHost directives anywhere…

My listen.conf file looks like this (some goodies ommitted):

NameVirtualHost *:80
NameVirtualHost *:443

and my vhost.conf file looks like this (some goodies ommitted):

<VirtualHost *:443>
        ServerName subdomain.somedomain.com
        ## OTHER STUFF ##
</VirtualHost>

<VirtualHost *:443>
        ServerName anothersubdomain.somedomain.com
        ## OTHER STUFF ##
</VirtualHost>

<VirtualHost *:80>
        ServerName someotherserver.somedomain.com
        ## OTHER STUFF ##
</VirtualHost>

Best Answer

It looks like you need to enclose your ServerName somedomain.com ## OTHER STUFF ## inside

<VirtualHost *:80>
</VirtualHost>

tags. The error is saying that you have no virtual hosts defined for port 80 and 443. Change the *:80 to *:443 for an ssl host.

Related Solutions

Apache Warning – How to Fix ‘NameVirtualHost *:80 Has No VirtualHosts’ Warning

Change

<VirtualHost *>

to read

<VirtualHost *:80>

Or its (NameVirtualHost *:80) added twice in your apache2 Confing file. ( By Default its added in ports.conf file )

This should clear the error.

Aside: you shouldn't ignore this error. Apache's config, especially when globbing virtual hosts (eg Include /etc/httpd/vhosts.d/*) is not stable. That means you don't control the order of loading the hosts explicitly so the default vhost for an IP becomes the one that is loaded first, which can lead to unintended consequences.

One example of this is the default vhost for an IP will also be available on that IP, rather than its name. This can cause information to leak onto google referring to your sites IP rather than name, which can be confusing for customers.

The NameVirtualHost error above can be a hint that apache has loaded things in a non optimal way, so you shouldn't ignore it.

Centos – My VirtualHosts overlap and the NameVirtualHost has no VirtualHosts

Are you sure your NameVirtualHost directive is actually being "seen" by Apache? That's a common mistake we see

Hey, try this command:

/usr/sbin/apache2ctl -t -D DUMP_VHOSTS

Here's what I see from it on a server that's working properly for me:

VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:*                    is a NameVirtualHost
         default server loghost.example.com (/etc/apache2/vhosts.d/10_loghost.example.com.conf:4)
         port * namevhost loghost.example.com (/etc/apache2/vhosts.d/10_loghost.example.com.conf:4)
         port * namevhost netflow.example.com (/etc/apache2/vhosts.d/20_netflow.fluent.com.conf:4)
         port * namevhost licensewatch.example.com (/etc/apache2/vhosts.d/40_licensewatch.example.com.conf:8)
Syntax OK

Best Answer

Related Solutions

Apache Warning – How to Fix ‘NameVirtualHost *:80 Has No VirtualHosts’ Warning

Centos – My VirtualHosts overlap and the NameVirtualHost has no VirtualHosts

Related Topic