How to fix common HTTP error codes Print

  • 0

CodeMeaningWhat to try
400 Bad RequestThe browser sent a request the server couldn't understandClear browser cache and cookies; check the URL
401 UnauthorisedLogin neededCheck the username/password for a protected folder
403 ForbiddenAccess deniedCheck permissions (folders 755, files 644), an index file exists, and .htaccess isn't blocking you
404 Not FoundThe page doesn't existCheck the file exists with the exact name (names are case-sensitive); for WordPress re-save Settings › Permalinks
500 Internal Server ErrorSomething failed on the serverCheck the error log; rename .htaccess to test; check recent plugin/theme changes
503 Service UnavailableServer busy or resource limit reachedCheck Resource Usage in cPanel; enable caching
508 Resource Limit ReachedYour account hit its LVE limitsSee How to understand resource limits

If the error affects every site on your account or you can't find a cause, raise a ticket with the URL and the time you saw the error.


Was this answer helpful?

« Back