How to Fix Common Website Errors (404, 403, 500, 508)
Last updated Changelog
On this page
When something’s wrong with a website, the browser shows an error page with a number. Here’s what the common ones look like on our servers, and how to fix them. We made each error on purpose on our test site, store.cranedemo.com.
404 Not Found

The page or file doesn’t exist at that address.
- Check the address for typos. Capital letters matter:
About.htmlandabout.htmlare different files. - Check the file is in the right folder: domains › your domain › public_html. See File Manager.
- On WordPress, if every page except the home page shows 404, log in to WordPress, go to Settings › Permalinks and click Save Changes. That rewrites the
.htaccessfile WordPress needs.
Tip: You can make this page match your site: see Custom error pages.
403 Forbidden

The file exists, but the server won’t show it. We caused this one by removing all permissions from a file.
- Check the permissions. In File Manager, tick the file and choose More › Set permissions. Files should be
644and folders755. - Check you haven’t blocked yourself. A blocked IP address gets 403 on every page. See Block an IP address.
- Check
.htaccess. ADenyorRequireline in the folder’s.htaccessfile can block everyone.
500 Internal Server Error

The website’s code crashed. In Chrome it looks like this; other browsers show a plain 500 Internal Server Error. We caused it with a PHP file that calls a function that doesn’t exist.
- Undo the last change. On WordPress, it’s usually a plugin or theme you just installed or updated. Rename that plugin’s folder in
wp-content/pluginswith File Manager to switch it off, and the site comes back. - Check your PHP version. If the site broke right after you changed PHP version, switch back: see PHP version and settings.
- Still stuck? PHP’s error messages don’t show up in DirectAdmin’s logs. Contact support with the page address and the time you saw the error, and we’ll look up the exact message for you.
508 Resource Limit Is Reached
Your site used all the memory or processes your plan allows, so the server turned some visitors away for a moment. See Check your CPU and memory usage for which limit it hit and what to do.
Troubleshooting
| Problem | What to do |
|---|---|
| “Error establishing a database connection” (WordPress) | The database details in wp-config.php don’t match. Check the database name, user and password in Databases. |
| “Your connection is not private” | The site’s SSL certificate is missing or doesn’t cover that address yet. See Free SSL. |
| “ERR_TOO_MANY_REDIRECTS” | Two redirects send visitors back and forth. Check your redirects, and that your WordPress address under Settings › General starts with https://. |
| The error only shows for you | Clear your browser cache, or try a private window or another network. If others can see the site, your IP address may be blocked. |
Snagged on something? Contact support and we’ll get you sorted.