Custom Error Pages in Cloud Website Hosting
The customized error pages function is offered with every cloud website hosting package we offer and you will be able to swap all generic pages with your own with no more than just a few clicks in your Hepsia hosting Control Panel. You'll have to develop the actual files and to upload them to your account, then to set them for a given domain or subdomain via the Hosted Domains section of the Hepsia Control Panel. You may do this for every web site hosted in the account separately, so that every set of custom pages will have the very same layout as the Internet site it's part of. If required, you may always revert back to a default page from our system or to a default Apache server page. Another way to set custom error pages is to create an .htaccess file in the domain/subdomain root folder and to add a few lines in it. If you never done this before, you could simply copy the required code from our Help article about the subject.
Custom Error Pages in Semi-dedicated Hosting
Including your pages for each of the four error types to any site hosted in a semi-dedicated server account with us will be really easy and won't take more than several mouse clicks. Once you upload the files in your account, you could go to the Hosted Domains section of your Hepsia Control Panel and edit each of the domains and subdomains listed there through an intuitive interface with drop-down menus. You may pick what page should display for each and every error type. Your choices are a standard Apache server page or a page from our system, and personalized pages. If you pick the aforementioned option, you have to type in the link to every page inside your account, then save the change. The link or the kind of page that will appear when a user encounters an error can be changed at any time. If you're more experienced, you can use an .htaccess file to be able to set tailor-made error pages too, as an alternative to using our integrated generator software instrument, and should you choose this option, the file must be positioned in the root directory of a specific domain or subdomain.