Available for new work Remote - worldwide hello@wordpressfixe.com
wordpressfixe

Troubleshooting

WordPress 500 internal server error: plugin or server?

A 500 is not a WordPress error. It is the server saying the request could not be completed — which is why the first question is always “where did it die?”

“500 Internal Server Error” is the most generic message a web server can send. It means the request failed on the server side and no more specific response was available. WordPress never gets to apologise, because WordPress may not have run at all.

That distinction — did WordPress run? — is the whole diagnosis. It splits the problem into two very different investigations.

Test 1: does a static file load?

Create a file called test.html in your web root containing the word “hello”. Visit https://yourdomain.com/test.html.

  • It loads. The web server is fine. The failure is in PHP or WordPress. Go to test 2.
  • It also returns 500. The problem is at the server or account level: a broken .htaccess, a disk quota, a PHP handler misconfiguration, or the account itself being suspended.

Test 2: is PHP running?

Create test.php containing <?php echo 'php ok'; and load it.

  • “php ok” appears. PHP works. The fault is in WordPress, a plugin, a theme, or wp-config.php.
  • 500 again. PHP itself is failing — wrong PHP version for the handler, a missing extension, or a syntax error in a config file the server parses.

Both files should be deleted afterwards. They are diagnostic tools, not content.

If it is the server

The most common causes, in order:

  1. A malformed .htaccess. One bad line breaks every request. Rename it to .htaccess.bak and reload. If the site returns, the file was the cause. Regenerate it from WordPress → Settings → Permalinks.
  2. File permissions. Folders should be 755 and files 644. A 777 file or a 600 folder can produce a 500 on hardened hosts.
  3. Disk quota or inode limit. Full disks fail silently and confusingly. Check the hosting panel.
  4. PHP version. A host upgrade to 8.3 can break older code. Check the version in the panel and the error log.
  5. ModSecurity or a WAF rule. A false positive on a request can return 500 instead of 403. Disable the rule for your IP to confirm, not for everyone.

If it is WordPress

Now the error log matters. Look for a PHP Fatal error with a file path. If there is no log, enable it:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Then reload the failing page and read wp-content/debug.log. If the log is empty and the page still 500s, the failure is before WordPress loads — check wp-config.php for a stray character, a wrong database host, or a corrupted file from an upload.

The bisect method

With SFTP access:

  1. Rename wp-content/plugins to plugins.off and create an empty plugins folder.
  2. Reload. If the site returns, it is a plugin.
  3. Move plugin folders back in halves, reloading after each move.
  4. Once you have one plugin, check its PHP compatibility and the line in the error log.

If plugins are not the cause, rename the theme folder. WordPress falls back to a default theme if one exists in wp-content/themes; if not, download a fresh default theme over SFTP.

What not to do

  • Do not reinstall WordPress first. Core corruption is rare, and a reinstall deletes evidence.
  • Do not set permissions to 777. It rarely fixes the 500 and it opens a security hole.
  • Do not disable ModSecurity globally to test. Whitelist your IP.
  • Do not restore a backup immediately. If the fault is a plugin update from three weeks ago, you restore the same fault with older data.

How long should this take?

With access to the error log, ten to twenty minutes. Without it, the bisect takes longer but still finishes inside an hour for a typical site. If a 500 has survived several hours of plugin deactivation, the fault is usually at the server layer and needs the host involved.

If you need it handled now, emergency WordPress repair starts with exactly this split: server or application, then the specific file.

Written by

Sahed Rana Neka

PHP and WordPress work focused on repair: emergency fixes, malware cleanup, performance and migrations. Portfolio on sahed.dev.

Need this fixed rather than explained?

MoreKeep reading

Other notes from the same work.