Hello,

I have an account on a cPanel machine that is returning the following:

Not Found

The requested URL http://www.domain.com was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

The domain is using a dedicated IP which returns the same thing. If I change the IP to to use the shared one, I get the Apache page. Any ideas???

Thanks for your time!

Anybody? Just a hint, maybe...

It could be several things....

The hint would be....

1. verify that you are making the request to the IP address you think you are (or should be)
2. verify that the server is properly configured to handle that request on that interface with the specified hostname
...or....
figure out where the server thinks it should serve the request from, which will (at least it should) tell you where your configuration is messed up at.

It would probably take less than 5 minutes to diagnose with root access.... and several hours (or days) to diagnose through a forum, and several years to diagnose with the amount of information you have provided so far. :)

NoNot Found

The requested URL http://www.domain.com was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

The domain is using a dedicated IP which returns the same thing. If I change the IP to to use the shared one, I get the Apache page. Any ideas???

Thanks for your time!

I am wondering, if you have shell access, ssh in and do this

check the /etc/httpd/conf/httpd.conf. There should be a "VirtualHost tag" for this domain. If not, add it. If it is there, try restarting apache.

Hope this helps :)

Andres

Okay....

I checked the http.config and it looked normal. I checked the named config and it looked normal. I had already restarted Apache and the Server. I checked the zone file and it looked normal. It should be working!

I don't know what other information to give you.

Thank for your time!

From a windows machine, do a ping or tracert to your domain name (the one that doesn't work) to verify the ip address you are connecting to is the one you think you are. ex. tracert yourdomain.com

On the server, from a shell prompt, do ...
/usr/sbin/httpd -S
to see the ip address that apache thinks the domain should be serverd from.

verify the document root setting for the domain in httpd.conf, and verify that the directory exists, and is readable by the user the apache server runs as.

If you are not specifying a particular file in the request, try it that way (http://yourdomain.com/index.html instead of http://yourdomain.com ) If it works that way and not the other way, verify your directoryindex settings for the domain in httpd.conf and in any applicable .htaccess files

If all of the above look OK, you can tail log files while making the request and see if you can determine which virtualhost container is handling the request (if any)

login and run apachectl configtest then httpd -S then httpd -t
One of the doc roots or vhosts is wrong.
But I'm more inclined to agree with elsemore1.

So far everything checks out. Using the file name in the URL does not help either. Ping is correct, http is correct...

What files should I tail? I tailed "/usr/local/apache/logs/access_log" and got nothing.

Thanks again!

If you want to PM me, we can pursue this further off list, but you should tail at least the default "access_log" (may be called transfer_log) files for the server, and possibly any other log files specified in one or more of the virtualhost containers (if any). If your request doesn't show up in any of them, it would be an indication that the request isn't even getting to the server you think it is. :)

It's getting to the server because if I call the IP, the Not Found page still says that the domain was not found on this server.

That means it is getting to "a" server. Does the 404 page specify which server is generating that message?

If you can verify that it is getting to the correct server, (which it probably is) and the webserver software (Apache?) is handling the request, then it is just a matter of finding out why apache doesn't believe it should serve up the page for that domain under that IP address. Re-directs, re-writes, mis-types, etc... are all possibilities, but apache will have a record of it somewhere, unless you have disabled logging for the request type in question, in which case, that can be re-enabled and the problem properly diagnosed.

[added] you said when you "call the IP the Not Found page still says that the domain"...
That is a confusing statement... are you saying that you try to request http://nn.nn.nn.nn/ (where nn.nn.nn.nn is the IP address) and it tells you that "yourdomain.com" is not on the server? I

This is a bit of wild guess, but... Go into the document root (where the files for your site are kept). Are there any files at all? If not, try running "touch index.html" and then try again. (You should get a blank page.)

Arrgg!!

Turns out that the Not Found page was the index page. :rolleyes:

Where the heck did it come from? And what could have put it there? I nor the client did not do it.

Very sorry for waisting everyones time! Duh! :eek:

Originally posted by v-rod
Arrgg!!

Turns out that the Not Found page was the index page. :rolleyes:

Where the heck did it come from? And what could have put it there? I nor the client did not do it.

Very sorry for waisting everyones time! Duh! :eek:
LOL. But the Not Found page was not the index page, your server returned 404 Not Found error because it can't find your index file in your home dir.

Yes, the index.htm file WAS the Not Found page. THAT is what started this whole thing.... :eek3: