Web Design & Development · 7 min read · 1,527 words

WordPress 500 Internal Server Error: 5 Fixes in Order

WordPress 500 Internal Server Error: 5 Fixes in Order

Quick answer

A 500 Internal Server Error on WordPress means the server hit a problem it could not describe more precisely. The usual causes are a corrupted .htaccess file, a faulty plugin or theme, or PHP running out of memory. Take a backup, then rename .htaccess, switch plugins off, try a default theme and check the error log.

This guide explains what the error means, the order to check things in so you fix it without making it worse, how to read the error log, and when to stop and hand it to someone with server access. It is written for small business owners who manage their own WordPress site or are trying to understand what their developer or host is doing.

What a 500 error actually means

A 500 error is the web server’s way of saying something went wrong and it does not have a more specific message to give. MDN’s reference on HTTP status codes describes it as a generic catch-all response for server issues, used when the server cannot find a more appropriate error to return.

That vagueness is the frustrating part. The page itself tells you almost nothing; the useful detail is in the server’s error log. On a WordPress site, though, the list of likely causes is short, and working through it in order fixes most cases.

First: check whether it is the whole site or one page

What you see Likely area
Every page, including the homepage and admin, shows a 500 .htaccess, a plugin or theme loaded everywhere, PHP memory, or the server
Only the admin area shows a 500 An admin-side plugin, memory limits on heavier admin screens
Only one page or feature, such as checkout or a form The plugin or code behind that feature
It appeared straight after an update or a new plugin That update or plugin, almost certainly
It comes and goes under busy traffic Server resources or hosting limits

Also note exactly what changed recently. An update, a new plugin, a settings change or a hosting change is the most valuable clue you have.

Before you touch anything: take a backup

Every fix below involves changing files on the server. Take a full backup of files and database first, from your hosting control panel if you cannot reach the WordPress dashboard. If your host keeps daily backups, check when the last one ran; restoring the version from just before the problem started is sometimes the quickest fix of all, especially on a site that takes bookings or payments. Our guide to WordPress maintenance covers backup habits that make this painless.

Six-step order for fixing a WordPress 500 Internal Server Error, from backing up to reading the error log
Change one thing at a time and test after each step.

The fix order, step by step

The WordPress documentation on common errors sets out a sensible sequence for an internal server error. Here it is in plain terms:

  1. Rename the .htaccess file. Using your host’s file manager or FTP, find .htaccess in the site’s main folder and rename it to something like .htaccess_old. Reload the site. If it works, go to Settings, then Permalinks, in the dashboard and click Save to generate a fresh file. The documentation calls a corrupted .htaccess the most likely issue.
  2. Switch off all plugins. If you can reach the dashboard, deactivate them all. If not, rename the plugins folder inside wp-content, which disables every plugin at once. If the site comes back, rename the folder back and reactivate plugins one at a time until the error returns. The last one you switched on is the culprit.
  3. Switch to a default theme. If plugins are not the cause, temporarily activate a default WordPress theme. If the site recovers, the problem is in your theme or its customisations.
  4. Raise the PHP memory limit. Heavy plugins, page builders and large imports can exhaust the memory WordPress is allowed. Your host can raise it, or a developer can set it in the configuration.
  5. Replace the WordPress core folders. As a last DIY step, the documentation suggests re-uploading the wp-admin and wp-includes folders from a fresh copy of WordPress. Do not touch wp-content, which holds your themes, plugins and uploads.

Work through one step at a time and test after each. Changing several things at once makes it impossible to tell what fixed it, or what broke something else.

Reading the error log

If the steps above do not reveal the cause, the error log usually will. There are two places to look:

  • Your hosting control panel. Most hosts show a PHP or server error log. Look for entries timed when you loaded the broken page. Lines mentioning “Fatal error” usually name the file, and the file path usually names the plugin or theme.
  • WordPress’s own debug log. WordPress’s debugging documentation explains how to turn on WP_DEBUG and WP_DEBUG_LOG in the wp-config.php file, which writes errors to a debug.log file in the wp-content folder. Setting WP_DEBUG_DISPLAY to false keeps errors off the public pages.

The same documentation warns that debug tools are not recommended on live sites and are meant for local testing and staging. If you switch logging on to diagnose a live problem, switch it off again once you have what you need, and delete the log file, which can contain information you would not want public.

Common causes and their fixes

Cause Clue Fix
Corrupted .htaccess Whole site down; often after a plugin edits rewrite rules Rename and regenerate via Permalinks
Faulty plugin update Error started right after an update Disable it, restore the previous version, report it to the author
Plugin conflict Two plugins doing similar jobs, such as two caching or security plugins Keep one
Theme error Recovers on a default theme Undo recent theme edits or update the theme
PHP memory exhausted Log mentions “Allowed memory size exhausted” Raise the memory limit; review heavy plugins
PHP version mismatch Started after the host changed PHP version Update plugins and theme, or ask the host to adjust
File permissions Started after a migration or file upload Ask your host to reset permissions
Server overload Comes and goes at busy times Better hosting or caching

What not to do

  • Do not delete plugins to test them. Deactivating or renaming is enough; deleting can lose settings.
  • Do not reinstall WordPress over the top without a backup and without leaving wp-content alone.
  • Do not edit wp-config.php unless you are comfortable and have a copy of the original.
  • Do not keep running updates hoping one will fix it. Stabilise the site first.
  • Do not ignore a 500 that keeps coming back. Intermittent errors usually point to a hosting or resource problem that will get worse.

When it might be something more serious

Occasionally a 500 error is a symptom of a compromised site: unfamiliar files, plugins you did not install, or redirects to strange pages alongside the error. If you see any of those, treat it as a security incident rather than a simple error. Our guide on what to do if your website is hacked sets out the steps, and our WordPress security guide covers prevention.

Preventing it next time

  1. Keep automatic daily backups, stored away from the website itself, and check now and then that one restores.
  2. Update plugins in small batches rather than all at once, so a fault is easy to trace.
  3. Test major updates on a staging copy first if the site takes payments or bookings.
  4. Remove plugins you no longer use, and avoid two plugins that do the same job.
  5. Keep a short note of every change you make, with the date. It turns the next fault into a five-minute job.

When to hand it over

Stop and get help if you cannot reach your hosting control panel or files, if the error log points to something you do not understand, if the site takes payments or bookings and every hour offline costs money, or if you have already tried the steps above. A developer or a good host can usually read the log and fix a straightforward 500 quickly.

If problems like this keep happening, the underlying issue is often maintenance: plugins updated without testing, no reliable backups and no one watching the site. Our Website Management and Hosting is £20 a month and includes UK hosting, SSL, daily backups, security monitoring, automatic updates and up to three business email mailboxes. If the site is old, fragile and hard to update, our custom WordPress websites start at £499, hand-coded without page builders. All prices are on our pricing page. You can order online or email support@luxbranding.co.uk.

Free resource

Get the UK Website Project Brief Template (free)

A two-page template for briefing any UK web designer: sitemap, integrations, audience and deliverables. Cuts revision rounds in half.

No spam. UK GDPR compliant. We only use your email to send this resource, unless you tick the box to hear from us.

Frequently asked questions

What causes a 500 Internal Server Error in WordPress? +

The most common causes are a corrupted .htaccess file, a faulty or conflicting plugin, a theme error and PHP running out of memory. Less often it is a PHP version change, wrong file permissions or an overloaded server. The error page itself gives no detail, so the server or WordPress error log is where the real cause is recorded.

How do I fix a 500 error if I cannot log in to WordPress? +

Use your hosting control panel's file manager or FTP. Rename the .htaccess file and reload the site. If that does not help, rename the plugins folder inside wp-content to disable every plugin at once. If the site returns, rename it back and reactivate plugins one by one in the dashboard to find the culprit.

Is it safe to turn on WP_DEBUG on a live site? +

WordPress's own documentation says debug tools are not recommended on live sites and are meant for local testing and staging. If you must use logging to diagnose a live problem, set WP_DEBUG_DISPLAY to false so errors stay off public pages, switch logging off afterwards and delete the debug.log file.

What is the difference between a 500 and a 503 error? +

A 500 is a generic error meaning the server hit an unexpected problem it could not describe more precisely, often caused by code or configuration on the site. A 503 means the server is temporarily unable to handle requests, often because of overload, hosting limits or maintenance mode. The fixes overlap, but a 500 usually points to the site itself.

Can Luxbranding look after my WordPress site so this does not happen? +

Our Website Management and Hosting is £20 a month and includes UK hosting, SSL, daily backups, security monitoring, automatic updates and up to three business email mailboxes. If your site is old and fragile, custom WordPress websites start at £499, hand-coded without page builders. You can order online or email support@luxbranding.co.uk.

Work With Us

Need help with your brand or website?

Luxbranding is a UK online creative agency. Fixed prices, unlimited revisions, 48-hour start. Logo design from £129, websites from £299.

Ask Us a Question

Reply within one working day · No commitment