If a particular page on a website doesn't load for some reason or if a link is broken, the visitor shall see an error page with a generic message. The page will have nothing in common with the rest of the site, which can make the visitor leave your Internet site. A possible solution in such a case is a feature made available from some hosting service providers - the option to set your own personalized error pages that shall have the same design as your site and which can contain any text or images that you'd like depending on the specific error. There are four common errors that may take place and they involve these particular so-called HTTP status codes - 400, when your browser sends a bad request to the server and it can't be processed; 401, in case you are supposed to log in to see some page, but you have not done so yet; 403, if you don't have a permission to view a particular page; and 404, in case a link which you've clicked leads to a file that does not exist. In any of these cases, website visitors shall be able to see your personalized content rather than a generic error page.

Custom Error Pages in Cloud Hosting

If you get a Linux cloud hosting package from us, you'll be able to set custom made error pages for your sites quickly and easily, as this function is part of all our packages. After you've created the files and uploaded them to your web hosting account, you can go to the Hosted Domains section of your Hepsia Control Panel and click on the Edit button for the specific domain or subdomain. Inside the pop-up which will appear, you'll see drop-down menus for all 4 kinds of errors and for each of them you could pick an Apache default page, a generic page from our system or a custom page. Should you pick the third option, you should simply enter the URL to the file which you have uploaded and save the change. A different way to set custom made error pages is to set up an .htaccess file inside the domain or subdomain folder and to add a couple of lines of code in it. In case you don't have preceding experience or if you are simply uncertain how to do that, you can just copy/paste the code from our Knowledge Base article on that subject.