+8801928835756
Back to Blog
WordPress Development 6 min read 23 views

How to Fix 500 Internal Server Error in WordPress

IM

Ibrahim Monir

Full-Stack Developer

Jul 9, 2026
How to Fix 500 Internal Server Error in WordPress

Seeing a 500 Internal Server Error on your WordPress site? Here is how to fix it — corrupted .htaccess, PHP memory limits, plugin and theme conflicts, file permissions, and enabling debugging to find the real cause.

Few errors are as alarming as loading your site and seeing a blank page that says "500 Internal Server Error." It gives no details, and suddenly your whole WordPress site — or admin area — is inaccessible. The good news: a 500 error is a generic server message with a short list of common causes, and each has a clear fix. This guide shows you how to fix the 500 Internal Server Error in WordPress, step by step, starting with the most likely causes.

What is a 500 Internal Server Error?

A 500 Internal Server Error is a generic HTTP status code that means something went wrong on the server, but the server can't be specific about what. In WordPress, it's almost always caused by a corrupted .htaccess file, an exhausted PHP memory limit, or a plugin or theme conflict. Because the message itself is vague, the fix is a process of elimination.

Key takeaways

  • Back up your site first — before changing any files.
  • A corrupted .htaccess file and low PHP memory are the two most common causes.
  • Plugin and theme conflicts cause most of the rest — deactivate to isolate them.
  • Enable WP_DEBUG to turn the vague 500 into a specific, fixable error.
  • Work through the fixes in order rather than guessing.

Before you start: back up and enable debugging

Always take a full backup before editing core files. Then turn on WordPress debugging so the vague 500 error reveals its real cause. Add this to wp-config.php:

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

Errors are then logged to wp-content/debug.log, which often names the exact plugin, theme, or file causing the problem.

1. Fix a corrupted .htaccess file

A broken .htaccess file is the most common cause of a 500 error. To fix it, connect via FTP or your host's file manager, rename .htaccess to .htaccess_old, and reload your site. If it works, the file was the problem. Then go to Settings → Permalinks and click Save to generate a fresh one, or paste in the default WordPress rules:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

2. Increase the PHP memory limit

Running out of PHP memory frequently triggers a 500 error. Raise the limit by adding this to wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );

If that doesn't hold, edit php.ini (or ask your host) to set memory_limit = 256M. A memory-related 500 often appears right after installing a heavy plugin or theme.

3. Deactivate all plugins

A faulty or incompatible plugin is a leading cause. If you can access the dashboard, deactivate all plugins at once, then reactivate them one by one, reloading the site after each until the error returns — that's your culprit. If you're locked out, use FTP to rename the wp-content/plugins folder to plugins_old, which deactivates them all, then restore and test individually.

4. Switch to a default theme

If plugins aren't the cause, your theme might be. Activate a default theme like Twenty Twenty-Four. If you can't reach the dashboard, rename your active theme's folder in wp-content/themes via FTP — WordPress will fall back to a default theme automatically. If the error clears, the theme is the problem.

5. Re-upload core WordPress files

Corrupted core files can cause a 500 error. Download a fresh copy of WordPress from wordpress.org, then via FTP re-upload the wp-admin and wp-includes folders, overwriting the existing ones. This replaces any damaged core files without touching your content in wp-content or your database.

6. Check file and folder permissions

Incorrect permissions can trigger a 500 error. The standard, secure values are:

  • Folders: 755
  • Files: 644
  • wp-config.php: 600 or 640

Avoid ever setting anything to 777 — it's insecure and some servers reject it, causing the very error you're trying to fix.

7. Check your PHP version and server logs

An outdated or incompatible PHP version can cause 500 errors, especially after a plugin or theme update. Make sure you're on a supported version (PHP 8.0+). Finally, check your server error logs (via your hosting panel) — for a persistent 500 error, the log usually contains the specific PHP fatal error you need to fix.

Frequently asked questions

What causes a 500 Internal Server Error in WordPress?

The most common causes are a corrupted .htaccess file, an exhausted PHP memory limit, and plugin or theme conflicts. Less often, it's caused by corrupted core files, incorrect file permissions, or an incompatible PHP version. Because 500 is a generic error, you find the cause by testing each in turn.

How do I fix a 500 error if I can't access wp-admin?

Use FTP or your host's file manager. Rename the .htaccess file to force a fresh one, rename the wp-content/plugins folder to deactivate all plugins, or rename your theme folder to fall back to a default theme. These let you isolate the cause without needing the dashboard.

How do I see the real error behind a 500 error?

Enable debugging by adding WP_DEBUG and WP_DEBUG_LOG to your wp-config.php, then check wp-content/debug.log. You can also review your server's error logs in your hosting control panel. Both usually reveal the specific plugin, theme, or PHP error causing the generic 500 message.

Can a plugin cause a 500 Internal Server Error?

Yes — a faulty, outdated, or incompatible plugin is one of the most common causes. Deactivate all plugins (via the dashboard or by renaming the plugins folder over FTP), then reactivate them one at a time to find which one triggers the error.

Final thoughts

A 500 Internal Server Error looks scary, but it's rarely serious once you know where to look. Back up first, enable debugging to uncover the real message, then work through the fixes in order: reset .htaccess, raise PHP memory, rule out plugins and themes, and check core files, permissions, and PHP version. One of these resolves the vast majority of 500 errors — and with debugging on, you'll usually know exactly which one before you even start.

More from WordPress Development

Related Posts