A domain has been on a Plesk 7.5.4 server for some time. It was previously sharing the main server IP with a few dozen other domains. More recently the domain owner needed to have it moved to its own dedicated IP number so that they could activate some e-commerce and install their own SSL cert. No problem right? Plesk allows you to do that right in the control panel.
The problems...
First there were problems with getting a reverse pointer set up for the new IP number. EV1's system said it thought the domain was still on the main IP number instead of the new one, even though the server runs it's own DNS (doesn't got through EV1's nameservers) and even though I could nslookup or dig from several locations and everything seemed to trace back to the correct IP number. An EV1 tech "fixed" this by editing resolv.conf to input EV1 nameserver IP numbers instead of the ones on the server. So it was fixed. Though the resolv.conf was changed back to be correct.
Now a new problem raises it's ugly head. The domain has Custom Error Documents set up and checked in the Setup area. Always has had them in fact. If you use the standard Apache/Plesk error docs the message that now shows up is
QUOTE
Not Found
The requested URL /nopage.html 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 requested URL /nopage.html was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
(emphasis mine)
If you try to use a truly custom error document and set up an .htaccess call to it, you get nothing at all. The server just times out before delivering anything at all.
Something in changing the domain to having its own domain appears to have seriously messed up a path somewhere or something and it's causing Apache to freak out a bit. I've scanned over the httpd.include file for the domain and the vhost.conf and vhost_ssl.conf and they're all in good order. Nothing at all out of the ordinary. Which makes me think there may be something in the Plesk database that was supposed to be altered during the change but wasn't.
Anybody seen anything like this before when changing from shared to dedicated IP? Any ideas on where to start looking? Does it sound like a PSA database error to you too?