HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=27)
-   -   Ispconfig 3 Vhost issues. (http://www.howtoforge.com/forums/showthread.php?t=31803)

DestRoYeD 25th February 2009 22:56

Ispconfig 3 Vhost issues.
 
I Have Ispconfig 3 installed, One of my Coworkers was setting up awstats and made a mess of the Vhost files, I Have managed to fix this problem, But now many of my sites including the ispconfig 3 Admin, No longer work they just Redirect to the Default page.

Nothing in the apache error.log or the error log for that particular vhost.

I Have check the vhost files of the sites that don't work and they look fine.

This is the error i get when i restart apache2

Quote:

XXXXXX@XXXX:/etc/apache2/sites-available$ sudo /etc/init.d/apache2 start
* Starting web server apache2

[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost _default_:8080 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Thu Feb 26 10:45:50 2009] [warn] NameVirtualHost *:8080 has no VirtualHosts

Quote:

[Thu Feb 26 10:45:50 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
I have heard that this is a common problem with Ubuntu/Debian and has to do with the default file.


Any Ideas?

Brett

till 25th February 2009 23:41

Yes, thats a issie with the default file. Open the apache default host file and replace * with *:80 in thevhost and the namevirtualhost directive and then restart apache.

DestRoYeD 26th February 2009 00:55

Cheers till,

I tried this and it just made all sites go to the default

Quote:

* Stopping web server apache2
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Feb 26 12:51:22 2009] [warn] NameVirtualHost *:8080 has no VirtualHosts
My main problem is not being able to access the ispconfig administration. It just goes to the Default page e.t.c /var/www/index.php

till 26th February 2009 09:13

Looks as if you specified more then one default host manually in your installation. You will have to remove them.

DestRoYeD 26th February 2009 21:08

Thanks
 
Thanks Till, That was it still getting the same messages when i restart apache, But everything seems to be working now :)

Cheers

vk1003 25th November 2010 11:29

small issue
 
hi there,

not sure if i have to post this here or as a new topic.. we have installed the centos 5.5 and installed ispconfig3 as well, mails are working perfectly for the domain we create via the ispconfig control panel and ftp is working absolutely fine showing all folders inside and uploading is smooth as well.

but the website alone is not showing up.. for what ever domain account we create it shows the apache test page only and not that of the one we uploaded on ftp..

We installed apache and everything via the ispconfig3 and nothign was manually edited.. can some one help us where the mistake is hapening to sort the same.

regards
venkat v

till 25th November 2010 11:35

Add the ip address of the servcr under system > server ip and then select the ip in the website settings.

vk1003 25th November 2010 11:42

that was done
 
hi till,

thanks for the immediate reply, we had the public ip added and were actually choosing it.. and it still wasnt loading.. i will ask my system engineer to the log error shortly on here as i think it should give some idea..


One small piece of information, i am registering domains else where and holding the dns with the domain and pointing mx, a and cname entries to this server.

regards
venkat

till 25th November 2010 11:44

If you are in a NAT enviroment, then you have to use the private and not public IP. Public IP's are only used in dns but not in website settings.

vk1003 25th November 2010 11:46

Nat ! ?
 
Yes my AIRTEL Router has NAT settings and i use that to forward the ports to my local machine which contains the linux installed..

you said we should add only the local ip .. does that mean that i should add the 192.168.1.2 ip in the ispconfig if i am on nat !! am i right


All times are GMT +2. The time now is 11:20.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.