Custom Error Pages
Understand what a Custom Error Page is, what role does it have and ways to set up one.
Whenever a page on your website does not load, an error message shall be displayed to the site visitor. Since there are different errors, there are different pages which will appear, but what is standard for all of them is that they're generic and in all probability shall have absolutely nothing in common with the layout of your site, which may be frustrating for any website visitor. This is the main reason why website hosting companies have introduced a feature referred to as Custom Error Pages. For a number of different errors, website visitors will see your custom made content, which could be informative or amusing, in accordance with your personal preference, and that will match the design and style of your Internet site, so the pages will not look like they aren't part of your site at all. You can use this option for many errors - 400 (Bad request), 401 (Unauthorized), 403 (Forbidden) and 404 (File not Found).
-
Custom Error Pages in Shared Hosting
When you obtain a
Linux shared hosting package from us, you will be able to set customized error pages for your websites quickly and easily, since this function is a part of all of our solutions. The moment you've created the files and uploaded them to your web hosting account, you should check out the Hosted Domains section of your Hepsia CP and click on the Edit button for the selected domain or subdomain. Inside the pop-up which will be displayed, you'll see drop-down options menus for all 4 types of errors and for each one of them you could choose an Apache default page, a generic page from our system or a customized page. Should you choose the third option, you should only input the URL to the file that 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 several lines of code in it. In case you don't have prior experience or if you are simply unsure how to do this, you can simply copy/paste the code from our Knowledge Base article on that topic.