To inform Internet users of web server errors and help figure out what caused the problem, web servers generate and display standard HTML pages. Following is a list of error documents with descriptions.
400 Bad File Request | Usually means the syntax used in the URL is incorrect (e.g., uppercase letter should be lowercase letter; wrong punctuation marks). |
401 Unauthorized | Server is looking for some encryption key from the client and is not getting it. Also, wrong password may have been entered. |
403 Forbidden/Access Denied | Similar to 401; special permission needed to access the site - a password and/or username if it is a registration issue. |
404 File Not Found | Server cannot find the requested file. File has either been moved or deleted, or the wrong URL or document name was entered. |
408 Request Timeout | Client stopped the request before the server finished retrieving it. Usually occurs when servers are slow or file sizes are large. |
500 Internal Error | Could not retrieve the HTML document because of server-configuration problems. |
501 Not Implemented | Web server does not support a requested feature. |
502 Service Temporarily Overloaded | Server congestion; too many connections; high traffic. |
503 Service Unavailable | Server busy, site may have moved, or Internet connection was lost. |
Connection Refused by Host | User either does not have permission to access the site or password is incorrect. |
File Contains No Data | Page is there but is not showing anything. Error occurs in the document. Attributed to bad table formatting, or stripped header information. |
Bad File Request | Browser may not support the form or other coding the user is trying to access. |
Failed DNS Lookup | The Domain Name Server cannot translate domain request into a valid Internet address. Server may be busy or down, or incorrect URL was entered. |
Host Unavailable | Host server down. |
Unable to Locate Host | Host server is down, Internet connection is lost, or URL typed incorrectly. |
Network Connection Refused by the Server | The Web server is busy. |
With Plesk 7.5 you can customize only the following error messages:
If you would like Plesk web server to show your custom error pages instead of standard ones, follow these steps:
Switch on support for custom error documents through Plesk interface. Go to a specific domain’s administration page, click Setup, and select the Custom Error Documents checkbox.
If you access Plesk remotely, connect to your FTP account on the Plesk server, and go to the error_docs directory. If you access Plesk locally, go to the directory /vhosts/domain_name.tld/error_docs/
Edit or replace the respective files. Be sure to preserve the correct file names:
Once done editing, restart the web server manually, or wait till it is restarted. After that, the web server will start using your error documents.