Custom Error Pages
Get familiar with website error pages. Find out when they show up and why you need to set up your individual custom error pages.
Whenever a page on your site doesn't load, an error message will be shown to the site visitor. Since there are different errors, there are different pages that will show up, but what is typical for all of them is that they're generic and probably shall have nothing in common with the design of your Internet site, which may be aggravating for any visitor. That is the reason why website hosting providers have introduced a feature known as Custom Error Pages. For a number of different errors, site visitors will see your customized content, which can be informative or humorous, in accordance with your choice, and which shall match the design of your site, so the pages will not seem like they aren't part of your website at all. You can use this option for numerous errors - 400 (Bad request), 401 (Unauthorized), 403 (Forbidden) and 404 (File not Found).
Custom Error Pages in Cloud Website Hosting
When you buy a cloud website hosting plan
from our company, you'll be able to set custom error pages for your Internet sites fast and easy, as this function is part of all our packages. As soon as you have created the files and uploaded them to your web hosting account, you should check out the Hosted Domains section of your Hepsia Control Panel and click on the Edit button for the specific domain or subdomain. In the pop-up that will be displayed, you'll see drop-down options menus for all four types of errors and for each of them you may select an Apache default page, a generic page from our system or a tailor-made page. If you select the third option, you should simply type the URL to the file which you have uploaded then save the change. Another way to set customized error pages is to set up an .htaccess file inside the domain or subdomain folder and to include a few lines of program code in it. If you do not have previous experience or if you're just unsure how to do this, you could just copy and paste the code from our Knowledge Base article on that matter.