All domains showing same web content in linode
I'm really confused. What do I do?
8 Replies
For an example of what it's supposed to be:
[Mon May 19 06:50:27 2008] [error] VirtualHost xxx.xxx.xxx.xxx:0 – mixing * ports and non-* ports with a NameVir
tualHost address is not supported, proceeding with undefined results
[Mon May 19 06:50:27 2008] [error] VirtualHost xxx.xxx.xxx.xxx:0 – mixing * ports and non-* ports with a NameVir
tualHost address is not supported, proceeding with undefined results
[Mon May 19 06:50:27 2008] [warn] NameVirtualHost xxx.xxx.xxx.xxx:80 has no VirtualHosts
[Mon May 19 06:50:27 2008] [warn] NameVirtualHost *:0 has no VirtualHosts
[Mon May 19 06:50:27 2008] [warn] NameVirtualHost *:0 has no VirtualHosts
[Mon May 19 06:50:37 2008] [error] VirtualHost xxx.xxx.xxx.xxx:0 – mixing * ports and non-* ports with a NameVir
tualHost address is not supported, proceeding with undefined results
[Mon May 19 06:50:37 2008] [error] VirtualHost xxx.xxx.xxx.xxx:0 – mixing * ports and non-* ports with a NameVir
tualHost address is not supported, proceeding with undefined results
[Mon May 19 06:50:37 2008] [warn] NameVirtualHost xxx.xxx.xxx.xxx:80 has no VirtualHosts
[Mon May 19 06:50:37 2008] [warn] NameVirtualHost *:0 has no VirtualHosts
[Mon May 19 06:50:37 2008] [warn] NameVirtualHost *:0 has no VirtualHosts
xxx.xxx.xxx.xxx is my IP.
Thanks.
Also, I don't know where the xxx.xxx.xxx.xxx:0 and *:0 are coming from–Apache shouldn't be listening on port 0 normally.
Any further help will be appreciated.
Thanks.
<virtualhost xx.xx.xx.xx:80="">DocumentRoot /var/www/html
<directory var="" www="" html="">Options Indexes IncludesNOEXEC FollowSymLinks
allow from all
AllowOverride All</directory></virtualhost>
Now it shows up as empty (since /var/www/html is empty too), could also post a message there or whatever.
I'm on CentOS btw, so the config might differ.
It's basically exactly what the previously linked Apache documentation talked about.
In short you've got ports and addresses configured incorrectly in your Apache configuration--Virtualmin doesn't touch the NameVirtualHost directives (though you can set them in Webmin's Apache module), and so if you've configured it incorrectly all of your virtual hosts will be broken.
And to answer the earlier suggestion that Webmin or Virtualmin may not know about Debian-based distros locations, it definitely does. Debian and Ubuntu are both well-supported (and Jamie and I use Debian on some of our own systems).