Custom Error Pages
Take a plunge into website error pages. Discover when they show up and why you should set up your own custom error pages.
If you have looked at lots of Internet sites, you have probably stumbled upon some error message once in a while. An error may take place in case the hosting server cannot process a request (Error 400), if you must log in to see some content and you have not done so (Error 401), if you are not permitted to access some page (Error 403) or if a link leads to a file that isn't on the server (Error 404). Getting this sort of messages may often be annoying because the pages have absolutely nothing in common with the actual site. That’s why some hosting providers permit you to apply your own error pages which will match the style of your own website and which could have any content that you want - info why the error has occurred, a suggestion how to handle it or even some amusing remark. Such a function will help you keep the visitor on the website whatever the error or the reason for it.
Custom Error Pages in Website Hosting
When you buy a Linux website hosting
from our company, you'll be able to set custom made error pages for your sites fast and easy, since this feature is a part of all of our packages. The moment you've created the files and uploaded them to your web 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 that will show up, you shall see drop-down options menus for all four sorts of errors and for each one of them you can pick an Apache default page, a generic page from our system or a custom made page. Should you pick the third option, you should just enter the URL to the file you have uploaded then save the change. A different way to set custom made error pages is to set up an .htaccess file in the domain or subdomain folder and to include several lines of code in it. In case you don't have preceding experience or if you're simply unsure how to do this, you could just copy/paste the code from our Knowledge Base article on that subject.