Plesk Custom 404 Error
Contents |
Guide cPanel WebHost Manager (WHM) Plesk SSL Certificates Specialized Help Offers & Bonuses Website Design Affiliates Helpful Resources Account Addons Billing System HostGator Blog HostGator Forums Video Tutorials Contact plesk 12 custom error documents Us Interact and Engage Put two or more words in quotes to
Custom Error Documents Plesk
search for a phrase: "name servers" Prepend a plus sign to a word or phrase to require its presence in an article: +cpanel Prepend a minus sign to a word or phrase to require its absence in an article: -windows Words of less than three characters are ignored. All searches are case-insensitive. Search [?] Support Portal Home » Plesk » Plesk 10 » Plesk 10 Client Side » Setting Up Custom Error Documents on Plesk 10 Linux VPS Setting Up Custom Error Documents on Plesk 10 Linux VPS Overview cPanel Plesk on Windows Plesk 10 VPS Please add this code to your .htaccess file in the httpdocs directory. ErrorDocument 403 /403.shtml
ErrorDocument 404 /404.shtml
ErrorDocument 500 /500.shtml
Next create a file named 403.shtml in your httpdocs folder. Now the 403 errors will yield the 403.shtml page. Repeat for 404.shtml and 500.shtml. You can even use existing pages as the resulting page. Say you don't want any visitors seeing 404 errors on your site. You can make your home page the result, like so: ErrorDocument 404 /index.html
If Internet Explorer is not displaying the custom error page, it is likely because the error page must be larger than 1 kilobyte. There are many error pages which may be defined. Client Request Errors 400 - Bad Request 401 - Authorization Required 403 - Forbidden 404 - Not Found 405 - Method Not Allowed 406 - Not Acceptable (encoding) 407 - Proxy Authentication Required 408 - Request Timed Out 409 - Conflicting Request 410 - Gone 411 - Content Length Required 412 - Precondition Failed 413 - Request Entity Too Long 414 - Request URI Too Long 415 - Unsuppo
standard error messages may inform of problems, but they do not usually say how to resolve them or how to get the lost visitor on his way, and they also look dull. You may want to create your own error pages and use them on your web server. The following error messages are the ones customized most often: 400 Bad File Request. Usually means the syntax used in the URL is incorrect (e.g., uppercase letter should be lowercase letter; wrong punctuation marks).401 Unauthorized. Server is looking for some https://support.hostgator.com/articles/plesk/plesk-10/plesk-10-client-side/setting-up-custom-error-documents-on-plesk-10-linux-vps encryption key from the client and is not getting it. Also, wrong password may have been entered.403 Forbidden/Access denied. Similar to 401; a special permission is needed to access the site – a password and/or username if it is a registration issue.404 Not Found. Server cannot find the requested file. File has either been moved or deleted, or the wrong URL or document name http://download1.parallels.com/Plesk/Plesk8.6/Doc/en-US/plesk-8.6-win-administrators-guide/24891.htm was entered. This is the most common error.500 Internal Server Error. Could not retrieve the HTML document because of server-configuration problems.To configure Plesk's web server to show custom error pages for a domain:/ Switch on support for custom error documents through Plesk. Go to Domains > domain name > Setup. Select the Custom Error Documents check box. Click OK.Go to Domains > domain name > Web Directories to see the list of error documents for the root web directory (error documents located here are used for all domain web pages). If you want to customize error pages for a certain web directory, go to that directory.Click Error Documents tab and click the required error document in the list.To use the default document provided by IIS for this error page, select Default in the Type menu.To use a custom HTML document already located in the error_docs
directory on a domain, select File in the Type menu and specify the file name in the Location field. To use a custom HTML document located in directory other than error_docs on a domain, select URL in the Type menu and enter
ProdukteKontoeinstellungenMeine VerlängerungenAbmeldenAnmeldenMenüHilfeSystemstatusZurück|Start Gesamte WebsiteHilfeHosting für Windows (Plesk)Hosting für Windows (Plesk) HilfeKontaktieren Sie uns Landesweit: 9 bis 19 Uhr, Mo-Fr 032 221 094 047 Alternative NummernBerlin: 9 bis 19 Uhr, Mo-Fr030 https://www.godaddy.com/help/set-up-a-custom-404-page-16005 215 029 52München: 9 bis 19 Uhr, Mo-Fr089 380 375 91Landesweit: 9 bis 19 Uhr, Mo-Fr032 221 094 047Set up a custom 404 http://kb.odin.com/en/124357 page404 pages display when someone tries to access a page on your website that doesn't exist. Our hosting accounts allow you to custom error use your home page as your 404 page, or you can create a custom one. Server-side scripts, such as ASP.NET and PHP, might not work on custom 404 pages because of how Web server software (i.e. IIS and Apache) handles them. Log in to your custom error documents GoDaddy account. Click Web Hosting. Next to the hosting account you want to use, click Manage. In the section for the domain you want to use, click Show More. Click Hosting Settings. Select Custom error documents, and then click OK. Click Virtual Directories. Go to the Error Documents tab. Navigate to the second page of errors, and then click 404. In the Location field, enter the URL of the 404 page you want to use, and then click OK. Error docs must be web-visible, i.e. in your httpdocs directory or hosted elsewhere.War dieser Artikel hilfreich?JaNeinVielen Dank für Ihr FeedbackGern geschehen! Können wir sonst noch etwas für Sie tun?Tut uns leid. Wie können wir weiter behilflich sein? AbsendenAbbrechenRelevante ArtikelDatenbankdetails mit Konten für gemeinsames Hosting anzeigenBenötigen Sie weitere Hilfe?Rufen Sie unser preisgekröntes Supportteam anKontaktieren Sie uns
Automation 7.0 Operations Automation 6.x All products Operations Automation 6.0 Operations Automation 5.x All products Operations Automation 5.5 Operations Automation 5.4 Operations Automation 5.3 Operations Automation 5.2 Operations Automation 5.1 Operations Automation 5.0 Operations Automation 2.x All products Operations Automation 2.9 Operations Automation 2.8 Operations Automation 2.7 Operations Automation 2.6 Business Automation All products Business Automation 7.x All products Business Automation 7.0 Business Automation 5.x All products Business Automation 5.5 Business Automation 5.4 Business Automation 5.1 Business Automation 5.0 Business Automation 6.x All products Business Automation 6.0 Business Automation 4.x All products Business Automation 4.4 Business Automation 4.3 Business Automation 4.2 Business Automation 4.1 Odin Business Automation Standard All products Odin Business Automation Standard 4.x All products Odin Business Automation Standard 4.5 Odin Business Automation Standard 4.3 Odin Business Automation Standard 4.2 Odin Business Automation Standard 4.1 Odin Business Automation Standard 4.0 Odin Business Automation Standard 3.x All products Odin Business Automation Standard 3.4 Odin Business Automation Standard 3.3 Odin Business Automation Standard 3.2 Plesk Automation All products Plesk Automation 11.1 Plesk Automation 11.5 Plesk Automation Billing Odin Automation Essentials All products Odin Automation Essentials 6.5 Odin Automation Essentials 7.0 WPB for Automation Service provider products licensing Other All products H-Sphere All products H-Sphere 3.3 H-Sphere 3.4 All products H-Sphere 3.4.1 H-Sphere 3.5 All products H-Sphere 3.5 SPU H-Sphere 3.5.1 Pro Control Panel All products Pro Control Panel Linux All products Pro Control Panel Linux 10.3.0 Pro Control Panel Linux 10.3.4 Pro Control Panel Linux 10.3.5 Pro Control Panel Windows SiteStudio Sphera Helm All products Helm 4 All products Helm 4.0 Helm 4.1 Helm 4.2 Helm 3 Confixx Professional 3 APS All products APS 1.x APS 2.x Custom 404 error pages does't work on windows server. Article ID: 124357, created on Feb 2, 2015, last review on Feb 2, 2015 Applies to: H-Sphere 3.6.3 Symptoms After websites was moved from win1 to win3 server which is a new windows 2008 R2 server. The custom pages for 404 error does not show up. Just the default IIS 7.5 error page appears. In IIS->Error Pages the following warning is shown: You have configured detailed error messages to be returned for both local and remote requests. When this option is selected, custom error configuration is not used. Cause Detailed error messages for remote reques