Creating Error Pages

It's easy to add error pages to your web site. Simply login to cPanel and scroll down to Advanced and click on Error Pages. Choose the domain or subdomain you want and click the page you want to edit and insert your own custom page code.

Alternatively, you can write your own web pages and save them in .shtml format and upload them to your public_html directory.

Although this is not an exhaustive list, these are some of the more common error pages.

400.shtml  -  400 Bad Request The request cannot be fulfilled due to bad syntax.

401.shtml  -  401 Unauthorized The request was a legal request, but the server is refusing to respond to it.
                        For use when authentication is possible but has failed or not yet been provided.

403.shtml  -  403 Forbidden The request was a legal request, but the server is refusing to respond to it.
404.shtml  -  404 Not Found The requested page could not be found but may be available again in the future.
405.shtml  -  405 Method Not Allowed A request was made of a page using a request method not supported by that page.
406.shtml  -  406 Not Acceptable The server can only generate a response that is not accepted by the client.
407.shtml  -  407 Proxy Authentication Required The client must first authenticate itself with the proxy.
412.shtml  -  412 Precondition Failed The precondition given in the request evaluated to false by the server.
414.shtml  -  414 Request-URI Too Long The server will not accept the request, because the URL is too long. Occurs when you
                        convert a POST request to a GET request with a long query information

415.shtml  -  415 Unsupported Media Type The server will not accept the request, because the media type is not supported.
500.shtml  -  500 Internal Server Error A generic error message, given when no more specific message is suitable.
501.shtml  -  501 Not Implemented The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502.shtml  -  502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response from the upstream server.

  • Email, SSL
  • 0 Users Found This Useful
Was this answer helpful?