Custom error pages on Loopia hosting let you replace the web server’s default error messages (such as the familiar 404 page) with your own pages. This article explains how to configure custom error pages in the Loopia Customer Zone, which file types are supported (ASP.NET, ASP, HTML and PHP), and what each of the configurable HTTP error codes means.
What are custom error pages?
When a web server cannot deliver a particular page, it generates an error message. This may be because the page does not exist (the familiar 404 error), because a programming error occurred, or for a similar reason. With the custom error pages feature in the Loopia Customer Zone, you can replace the web server’s default error pages with your own.
An example is available here. This is our own custom-made error page for the 404 error (page not found).
How to configure custom error pages
To set a custom error page, you need a hosting account with at least one (1) domain. The error pages you can change are listed further down (along with what they mean).
To set a custom error page, log in to the Loopia Customer Zone and look for the section titled “Domain names”. Select the domain you want to configure custom error pages for.
Choose “Error pages”, enter the path to the file and then save.
We support the following file types for custom error pages: ASP.NET, ASP, HTML and PHP.
Explanation of error codes
Below you will find an explanation of the HTTP error codes for which we offer custom error pages.
400 Bad Request
The client sent a bad request. Not normally used; indicates a communication problem between the browser and the web server.
401 Unauthorized
Can be useful if you are using password-protected files and folders.
403 Forbidden
Usually indicates an incorrect setting on the FTP site.
404 Not Found
The requested file or folder could not be found. Usually caused by an incorrect file name or link.
500 Internal Server Error
Usually generated by script errors. You should ask the visitor to try again later.
501 Not Implemented
The client sent a request the server does not support. Not normally used; indicates a communication problem between the browser and the web server.
502 Bad Gateway
Something is wrong with the program on the server. You should ask the visitor to try again later.