When loading a web page, you may occasionally see a status code instead of the page. When you get a status code, it can initially be confusing, but once you know what the code means, the problem is usually quite easy to fix.
Status codes for websites can be categorised by the number they begin with.
Here are some of the most common statuses that you will see:
This is the status code that is returned when everything works and the server has completed its action without running into any issues. You will only really see this code if you’re running a browser add-on or using command-line tools.
This appears when you are attempting to view a file that cannot be found. It may have a different name, be in a different location, or it may not exist on that server.
If your file is in the right place, with the right name, it may be that the domain name points to a different server than the one your files are on.
To check whether your domain name is pointing to the right server:
There might also be rewrites or redirects in place that move the browser from the correct file to a file that does not exist. You can check this on your Linux account by looking for the .htaccess, and on your Windows account by looking for the web.config.
The 403 error usually appears when your site’s files or folders have permissions set so they cannot be read, the file is in a format the server does not recognise, or that your site is disabled.
We do occasionally disable websites due to it being compromised, using too much of the server’s resources, and other such reasons. If you check your account, you should see a notification from us if this has happened, along with an explanation.
If the permissions are set so that people cannot access the file, you need to set the permissions to be more publicly accessible. In the eXtend Control Panel’s File Manager, you can select the file and check the permissions. In general, 644 for files and 755 for folders are considered good permissions to give. If the permissions are too liberal and could cause a security risk, the file will be highlighted in red in your File Manager.
If your 403 error also has a 404 error, this can happen when the file isn’t recognised by the server. This primarily occurs with home pages, since the server looks for an index.[filetype] first, such as index.html, index.php, index.cgi, and index.htm. However, you can configure the .htaccess or web.config file in your hosting package to accept whatever file you want to use.
The 500 error is a wide-ranging error and means that, in most cases, there is an issue in the file’s code preventing it from being properly interpreted by the server. This can be due to the configuration files, such as .htaccess, or the actual code within in the file.
To diagnose a 500 error, you must check the error logs for that website, which will have the details of the error, including the line of code where the issue arises and usually a more specific error message for you to troubleshoot.
You can find your error logs in your eXtend Control Panel, under ‘Log File Download’.
And here is the full list of website status codes:
Article ID: 575
Created On: Wed, Apr 1, 2015 at 11:47 AM
Last Updated On: Thu, Apr 23, 2015 at 12:38 PM
Online URL: https://www.heartinternet.uk/support/article/what-does-this-website-status-code-mean.html