Custom Error Pages
Take a plunge into website error pages. Discover when they appear and why you should configure your individual custom error pages.
If you have browsed loads of sites, you have probably come across some error message once in a while. An error can occur in case the website hosting server cannot process a request (Error 400), if you must log in to see some content and you haven't 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 web server (Error 404). Getting this sort of messages could often be aggravating as the pages have absolutely nothing in common with the actual website. That’s why some website hosting providers permit you to use your own error pages which will match the layout of your own website and that could have any content which you want - details why the error has occurred, a suggestion how to proceed or even some humorous remark. This kind of feature will help you keep the visitor on the website whatever the error or the reason for it.
Custom Error Pages in Cloud Hosting
If you acquire a Linux cloud hosting
from us, you'll be able to set personalized error pages for your Internet sites easily and quickly, as this function is part of all our solutions. The moment you have created the files and uploaded them to your web hosting account, you can check out the Hosted Domains section of your Hepsia CP and click on the Edit button for the specific domain or subdomain. In the pop-up which will be displayed, you'll see drop-down options menus for all four sorts of errors and for each of them you could choose an Apache default page, a generic page from our system or a custom page. In case you select the third option, you should simply type the URL to the file that you've uploaded then save the change. A different way to set customized error pages is to set up an .htaccess file inside the domain or subdomain folder and to include a couple of lines of program code in it. If you do not have preceding experience or if you are just unsure how to do this, you may simply copy and paste the code from our Knowledge Base article on that topic.