This article explains the most common website errors, what usually causes them, and how to fix them.
Finding the real error
Error pages rarely say what went wrong. The details are usually in an error log:
- In cPanel, under Metrics, click Errors to see the latest web server errors.
- Look for a file named
error_login the folder of the page that isn't working (oftenpublic_html). It lists PHP errors with the file and line number.
500 Internal Server Error
Something on the server side stopped the page from loading. Common causes:
- Wrong file permissions. Files should be 644 and folders 755. Files or folders writable by everyone (such as 777) are blocked on our servers and cause this error. Fix permissions in File Manager.
- A bad rule in
.htaccess. Rename.htaccessto.htaccess-oldand reload the page. If the error goes away, the problem is in that file. - A PHP error. Check the
error_logfile. In WordPress, this is often a recently installed or updated plugin.
403 Forbidden
The server is refusing access to the page. Common causes:
- There's no
index.htmlorindex.phpfile in the folder. - Permissions are too restrictive. Check that files are 644 and folders 755.
- An
.htaccessrule or security plugin is blocking your IP address.
404 Not Found
The page or file doesn't exist at that address.
- Check the spelling of the address. File names on our servers are case-sensitive, so
Photo.jpgandphoto.jpgare different files. - Make sure the files were uploaded to the correct folder, usually
public_html. - In WordPress, if every page except the home page shows a 404, go to Settings > Permalinks and click Save Changes without changing anything.
503 or 508 "Resource Limit Reached"
Your account has temporarily used all of the memory, CPU or processes included in your plan. It usually clears up within a few minutes. If it keeps happening:
- Check Resource Usage in cPanel (under Metrics) to see which limit is being hit.
- Turn on caching. For WordPress, we recommend the LiteSpeed Cache plugin.
- Block heavy bot traffic, and remove unused plugins.
- If your site has simply outgrown its plan, consider upgrading.
Blank white page
This is almost always a PHP error that isn't being shown on screen. Check the error_log file. In WordPress, you can disable all plugins by renaming the wp-content/plugins folder to plugins-old in File Manager, then rename it back once you've logged in.
"This site can't be reached"
Your domain isn't pointing to our server, or DNS is still propagating. See Pointing your domain to 247-Host and DNS propagation: why changes take time. Also check that your domain hasn't expired.
Still stuck?
Open a support ticket and include the exact address showing the error, what you were doing when it started, and any recent changes (a new plugin, an update, or a file edit). We can check the server logs for you.
Please note that fixing errors in custom code, themes or plugins is outside the scope of our support. In those cases we'll tell you what the logs show so you can pass it on to your developer.
