Understanding Common HTTP Error Codes
When visiting a website, you may occasionally encounter error pages instead of the content you expected. Understanding what these errors mean can help you troubleshoot issues with your own website or know when to contact support.
400 Bad Request
What it means: The server cannot process the request due to something perceived as a client-side error, such as malformed syntax or an invalid URL.
Common causes: Corrupted browser cache or cookies, URL that is too long, or uploading a file that exceeds the server's size limit.
How to fix: Clear your browser cache and cookies, check the URL for typos, or try a different browser.
401 Unauthorised
What it means: The requested page requires authentication. You need to log in with valid credentials to access it.
Common causes: Incorrect login credentials, expired session, or a password-protected directory.
How to fix: Double-check your username and password. If you've set up directory protection in cPanel, ensure you're using the correct credentials.
403 Forbidden
What it means: The server understands your request but refuses to fulfil it. Unlike 401, authentication won't help.
Common causes: Incorrect file permissions, no index file in the directory, IP address blocked, or .htaccess rules blocking access.
How to fix: Check file permissions in cPanel's File Manager (files should typically be 644, folders 755). Ensure you have an index.html or index.php file in your website's root directory. Review your .htaccess file for any blocking rules.
404 Not Found
What it means: The server cannot find the requested page. This is the most common error visitors encounter.
Common causes: The page has been deleted or moved, the URL contains a typo, or a broken link is pointing to a page that no longer exists.
How to fix: Check for typos in the URL. If the page was moved, set up a redirect in cPanel or via .htaccess. Use a broken link checker to find and fix broken links on your site.
500 Internal Server Error
What it means: A generic error indicating something has gone wrong on the server, but the server cannot be more specific about the problem.
Common causes: Syntax errors in .htaccess files, PHP errors in your scripts, exhausted PHP memory limits, or incorrect file permissions.
How to fix: Check your error logs in cPanel (Metrics > Errors) for specific details. Review any recent changes to .htaccess or PHP files. Try renaming your .htaccess file temporarily to see if that resolves the issue.
502 Bad Gateway
What it means: The server received an invalid response from an upstream server while trying to fulfil the request.
Common causes: Server overload, network connectivity issues between servers, or a faulty proxy configuration.
How to fix: Wait a few minutes and try again. Clear your browser cache. If the problem persists, contact our support team.
503 Service Unavailable
What it means: The server is temporarily unable to handle the request, usually due to maintenance or overloading.
Common causes: Server maintenance, too many simultaneous connections, or resource limits being exceeded.
How to fix: Wait a few minutes and refresh the page. If you're seeing this on your own website frequently, you may need to optimise your site's resource usage or consider upgrading your hosting plan.
504 Gateway Timeout
What it means: The server didn't receive a timely response from an upstream server needed to complete the request.
Common causes: Slow PHP scripts, database queries taking too long, or network issues between servers.
How to fix: Optimise slow database queries, increase PHP execution time limits if possible, or break large operations into smaller tasks. Check your error logs for more details.
Need Help?
If you're experiencing persistent errors on your website and can't resolve them, please open a support ticket and include the specific error code, the URL where you're seeing the error, and any recent changes you've made to your website.
