Common Web Hosting Web Page Errors & What do the error codes mean?

Common Web Hosting Web Page Errors & What do the error codes mean?
Like Tweet Pin it Share Share Email
Web Hosting Web Page Errors
Web Hosting Web Page Errors

The following article discusses the meaning of error codes that may appear in your browser window. When a problem occurs loading a webpage, an error code and message will appear in the browser instead of the webpage. The error code and message that appears is determined by the type of error. Typically the error code consists of a 3 to 4 digit number and a brief message describing the error. Below, you will find a list of the common error codes and some suggestions for resolving them.

Here’s a quick guide to help you understand the most common error codes with suggestions for what to do to fix the error:

500 Internal Server Error

This error message occurs when the server fails to process a script that is being run. The error message will typically contain information relating to the script failure. The resolution to this type of error will be based around the additional information provided in the error message. If you do not see additional information, please ensure that Show friendly HTTP error messages is unchecked.

What causes 500 Internal Server Errors?

Here are the three most common reasons:

  1. Incorrect file permissons – Most commonly having a file as “world” writeable. This is a very common issue with PHP files. In general on our servers, PHP file permissions should not be higher than 775. Keep in mind too that the permissions of the parent folders/directories need to be set correctly too.
  2. Leaving file permissions set incorrectly after manual installation of content management systems, forums, blogs, etc.
  3. Coding errors in the .htaccess file.

Fixing The 500 Internal Server Error In WordPress.

404 error not found pages

This error message occurs when the page that is requested does not exist on the server. This can occur if the user mistypes the name of the page, or attempts to load a page that no longer exists. One solution is to create a custom 404 error page that provides the user more detailed information and navigation so they can continue browsing your website. Instructions for configuring a custom 404 error page for a Windows account can be found here. Instructions for a Linux account can be found here.

The following is a complete list of client and server error messages:

4xx – Client Error
A client error is one that occurs on the users computer. For example, the user may request a page that does not exist, or the user may not provide valid authentication information.

400Bad request.
401Access denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
401.1Logon failed.
401.2Logon failed due to server configuration.
401.3Unauthorized due to ACL on resource.
401.4Authorization failed by filter.
401.5Authorization failed by ISAPI/CGI application.
401.7Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0.
403Forbidden. IIS defines a number of different 403 errors that indicate a more specific cause of the error:
403.1Execute access forbidden.
403.2Read access forbidden.
403.3Write access forbidden.
403.4SSL required.
403.5SSL 128 required.
403.6IP address rejected.
403.7Client certificate required.
403.8Site access denied.
403.9Too many users.
403.10Invalid configuration.
403.11Password change.
403.12Mapper denied access.
403.13Client certificate revoked.
403.14Directory listing denied.
403.15Client Access Licenses exceeded.
403.16Client certificate is untrusted or invalid.
403.17Client certificate has expired or is not yet valid.
403.18Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.
403.19Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.
403.20Passport logon failed. This error code is specific to IIS 6.0.
404Not found.
404.0(None) – File or directory not found.
404.1Web site not accessible on the requested port.
404.2Web service extension lockdown policy prevents this request.
404.3MIME map policy prevents this request.
405HTTP verb used to access this page is not allowed (method not allowed.)
406Client browser does not accept the MIME type of the requested page.
407Proxy authentication required.
412Precondition failed.
413Request entity too large.
414Request-URI too long.
415Unsupported media type.
416Requested range not satisfiable.
417Execution failed.
423Locked error.

5xx – Server Error

A server error is one that occurs on the server when the page is requested in a browser. The server cannot complete the request because it encounters an error.

500Internal server error.
500.12Application is busy restarting on the Web server.
500.13Web server is too busy.
500.15Direct requests for Global.asa are not allowed.
500.16UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
500.18URL authorization store cannot be opened. This error code is specific to IIS 6.0.
500.100Internal ASP error.
501Header values specify a configuration that is not implemented.
502Web server received an invalid response while acting as a gateway or proxy.
502.1CGI application timeout.
502.2Error in CGI application.
503Service unavailable. This error code is specific to IIS 6.0.
504Gateway timeout.
505HTTP version not supported.

Additional information about less common error codes and messages can be found on Microsoft’s website.

User Review
0 (0 votes)

Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.

Want Exclusive Blogging Tips?


Signup For Access To Free Blogging Tips, WordPress, Make Money Online Tips & Resources
Give it a try, you can unsubscribe anytime.