httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Andersson" <>
Subject Re: [users@httpd] Virtual host causing problems with default server
Date Thu, 10 Jul 2003 13:45:15 GMT
Robert Moskowitz wrote:
> I originally did not use the command:
> NameVirtualHost
> I added it both trying:
> NameVirtualHost
> and
> NameVirtualHost
> with no change.

Does and resolve to different IPs? If not, why do you
have them both? NameVirtualHost tells Apache which IP/port combinations to
use for name-based virtual hosting. It is always prefered to use the IP
instead of hostname:

> I tried adding:
> <VirtualHost>
>      ServerAdmin
>      DocumentRoot "D:/Pages"
>      ServerName
>      ErrorLog logs/error.log
>      CustomLog logs/access.log common
> </VirtualHost>
> And this produced some error that flashed too quick across the screen, but
> something like
> 'this conflicts with the default server'

If this was in addition to the other VHost, the problem is that you have
given two VHosts the same ServerName, which, of course, is conflicting.

> and still no access to

Is defined as a virtual host? If that is your "main server" and it
isn't sitting on a different IP than your virtual hosts, you won't ever
reach, due to reasons previously explained. If you are using name-based
virtual hosting, you must define each site/domain as a virtual host. With a
few exceptions, once you start adding virtual hosts, your "main
configuration" only becomes the default configuration for the virtual hosts;
not a host of its own.

If you still have problems, please summarize your case again, since this has
become a bit confusing.

Robert Andersson

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message