Errors can appear on websites for a number of reasons. Usually, these issues are quick to diagnose and fix, but sometimes further investigation may be required. Below are the most common error messages people experience when browsing websites (credit to Pingdom for supplying these)
HTTP error 400 (bad request)
This is 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.
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.
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, for example, happen if you try to access a (forbidden) directory on a website.
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).
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.
What should I do?
The first thing you should do upon experiencing an error/issue is log in to your cPanel account and click on the Error Logs option (found under the Logs section). This page will display the last 300 errors that appeared on your website. File Not Found/Missing errors usually are not the culprit of such issues. You should look out for warnings. Sometimes these warnings are very self-explanatory and explain exactly what the issue is. For example, you might see a Permission Denied error which usually comes down to a file or folder having invalid CHMOD permissions. CHMOD Permissions can be adjusted via cPanel –> File Manager. For the correct permissions to use, you should consult with the developer of the script (their website will usually have this information). Another common one is perhaps misspelled or defined by a module not included in the server configuration which is usually caused by a faulty/non-compatible flag in the .htaccess file. The best way to test if this is the case is to rename your .htaccess file (usually found within public_html) to .htaccess_bak and then re-test your website to see if the error still appears.
Generally speaking, the quickest and easiest way to move forward with such issues is to contact our technical support team who will be happy to help you out.