All articles Troubleshooting

WordPress 500 Internal Server Error: Causes and How to Fix It (2026)

What a 500 Internal Server Error means on a WordPress site, the most common causes and how to fix it step by step, from the error log to .htaccess, plugins and PHP.

WP Beekeeper Team · 7 min read
Server with a warning light, a wrench and a screwdriver next to a laptop with a blank page: fixing the WordPress 500 error

“500 Internal Server Error” is the least helpful message a website can show. It only says that something went wrong on the server, not what. For a WordPress site, the cause is almost always one of a few things: a broken .htaccess file, a plugin or theme error, too little memory, a PHP version change or wrong file permissions.

This guide shows how to find the actual cause in the error log and fix it step by step, starting with the quickest checks.

Key takeaways

  • A 500 error is a generic server error. The real cause is in the server or PHP error log, so look there first.
  • The most common causes on WordPress sites: a corrupted .htaccess file, a plugin or theme that triggers a fatal PHP error, an exhausted memory limit, an incompatible PHP version and wrong file permissions.
  • Renaming .htaccess and deactivating plugins via the file manager fixes a large share of 500 errors within minutes.
  • If the error appeared right after a change, undo that change first: the update, the PHP switch or the new snippet.
  • If none of this helps, ask your host: the server log shows errors you cannot see from WordPress.

What a 500 error means

The HTTP status code 500 means the server ran into a problem it could not handle and could not deliver the page. Unlike the WordPress message “There has been a critical error on this website”, which WordPress shows when it catches a PHP error itself, a 500 error often comes from the web server or PHP before WordPress can step in. That is why the browser shows a plain error page, sometimes completely blank.

A 500 error is different from 502 and 504 errors, which point to a problem between the web server and PHP or to a timeout, and from 503, which usually means the server is overloaded or in maintenance.

The most common causes

CauseTypical triggerHow to check
Corrupted .htaccessA plugin or manual edit wrote a wrong ruleRename .htaccess and reload
Plugin or theme errorUpdate, new plugin, incompatible codeError log, deactivate plugins
PHP memory limit exhaustedLarge imports, heavy plugins“Allowed memory size exhausted” in the log
PHP version changeHost switched PHP, old code not compatibleSwitch back to the previous version
Wrong file permissionsAfter a migration or manual uploadFolders 755, files 644
Server limits or timeoutsLong-running processes, overloaded serverServer log, ask the host
Damaged core filesInterrupted updateReinstall wp-admin and wp-includes

Step 1: The quick checks

  • Reload the page after a minute. A temporary server hiccup sometimes fixes itself.
  • Clear your browser cache and test in a private window, and clear the site cache if you use a caching plugin or CDN.
  • Check whether only one page or the whole site is affected, and whether the dashboard (/wp-admin) works.
  • Think about what changed last: an update, a new plugin, a PHP switch, an edit to .htaccess or functions.php.

Step 2: Read the error log

The error log usually names the exact cause. Most hosts show the PHP and server error log in the hosting panel, often as a file called error_log or in a logs section. If you do not find it, turn on WordPress debug logging in wp-config.php:

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

WordPress then writes PHP errors to wp-content/debug.log. Look for lines with PHP Fatal error. The path in the message shows which plugin or theme is involved. Set WP_DEBUG back to false when you are done. The official guide on debugging in WordPress explains all options.

Step 3: Rule out .htaccess

On Apache and LiteSpeed servers, a single wrong line in .htaccess can cause a 500 error for the whole site. In the WordPress root folder, rename .htaccess to .htaccess-old and reload the site. If it works now, the file was the problem. Create a new one by saving the permalinks under Settings → Permalinks, or create the file with the WordPress default rules:

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

Then add back your own rules from the old file, one block at a time, and test after each one. Nginx servers do not use .htaccess, so skip this step there.

Step 4: Deactivate plugins and test the theme

If the log points to a plugin, or you cannot tell, rename its folder in wp-content/plugins/, or rename the whole plugins folder to deactivate all plugins at once. If the site loads, rename the folder back and reactivate plugins one by one in the dashboard until the error returns. Do the same with the active theme folder in wp-content/themes/. Our guide on the WordPress critical error walks through these steps in detail.

Step 5: Memory and PHP version

If the log says “Allowed memory size of … bytes exhausted”, raise the WordPress memory limit in wp-config.php:

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

If the error appeared after a PHP version change, switch back to the previous version in your hosting panel and find the incompatible plugin or code. Old PHP versions do not receive security fixes, so plan the upgrade properly. Our guide on updating the PHP version in WordPress shows how.

Step 6: File permissions and core files

  • After a migration or a manual upload, wrong permissions can cause 500 errors. Usually folders should be 755 and files 644. Your host can reset them if you are unsure.
  • If an update was interrupted, core files may be incomplete. Upload fresh copies of wp-admin and wp-includes from wordpress.org, but never overwrite wp-content or wp-config.php.

Step 7: Ask your host

If none of this helps, contact your host’s support. They can see the web server log, PHP-FPM errors, resource limits and timeouts that are invisible from WordPress. Tell them the exact time the error occurs and the URL, and mention what you have already tried.

How to prevent 500 errors

  • Make a backup before every update and every change to .htaccess, wp-config.php or functions.php.
  • Update in the right order and check your pages afterwards.
  • Test PHP upgrades and big updates on a staging copy first.
  • Keep plugins to what you need, and remove abandoned ones.
  • Monitor your site, so you hear about an error from an alert, not from a customer.

If you want to restore quickly when something breaks, our WordPress backup guide explains what a usable backup needs.

Catch errors before your customers do.WP Beekeeper checks your site every five minutes, makes a full backup before every update and compares your pages before and after. If something breaks, you know right away. Try it free for 14 days.

Start free trial →

Sources and further reading

Frequently asked questions

What causes a 500 Internal Server Error in WordPress?

Most often a corrupted .htaccess file, a plugin or theme that triggers a fatal PHP error, an exhausted memory limit, an incompatible PHP version or wrong file permissions. The error log shows the exact cause.

How do I fix a 500 error in WordPress?

Read the error log, rename .htaccess and let WordPress create a new one, deactivate plugins and test the theme via the file manager, raise the memory limit or switch back the PHP version. If nothing helps, ask your host for the server log.

Can a plugin cause a 500 error?

Yes. A plugin that triggers a fatal PHP error, for example after an update or with a newer PHP version, is one of the most common causes. Rename its folder in wp-content/plugins to deactivate it.

Why does only wp-admin show a 500 error?

Often a plugin that only loads in the dashboard, or a memory limit that the admin area exceeds. Check the error log and deactivate plugins via the file manager.

What is the difference between a 500 error and the WordPress critical error?

The critical error message comes from WordPress itself after it caught a PHP error. A 500 error comes from the server or PHP, often before WordPress can show its own message. The causes and fixes overlap.

Will a 500 error hurt my SEO?

A short outage does not. If the error lasts for days, Google may crawl less and eventually drop affected pages. Fix it quickly and monitor your site.

Conclusion

A 500 error looks mysterious, but the cause is usually quick to find: read the error log, rule out .htaccess, deactivate plugins and the theme, check memory and the PHP version, then permissions and core files. If all that fails, your host can see more. And with a backup before every change, the worst case is a quick restore.