Posts: 31,888
Thanks: 693
Thanked 4,188 Times in 3,205 Posts
It uses ubuntus default vhost, but as I explained in one of my first posts, apache priorizes IP addresses in favor of wildcards, so it can be that a vhost which uses a IP address is shown befaore the default vhost. The solutions are:
a) Use * for all sites instaed of IP addresses.
b) Create a additional default vhost for each IP address.
There is only one vhost, and it is allready * marked
There is only one ip address. So there is no need to make an extra vhost.
I tried yesterday to point the DNS at this server again, with the right domain, but still there was the forbidden message this morning (after the DNS has probagated through all the DNS servers in the chain). So since it's a production site, I have switched the DNS back to point at another server.
The Following User Says Thank You to neumann For This Useful Post:
Changing the hosts file on your workstation affects only the applications that you run on your workstation, so you can test out the settings for a production side withou affecting any customers. Another psotive side affect is that you can do the test in realtime without having to with for the dns caches to change.
Posts: 31,888
Thanks: 693
Thanked 4,188 Times in 3,205 Posts
Just to close the issue, the server is behind a nat router and the vhost was configured to use the external ip address instead of the internal ip so apache could not find a matching vhost for the domain / ip combination.
General note for servers behind a router:
In websites (vhosts) use the internal ip address
For dns records (bind) use the external ip
Recent comments
18 hours 9 sec ago
22 hours 58 min ago
1 day 25 min ago
1 day 1 hour ago
1 day 3 hours ago
1 day 7 hours ago
1 day 8 hours ago
1 day 10 hours ago
1 day 23 hours ago
2 days 1 hour ago