Custom Error Pages
Find out about website error pages, exactly when they appear and why you ought to make use of customized error pages.
If you have checked out a lot of sites, you have probably stumbled upon some error message now and again. An error can occur if the web server cannot process a request (Error 400), if you have to log in to see some content and you have not done so (Error 401), if you are not allowed to access a webpage (Error 403) or when a link leads to a file that is not on the server (Error 404). Receiving this kind of messages can sometimes be irritating because the pages have absolutely nothing in common with the actual site. That’s why some web hosting companies permit you to use your own error pages that will match the design of your own site and that could have any content that you want - information why the error has appeared, a suggestion how to handle it or even some funny comment. This type of function shall help you keep the visitor on the site no matter the error or the reason for it.
Custom Error Pages in Shared Website Hosting
When you get a Linux shared website hosting package
from our company, you'll be able to set custom made error pages for your sites fast and easy, because this function is part of all our plans. The moment you've created the files and uploaded them to your web 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. Inside the pop-up that will appear, you'll see drop-down options menus for all four kinds of errors and for each of them you could choose an Apache default page, a generic page from our system or a tailor-made page. If you pick the third option, you should only input the URL to the file which you have uploaded and save the change. Another way to set personalized error pages is to set up an .htaccess file inside the domain or subdomain folder and to include several lines of code in it. If you don't have preceding experience or if you are simply not sure how to do this, you could simply copy/paste the code from our Knowledge Base article on that matter.