Custom Error Pages
Learn more about web site error pages, when they show up and why you should utilize customized error pages.
If you have looked at many sites, you've probably stumbled upon some error message from time to time. An error may take place in case the website hosting server can't process a request (Error 400), if you must log in in order to see some content and you have not done so (Error 401), if you are not able to access some webpage (Error 403) or when a link leads to a file which isn't on the website hosting server (Error 404). Receiving this kind of messages could sometimes be annoying since the pages don't have anything in common with the actual site. That’s why some web hosting providers allow you to set your own error pages that'll match the style of your own website and which can have any content which you would like - details why the error has occurred, a suggestion how to handle it or even some amusing remark. This sort of feature shall help you keep the visitor on the website no matter the error or the reason for it.
-
Custom Error Pages in Shared Hosting
If you buy a
Linux shared hosting package from our company, you shall be able to set customized error pages for your sites easily and quickly, since this feature is part of all of our packages. The moment you have created the files and uploaded them to your website hosting account, you can check out the Hosted Domains section of your Hepsia Control Panel and click on the Edit button for the particular domain or subdomain. Inside the pop-up which will be displayed, you'll see drop-down menus for all four types of errors and for each of them you may pick an Apache default page, a generic page from our system or a custom page. In case you choose the third option, you should just type the URL to the file that you have uploaded and save the change. One other way to set personalized error pages is to create an .htaccess file inside 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 unsure how to do that, you may simply copy/paste the code from our Knowledge Base article on that subject.