
25th February 2009, 22:56
|
|
Junior Member
|
|
Join Date: Feb 2009
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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
Last edited by DestRoYeD; 25th February 2009 at 23:04.
Reason: Addition for Clarity
|

25th February 2009, 23:41
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 32,068
Thanks: 697
Thanked 4,248 Times in 3,260 Posts
|
|
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.
|

26th February 2009, 00:55
|
|
Junior Member
|
|
Join Date: Feb 2009
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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
|

26th February 2009, 09:13
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 32,068
Thanks: 697
Thanked 4,248 Times in 3,260 Posts
|
|
Looks as if you specified more then one default host manually in your installation. You will have to remove them.
|

26th February 2009, 21:08
|
|
Junior Member
|
|
Join Date: Feb 2009
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Thanks
Thanks Till, That was it still getting the same messages when i restart apache, But everything seems to be working now
Cheers
|

25th November 2010, 11:29
|
|
Junior Member
|
|
Join Date: Nov 2010
Posts: 12
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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
|

25th November 2010, 11:35
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 32,068
Thanks: 697
Thanked 4,248 Times in 3,260 Posts
|
|
Add the ip address of the servcr under system > server ip and then select the ip in the website settings.
|

25th November 2010, 11:42
|
|
Junior Member
|
|
Join Date: Nov 2010
Posts: 12
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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
|

25th November 2010, 11:44
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 32,068
Thanks: 697
Thanked 4,248 Times in 3,260 Posts
|
|
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.
|

25th November 2010, 11:46
|
|
Junior Member
|
|
Join Date: Nov 2010
Posts: 12
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
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
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT +2. The time now is 10:56.
|
Recent comments
1 day 12 hours ago
1 day 15 hours ago
2 days 3 hours ago
2 days 5 hours ago
2 days 10 hours ago
2 days 16 hours ago
3 days 1 hour ago
3 days 3 hours ago
3 days 11 hours ago
3 days 13 hours ago