Custom Error Pages
Get familiar with website error pages. Learn when they show up and why you should configure your own custom error pages.
When a page on your Internet site doesn't load, an error message will be displayed to the site visitor. Because there are different errors, there are different pages that will display, but what's typical for all of them is that they are generic and in all probability will have practically nothing in common with the design of your website, which could be annoying for any visitor. This is the main reason why web hosting companies have introduced a function called Custom Error Pages. For a range of different errors, website visitors will see your custom made content, which can be informative or amusing, depending on your personal preference, and which will match the overall layout of your website, so the pages will not seem like they are not part of your site at all. You could use this option for a number of errors - 400 (Bad request), 401 (Unauthorized), 403 (Forbidden) and 404 (File not Found).
Custom Error Pages in Cloud Hosting
If you get a cloud hosting from us, you shall be able to set personalized error pages for your Internet sites easily, since this feature is a part of all of our plans. As soon as you've created the files and uploaded them to your hosting account, you can go to the Hosted Domains section of your Hepsia CP and click on the Edit button for the selected domain or subdomain. In the pop-up which will appear, you'll see drop-down menus for all 4 types of errors and for each of them you can choose an Apache default page, a generic page from our system or a custom page. In case you pick the 3rd option, you should simply input the URL to the file you have uploaded and save the change. Another way to set customized error pages is to create an .htaccess file in the domain or subdomain folder and to include a couple of lines of code in it. In case you don't have preceding experience or if you're simply uncertain how to do this, you can just copy/paste the code from our Knowledge Base article on that topic.