NameVirtualHost *:80 has no virtual hosts apache2 hosting multiple sites without DNS

tkmsr · 05-10-2010, 12:26 AM

Hi,
I have some problem in apache2 configuration.
I have two websites on same IP on LAN.i.e. 192.168.1.5
site1.abc.com
and abc.com
both have different document roots
for abc.com document root
/var/www/abc
and for site1.abc.com document root
/var/www/site1

the above sites are on a server which is accessible to me only via SSH.

Now on Lan if I do

http://192.168.1.5
I get abc.com
and if I do
http://192.168.1.5/abc
or http://192.168.1.5/site1

then in both cases I am getting abc.com which is alphabetically first vhost (that is also how apache2 serves)
What should I do to be able to access both the websites

following are vhosts in sites-enabled

for abc

Code:

  NameVirtualHost *:80
   <VirtualHost *:80>
        ServerAdmin webmaster@localhost
        ServerName abc.com
        ServerAlias www.abc.com
        DocumentRoot /var/www/abc
        <Directory /var/www/abc >
                Options FollowSymLinks
                AllowOverride None
        </Directory>
  
</VirtualHost>
~

and for site1.abc.com a separate file in /etc/apache2/sites-enabled

Code:

  NameVirtualHost *:80
   <VirtualHost *:80>
        ServerAdmin webmaster@localhost
        ServerName site1.abc.com
        ServerAlias site1.abc.com
        DocumentRoot /var/www/site1
        <Directory /var/www/site1 >
                Options FollowSymLinks
                AllowOverride None
        </Directory>
  
</VirtualHost>
~

What should I check in a few blogs I checked they said to mention in /etc/apache2/apache2.conf
ServerName.
But in this case what should I put I have two different websites or what other thing I have missed?
I am using Debian Lenny and apache2

John VV · 05-10-2010, 12:51 AM

it has been a while but.
http://httpd.apache.org/docs/2.2/vhosts/examples.html
you do not need the *:80 port in there
or you can set one to 80 and the other to 8080
"Running different sites on different ports."
but i use this
"Using the ServerPath directive"
and no-ip.com

bathory · 05-10-2010, 02:37 AM

Hi,

If you get the message you used to title your thread, then it looks like you don't have enabled vhosts.
What gives:

Code:

httpd -S

tkmsr · 05-10-2010, 02:43 AM

Unfortunately even before I could reply my system has crashed.So now I have even more problem but please let me know what you wanted to know from httpd -S and what according to you could have been possible reason of error.

Quote:

Originally Posted by John VV

it has been a while but.
http://httpd.apache.org/docs/2.2/vhosts/examples.html
you do not need the *:80 port in there
or you can set one to 80 and the other to 8080
"Running different sites on different ports."
but i use this
"Using the ServerPath directive"
and no-ip.com

John I had looked that link before you posted and had try to do the same you said and it had failed.So I posted the question any more clues.If you were to do as above of mine on different port then how would you give ServerPath I had read that but could not understand how to use it.
is it some thing like
ServerPath <Document Root of site>
in the link you say my doubt is I have two files in site-enabled directory should I keep ServerPath in both vhost files
site1.abc.com and abc.com

bathory · 05-10-2010, 02:56 AM

httpd -S should show you the vhosts that are running by your apache server
The error means that apache expects to find some vhosts, on port 80, but there are no vhosts defined.
I don't use Debian, but I know it uses a2ensite to create symlinks to the vhosts' definition files, so maybe those symlinks do not exist.

Regards

tkmsr · 05-10-2010, 04:02 AM

Quote:

Originally Posted by bathory

the vhosts' definition files, so maybe those symlinks do not exist.

Regards

Before it crashed the symlinks do existed.The vhost definition had some problem since when ever I restarted Apache it gave me error NameVirtualHost does not exist.
Inspite of the fact that there were separate vhost files for site1.abc.com and abc.com in sites-enabled directory.

http://httpd.apache.org/docs/2.2/vhosts/examples.html it says

Code:

In order to match the     correct virtual host a client must send the correct 
Host:     header. Old HTTP/1.0 clients do not send such a header and Apache  has    
 no clue what vhost the client tried to reach (and serves the request    
 from the primary vhost)

That is what was exactly happening.If I typed in browser http://192.168.1.5 I get abc.com which alphabetically was coming first.

Before it crashed I used a Firefox plugin Live HTTP headers
to see which header was going to webserver and it came to be HTTP 1.0 to which the above links says is a problem.I was surprised since I am using mozilla 3.6.3 if this has a problem then which brower sends correct HTTP :host header.

Or I was accessing the sites on LAN in a wrong way I mean I should have done some thing like
http://192.168.1.5/abc.com
and http://192.168.1.5/site1.abc.com

If ServerPath is to be used how is this to be used in my case ?
What I am not clear is /etc/apache2/sites-enabled/abc.com
/etc/apache2/sites-enabled/site1.abc.com
in both the files I should use ServerName or I should create a separate default file for this.

bathory · 05-10-2010, 04:30 AM

Quote:

That is what was exactly happening.If I typed in browser http://192.168.1.5 I get abc.com which alphabetically was coming first.

This is absolutely normal. Using an IP address is not the same as a vhost, so apache serves the 1st vhost.
Don't be confused with HTTP/1.0 headers and things like that. Since you get the " NameVirtualHost *:80 has no virtual hosts..." error, vhosts are not going to work.
When your box is up again, use the httpd -S to see if you have any hosts defined (I guess you don't) and maybe post the configs here for more help.

Regards

tkmsr · 05-10-2010, 04:32 AM

Quote:

Originally Posted by bathory

This is absolutely normal. Using an IP address is not the same as a vhost, so apache serves the 1st vhost.
Don't be confused with HTTP/1.0 headers and things like that. Since you get the " NameVirtualHost *:80 has no virtual hosts..." error, vhosts are not going to work.
When your box is up again, use the httpd -S to see if you have any hosts defined (I guess you don't) and maybe post the configs here for more help.

Regards

Ok.

jimwarr · 06-21-2010, 05:10 AM

I was having similar issues. Followed the instructions here and it worked like a charm, at library.linode.com/web-servers/apache/installation/ubuntu-10.04-lucid#configure_apache_for_named_based_virtual_hosting.

(This is my first post and I cannot do links.)

My issue was fat fingering in ports.conf. Once resolved, I removed and recreated the sites and life is good.

tkmsr · 06-21-2010, 10:27 AM

Fat fingering in ports.conf can you explain a bit what is that you are referring to and I guess this is the link you are referring to.