Top Common Errors in Website

Top Common Errors in Website

5. HTTP Error 401 (Unauthorized)

This error happens when a website visitor tries to access a restricted web page but isn’t authorized to do so, usually because of a failed login attempt.

4. HTTP Error 400 (Bad Request)

This is basically an error message from the web server telling you that the application you are using (e.g., your web browser) accessed it incorrectly or that the request was somehow corrupted on the way.

3. HTTP Error 404 (Not Found)

Most people are bound to recognize this one. A 404 error happens when you try to access a resource on a web server (usually a web page) that doesn’t exist. Some reasons for this happening can for example be a broken link, a mistyped URL, or that the webmaster has moved the requested page somewhere else (or deleted it). To counter the ill effect of broken links, some websites set up custom pages for them (and some of those are really cool).

2. HTTP Error 403 (Forbidden)

This error is similar to the 401 error, but note the difference between unauthorized and forbidden. In this case no login opportunity was available. This can happen, for example, if you try to access a (forbidden) directory on a website.

And the most common HTTP error of all is……….

1. HTTP Error 500 (Internal Server Error)

The description of this error pretty much says it all. It’s a general-purpose error message for when a web server encounters some form of internal error. For example, the web server could be overloaded and therefore unable to handle requests properly.

Judging by Google’s search statistics, this problem is a lot more common than 404 errors.

401 (Unauthorized) ⇒ this error happens when someone tries to access a page for which they are not authorized. You can usually fix this error by reviewing the URL of the page that is causing the error; it’s possible that the link clicked is one that is for authorized users only (for example, users who have logins with a valid user ID and password).

403 (Forbidden) ⇒ this error occurs when a server will not complete a request because a user isn’t allowed to access Slightly different than a 401 error, a 403 error recognizes that a user may be logged in with a valid user ID and password, but does not have authorization to access the specific page. Typically, this means the user have access granted by the website administrator.

404 (Not Found) ⇒ this error is one that most people see on a regular basis, unfortunately. A 404 error occurs when a user tries to access a webpage that doesn’t (or no longer) exists. The causes of this error could be from broken links, incorrect URLs, or a redirected page that is no longer valid. This error can easily be fixed, however, by reviewing your Google Search Console crawl errors, and submitting broken link re-directs for these errors in WordPress or other content management system, or having your web developers add in the redirects for you.

500 (Internal Server Error) ⇒ this error is definitely the most common error seen, and it’s pretty much just a generic error message for any type of internal server error that cannot be easily defined. This error can usually be fixed when the user refreshes their web browser (if the error is related to the server being busy and unable to process requests quickly enough), deletes their cookies, or visits the page at another time, possibly when the server isn’t so overloaded. On your end, however, you can usually troubleshoot the cause of the error through your WordPress or content management system, and follow the steps to diagnose and fix the issue.

502 Bad Gateway

The 502 status code, or Bad Gateway error, means that the server is a gateway or proxy server, and it is not receiving a valid response from the backend servers that should actually fulfill the request.

If the server in question is a reverse proxy server, such as a load balancer, here are a few things to check:

• The backend servers (where the HTTP requests are being forwarded to) are healthy
• The reverse proxy is configured properly, with the proper backends specified
• The network connection between the backend servers and reverse proxy server is healthy. If the servers can communicate on other ports, make sure that the firewall is allowing the traffic between them
• If your web application is configured to listen on a socket, ensure that the socket exists in the correct location and that it has the proper permissions

503 Service Unavailable

The 503 status code, or Service Unavailable error, means that the server is overloaded or under maintenance. This error implies that the service should become available at some point.

If the server is not under maintenance, this can indicate that the server does not have enough CPU or memory resources to handle all of the incoming requests, or that the web server needs to be configured to allow more users, threads, or processes.

504 (Gateway timeout) ⇒ another common one, a 504 error signifies a gateway timeout, which happens when one server did not receive a timely response from another server when it was attempting to load the page. Most of the time this issue is not the fault of a website, but there are a few ways to troubleshoot the error. If it’s a result of a corrupted database and your website is on WordPress, you can install and run WP-DBManager to repair and optimize your database. It might also be an issue relating to your .htaaccess filewithin WordPress. Or you could try contacting your hosting company, to see if the issue is on their end.