HTTP Error Codes

There are many different error codes that can be presented from a server when things go wrong. These can be used to help troubleshoot the main cause of the issue and fix the issue as soon as possible. The first digit of the status code a website gives allows us a broad understanding or group of what the issue may be.

  • 1## – These codes are usually informational and not used to identify errors
  • 2## – These codes represent a success, normally in regards to connecting to the server
  • 3## – These codes imply a permanent or temporary redirection of the page you are visiting
  • 4## – This is a client error code, and normally means the error is caused by the user connecting to the server
  • 5## – This is a server error code, letting the user know that the issue is caused on the server’s side


500 Internal Service Error


A 500 error often will say something similar to this:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

What causes a 500 internal server error?

When a site prompts a 500 Internal Server Error to show, it means it knows there’s a problem and wasn’t able to deliver on whatever was requested for an unknown reason. Many times, this error comes from a problem in the configuration of a script, but you aren’t provided any details about the exact problem.

Common causes:

  • Problems with the .htaccess file
  • Problems with the php.ini file
  • Permissions not set properly
  • Problems with script requests
  • Ownership not set properly

It can be tricky to find the exact cause, but you should first look in cPanel’s error logs. If that doesn’t help you identify the problem, please contact us so we can help you get it fixed.


502 Bad Gateway


A 502 error normally does not give a good description when it occurs.

What causes a 502 Bad Gateway error?

When a site prompts a 502 Bad Gateway Error to show, it means that the server is a gateway or a proxy that forwards the request to another backend server, and that it is not receiving a valid response to fulfill the request.

Common causes:

  • Backend servers are not healthy (Where the HTTP Requests are being forwarded to)
  • The reverse proxy is configured improperly, or with the invalid backends specified*
  • The connection between the backend servers and reverse proxy server Is unhealthy and needs to be checked on or the firewall is not allowing traffic from one or the other
  • The web application listening on a socket that is in the incorrect location or has improper permissions.

It can be tricky to find the exact cause, but you should first look in cPanel’s error logs. If that doesn’t help you identify the problem, please contact us so we can help you get it fixed.


400 bad request error


A 400 Bad Request Error is another common HTTP status code. You’ll see this when the site receives a corrupt or problematic request to do something, such as run a script or simply display the content of a page.

If you’re seeing a 400 bad request error, first make sure you’re trying to access the correct URL. If so, try to clear your cookies and your cache. If that doesn’t work, clear your DNS cache. If all else fails, contact us and let us help you get it fixed.


401 Unauthorized error


The 401 Unauthorized Error is another HTTP status code, except this one means that the user trying to access the specific resource from the server either has not been authenticated, or they have not been authenticated correctly. This is not caused by having different permissions on the file, this is more caused when a user does not enter in the correct username and password, which will exist in the .htpasswd file on the server in that same directory.

The .htpasswd file cannot be seen from the browser, as most configurations hide these types of files by default.

To resolve this error, make sure that you enter the correct username and password as you may have set up in the .htpasswd file.


403 Forbidden error


The 403 Forbidden Error occurs when the user is requesting a resource from the server, where the user or server do not have access to read or execute the file. It is commonly recommended for files to have their permissions set to 755 for directories and 644 for files. This essentially means that the user of the directory can read, write and execute, the assigned group of the files can read and execute, but not write to, and that everyone else that is not included can read and execute the files but not write.

File permissions on a Linux server can be changed within cPanel, here, or you can modify the file permissions from the command line, in which case you can use this article here.


404 Not Found error


The 404 Not Found error can be caused by multiple things. The reason this error code will show up is because the resource or file that a user is looking for is not there. This can be caused either by the coding of the site, someone else’s site, or due to user fault, by typing in the wrong url.

To fix this if it is a coding issue on your site, go through your code, usually using the built in find feature in most text editors, and find the link that is leading your users to an invalid page and correct. For the most part, these are typically just Typos.


If you should have any questions or would like assistance, do feel free to contact us through Live Chat, on our Phones, or by submitting a ticket with our Technical Support team.


Leave a Reply

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