Custom Error Pages
Discover more about web site error pages, when they display and why you ought to make use of customized error pages.
If you have looked at many sites, you have probably come across some error message every now and then. An error could take place when the web server cannot process a request (Error 400), if you need to log in to see some content and you haven't done so (Error 401), if you are not able to access some page (Error 403) or when a link leads to a file that isn't on the server (Error 404). Receiving this kind of messages could often be aggravating because the pages have absolutely nothing in common with the actual website. That’s why some hosting providers allow you to use your own error pages that'll match the style of your own site and which can have any content which you'd like - details why the error has appeared, a suggestion how to proceed or even some humorous remark. This type of feature can help you keep the visitor on the website whatever the error and the reason for it.
Custom Error Pages in Shared Website Hosting
If you buy a Linux shared website hosting
from us, you'll be able to set customized error pages for your Internet sites easily, since this function is a part of all of our solutions. After you have created the files and uploaded them to your hosting account, you can go to the Hosted Domains section of your Hepsia Control Panel and click on the Edit button for the particular domain or subdomain. In the pop-up which will appear, you shall see drop-down menus for all four sorts of errors and for each one of them you may select an Apache default page, a generic page from our system or a tailor-made page. If you select the 3rd option, you should simply type the URL to the file you have uploaded then save the change. Another way to set personalized error pages is to set up an .htaccess file in the domain or subdomain folder and to add a few lines of code in it. If you do not have preceding experience or if you are just unsure how to do that, you could simply copy/paste the code from our Knowledge Base article on that subject.