Common Website Errors and How to Fix Them (500, 404, etc.)

There are few things more stressful for a website owner than visiting your own site only to be met with a cryptic error message. These errors can seem alarming, but in most cases, they are pointing to a specific, fixable problem. Understanding what these common errors mean is the first step to resolving them quickly and getting your site back online.

This guide is your first-aid kit for troubleshooting the most common website errors. We’ll explain what they mean in plain English and provide actionable steps to fix them.

---

1. 500 Internal Server Error

This is one of the most common and most frustrating errors because it’s so vague. It simply means that something went wrong on the server, but the server couldn’t tell you what the specific issue was.

• Common Causes: A faulty plugin or theme, a corrupted .htaccess file, or exceeding your server’s PHP memory limit.
• How to Fix It:
  1. Check for a Corrupt .htaccess File: Log in to your site’s files via FTP or File Manager, find the .htaccess file, and rename it to something like .htaccess_old. Try reloading your site. If it works, the file was corrupt. For WordPress users, go to Settings > Permalinks and click “Save Changes” to generate a new, clean .htaccess file.
  2. Deactivate Plugins and Themes: A recent plugin or theme update is a very common culprit. If you can access your WordPress admin, deactivate all your plugins. If the error disappears, reactivate them one by one until you find the one causing the problem. If you can’t access your admin, use FTP or File Manager to rename the plugins folder inside wp-content, which will deactivate all of them.
  3. Increase PHP Memory Limit: Your host sets a limit on how much memory a script can use. If your site is hitting that limit, it can cause a 500 error. You may need to contact your host to have this limit increased.

---

2. 404 Not Found

A 404 error is much less critical than a 500 error. It means the server is working perfectly, but it simply couldn’t find the specific page or file that was requested.

• Common Causes: A visitor mistyped a URL, you have a broken link on your site, or you moved or deleted a page without setting up a redirect.
• How to Fix It:
  1. Check the URL: The most common cause is simply a typo in the address bar.
  2. Fix Permalinks (WordPress): Sometimes the permalink structure in WordPress can become corrupted. The fix is incredibly simple: go to Settings > Permalinks in your WordPress dashboard and just click the “Save Changes” button without making any changes. This forces WordPress to rebuild the rules it uses to create URLs.
  3. Set Up 301 Redirects: If you have intentionally changed the URL of a page, you need to set up a 301 redirect from the old URL to the new one. This tells browsers and search engines that the page has moved permanently, and it prevents visitors from seeing a 404 page.

---

3. Error Establishing a Database Connection (WordPress)

This error is specific to database-driven platforms like WordPress. It means that your website’s files are unable to communicate with the MySQL database that stores all of your content.

• Common Causes: The database login credentials in your wp-config.php file are incorrect, your database has become corrupted, or your database server is down.
• How to Fix It:
  1. Check Your wp-config.php File: This is the most common cause. Open your wp-config.php file and verify that the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST values are correct. These details are provided by your web host.
  2. Check Your Database Server: The server that hosts your database might be down. This is especially common on cheap, unreliable shared hosting. Contact your web host’s support to ask if there are any issues with the MySQL server.
  3. Repair the Database: WordPress has a built-in database repair mode. You can enable it by adding the line define('WP_ALLOW_REPAIR', true); to your wp-config.php file. Then, navigate to yourdomain.com/wp-admin/maint/repair.php to run the repair tool.

---

4. 403 Forbidden

This error means that the server understood the request, but it is refusing to grant access. You simply don’t have the necessary permissions to view the requested file or page.

• Common Causes: Incorrect file or folder permissions on your server, a misconfigured security plugin, or a rule in your .htaccess file that is blocking access.
• How to Fix It:
  1. Reset File Permissions: File and folder permissions control who can read, write, and execute them. Incorrect permissions can cause a 403 error. Typically, folders should be set to 755 and files to 644. You can change these using an FTP client or your host’s File Manager.
  2. Check Your .htaccess File: Look for any rules that contain the word Deny. These rules can be used to block access from certain IP addresses or to protect certain files. A misconfiguration here could be the cause.
  3. Temporarily Disable Security Plugins: A security plugin might be overly aggressive and incorrectly identify a legitimate request as a threat. Try temporarily deactivating your security plugins to see if that resolves the issue.

---

When in Doubt, Contact Your Host

While you can fix many errors yourself, remember that you are paying for a hosting service that includes support. If you’ve tried these basic troubleshooting steps and are still stuck, don’t hesitate to contact your web host’s support team. A good host will be able to check the server logs, identify the root cause of the problem, and help you get your site back online.