Apache is functioning normally

Hi guys,

I've added new users to my server which has been working perfectly for many years.

Howerver new users can't access there domains. www.NewDomain.com simply points to the "Apache is functioning normally" page.
However serverip/~newusername works perfectly.

I've searched on here and found people talking bout restarting named and httpd to fix the issues. I've tried both of those to no avail.

I've also found a thread that talks about PIM details in the httpd conf files and they all seem to be present. (http://www.directadmin.com/forum/showthread.php?t=22882&highlight=Apache+functioning)

Anyone got any ideas, I'm really at the end of my tether on this one.

Cheers.

Are you sure their domain points to the right ip address it is setup with on apache?

Yes I forgot to mention that DNS resolves to my server correctly as it should.

Well thats usually whats wrong is the dns is not the same as the virtualhost ip address. You might have to look in the configs for apache to make sure that its setup for the right ip as the dns.

If I look in /usr/local/directadmin/data/users/username/httpd.conf for the virtual host information it points at the same IP that DNS points to.

I've also tried moving the users to new IP addresses and creating an entry in my local hosts file to reflect the changes and it just re-writes the url to the primary ip of the server and gives me the "Apache is functioning normally" message.

Resolved the issue.

It was due to wordpress having been setup and configured using the 1p address rather than a domain name pending DNS changes taking place.

Nightmareish problem and such a stupid little detail

ohhh well hope somebody else can benifit from this rather than spending hours searching through apache configs for something that isn't even an apache problem.

agentoffortune said:

Resolved the issue.

It was due to wordpress having been setup and configured using the 1p address rather than a domain name pending DNS changes taking place.

Nightmareish problem and such a stupid little detail

ohhh well hope somebody else can benifit from this rather than spending hours searching through apache configs for something that isn't even an apache problem.

Click to expand...

Your a gem mate, I had been scratching my head with this problem all night

Thanks for posting the solution.

David