If a particular page on a website doesn't load for some reason or if a link is broken, the visitor will see an error page with some generic message. The page will have nothing in common with the rest of the website, which could make the visitor leave your website. A likely solution in such a case is a function offered by some hosting service providers - the option to set your own customized error pages which shall have the exact same layout as your site and which could contain any text or images you want depending on the specific error. There are 4 standard errors which can occur and they involve these particular so-called HTTP status codes - 400, when your world-wide web browser sends a bad request to the hosting server and it cannot be processed; 401, in case you are supposed to log in to see some page, but you haven't done so yet; 403, if you don't have a permission to view a certain page; and 404, if a link which you have clicked leads to a file that does not exist. In all of these situations, site visitors shall be able to see your customized content instead of a generic error page.
Custom Error Pages in Cloud Hosting
The customized error pages feature is provided with every cloud hosting package deal that we offer and you shall be able to swap all generic pages with your own with no more than several clicks in your Hepsia hosting CP. You shall have to develop the actual files and to upload them to your account, and then to set them for a particular domain or subdomain through the Hosted Domains section of the Hepsia Control Panel. You can do this for every single web site hosted in the account separately, so that every set of personalized pages will have the very same style and design as the site it is part of. If necessary, you may always go back to a default page from our system or to the default Apache server page. Another way to set custom error pages is to create an .htaccess file in the domain/subdomain root folder and to add a few lines in it. If you never done this before, you could simply copy the needed program code from our Help article about this.