Custom Error Pages in Cloud Web Hosting
The personalized error pages function is provided with every single cloud web hosting package deal which we offer and you'll be able to substitute all the generic pages with your own with no more than just a few clicks inside your Hepsia hosting Control Panel. You will need to create the actual files and to upload them to your account, then to set them for a specific domain or subdomain using the Hosted Domains section of the Hepsia Control Panel. You may do this for each site hosted inside the account separately, so that every group of custom made pages will have the exact same design as the site it is part of. If needed, you could always go back to a default page from our system or to the default Apache server page. An alternate way to set custom made error pages is to create an .htaccess file inside the domain/subdomain root folder and to include a few lines in it. If you have never done this before, you may simply copy the required program code from our Help article on this subject.
Custom Error Pages in Semi-dedicated Servers
Adding your own pages for each of the four error types to any site hosted in a semi-dedicated server account with us shall be very basic and will not take more than a few clicks. As soon as you upload the files to your account, you could check out the Hosted Domains section of your Hepsia Control Panel and edit each of the domains and subdomains listed there using an intuitive interface with drop-down navigation. You can choose what page should display for every single error type. The options are a default Apache server page or a page from our system, and custom pages. If you choose the abovementioned option, you need to input the link to each and every page in your account, then save the change. The link or the kind of page that will be shown when a user encounters an error can be modified at any time. If you are more experienced, you can use an .htaccess file so as to set in-house developed error pages as well, rather than using our integrated generator instrument, and should you select this option, the file needs to be located inside the root directory of a particular domain or subdomain.