When a server could not establish a proper connection to process data, it shows errors. This includes- 404 not found, 400 Bad Request, 500 Internal Server Error and so on. Lets’ take a look at different common server errors and their solutions.

404 Not Found

This is the most common error among others. This is not a major issue or technical failure of a server. This occurs when the requested file, page or data could not be found on the server. This could happen because of both client and users failure to locate a file, page or data properly. If one file, page or data is moved to another direction, but the URL is not modified, this could appear to the browser. Not only this but also users failure to type an URL correctly may cause this issue.

Solution: Reload the page again and check the URL is entered correctly. For further issues, it is advised to contact the webmaster or site authority.

400 Bad Request

400 Bad Request is a HyperText Transfer Protocol (HTTP) error response which is occurred in clients end. This happens when a server is unable to process a request due to syntax error. Besides, this could happen due to an explicit file size which crosses the bandwidth and other resources limit to process.

Moreover, an invalid or expired cookie of the browser can also be responsible for this problem. Web server identifies you via browser cookie and process requests through a session cookie. If accidentally your session token matches the session token of another request, 400 Bad Request could happen. Also, malicious cookies could cause this problem.

Solution: First, check your requested URL before going for further steps. If the URL is correct, then clear the relevant cookie. If this problem happens while uploading a file, try uploading a small file. Logout and log back in may give you the solution while using any user authentication form. Don’t forget to clear the relevant cookie before log back in.

500 Internal Server Error

Like above, this 500 Internal Server Error is another HyperText Transfer Protocol (HTTP) error response, which means something has gone wrong in the webserver. When the server could not specify the exact problem, it shows this error message.

Solution: This is a sever end problem. So, users don’t have many things to do. If your site faces this error, then check your file permission first. Incorrect permission of PHP and CGI script may cause this problem. Generally, the right permission is 0755 (-rwxr-xr-x).
Check your .htaccess file if you are not using any common .htaccess. Custom .htaccess with error may cause this issue.