Table of contents

What is it?Common causesPrerequisite1. Corrupted file2. Plugin conflicts3. Theme conflicts4. PHP memory limits5. Corrupted core files6. Incorrect file permissionsCan’t find the problem?FAQsNext stepsAdditional resources

Get the industry’s fastest hosting for WordPress◦ 99.999% uptime
◦ Comprehensive security
◦ 24/7 support

WordPress Guide → Errors → 500 Internal Server Error

WordPress 500 internal server error (and how to fix it)

Few things are more frustrating than visiting your WordPress site and being greeted by a blank page or “500 Internal Server Error” message. It looks serious—and it is—but it doesn’t mean your site is gone. The error is usually fixable with a few troubleshooting steps.

Get fast, reliable hosting for WordPress

Power your site with the industry’s fastest, most optimized WordPress hosting

WordPress.org hosting

What is the WordPress 500 internal server error?

A WordPress 500 internal server error is a general server-side problem that prevents your site from loading. Instead of showing your content, the server displays a generic error message: “500 Internal Server Error.”

Unlike specific error codes that point to clear issues (like a “404 Not Found”), the 500 error is vague. It simply tells you something went wrong inside the server but not exactly what. This makes it a bit intimidating, but it also means the problem could be one of several common and well-understood causes.

In WordPress, a 500 error often comes from corrupted files, plugin or theme conflicts, server configuration issues, or running out of memory. Fixing it involves identifying the root cause and making small adjustments to get your site back online.

Common 500 error causes and solutions

There isn’t one single reason this error appears. The good news is that there are several common culprits, and each one has a reliable fix. By following the steps below, you can narrow down the cause and get your website working again.

Prerequisite: Clear WordPress and browser caches

Before you start digging into deeper fixes, it’s smart to clear your cache. A “cache” is a stored copy of your site that helps it load faster. Sometimes, you may still be seeing the error even after it has been fixed because of cached data.

To clear your browser cache, go into your browser settings (in Chrome, click the three dots → More Tools → Clear browsing data). Select cached images and files, then click “Clear data.”

To clear your WordPress cache, log in to your dashboard if possible. If you’re using a caching plugin like W3 Total Cache or WP Super Cache, look for the “Clear Cache” or “Purge All Caches” button. If you can’t access your dashboard, you can temporarily disable your caching plugin by renaming its folder via FTP.

1. Corrupted .htaccess file

The .htaccess file controls server rules for your WordPress site. If it becomes corrupted, it can block your site from loading. Corruption often happens after plugin installations, theme changes, or manual edits.

To fix it:

Connect to your site using FTP or your hosting file manager.
Locate the .htaccess file in the root folder (the same place as wp-content and wp-config.php).
Rename it to .htaccess_old to disable it.
Try reloading your site. If it works, go to your WordPress dashboard → Settings → Permalinks and click “Save Changes” to generate a new .htaccess file.

2. Plugin conflicts

Plugins extend WordPress, but sometimes one plugin can break the site or clash with another. A poorly coded or outdated plugin is a common reason for a 500 error.

To fix it:

Access your site files via FTP or your hosting file manager.
Open the wp-content folder and find the plugins folder.
Rename the entire folder to “plugins_old.” This will deactivate all plugins.
Refresh your site. If it loads, rename the folder back to “plugins” and activate plugins one by one from the dashboard to find the culprit.

3. Theme conflicts

Themes control your site’s design, but if your active theme has a bug or conflict, it can also cause server errors.

To fix it:

Log in to your site files.
Navigate to wp-content → themes.
Rename your active theme’s folder (for example, change “twentytwentythree” to “twentytwentythree_old”).
WordPress will automatically fall back to a default theme like Twenty Twenty-One.
If your site works, the theme was the problem, and you’ll need to reinstall or replace it.

4. PHP memory limits

Every WordPress site runs on PHP, and your server sets a memory limit for how much it can use. If your site exceeds this limit, it can trigger a 500 error. This often happens on larger sites or sites with many plugins.

To fix it:

Access your wp-config.php file (located in the root WordPress directory).
Add the following line above the line that says /* That’s all, stop editing! */
define(‘WP_MEMORY_LIMIT’, ‘256M’);
Save and re-upload the file.
Reload your site to see if the error clears.

5. Corrupted WordPress core files

Core files are the backbone of WordPress. If they get corrupted during updates or file transfers, the site can break.

To fix it:

Download the latest version of WordPress from wordpress.org.
Extract the ZIP file on your computer.
Upload the wp-admin and wp-includes folders to your site via FTP, replacing the old ones.
Do not touch wp-content or wp-config.php to avoid overwriting your content and settings.

6. Incorrect file permissions

Every file on your server has permissions that tell it who can read, write, or execute it. If these are set incorrectly, WordPress may fail to load and throw a 500 error.

To fix it:

Access your site via FTP.
Right-click on the WordPress root folder and select “File Permissions.”
Set folders to 755 and files to 644.
Apply changes to all subfolders and files.

Can’t find the problem?

If you’ve tried the above fixes and your site still isn’t working, there are two more steps you can take.

Enable debug logs

Debugging allows WordPress to show error messages instead of a generic white screen. This can point you directly to the file or plugin causing the issue.

To enable debugging:

Open your wp-config.php file.
Find the line that says:

define(‘WP_DEBUG’, false);
Change it to:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false)
Reload your site. Error details will be saved in a debug.log file inside wp-content.

Contact your hosting provider

If you’re still stuck, reach out to your hosting provider. Hosting companies have access to server error logs and tools you can’t reach yourself. They can often identify whether the issue is server-related and may even fix it for you.

WordPress 500 error FAQs

The most common causes are corrupted files, plugin or theme conflicts, or exceeding PHP memory limits.

It’s the same type of error but happening on your staging site, usually caused by a plugin, theme, or incorrect staging setup.

This is often called the “white screen of death” and means the server can’t process something. Debugging logs usually reveal the problem.

Yes, by keeping WordPress, plugins, and themes updated, avoiding poorly coded plugins, and ensuring your hosting plan has enough resources.

Upgrade your WordPress.org hosting

Internal server errors happen, but it helps to either have the technical experience needed to troubleshoot it or to have the right team on your side.

If you find yourself struggling with the technical side of your website more than you’d like, it might be time to upgrade your WordPress.org hosting. A good web host will help keep your site fast and secure—and offer 24/7 expert support. If you need even more help, a managed WordPress hosting arrangement might be a good solution.

Liquid Web has been pushing the industry forward in web hosting for WordPress sites, for decades. Our server speeds are lightning fast, our uptime is unbeatable, and our support team is unrivaled. Click below to learn more, or start a chat right now to get answers and guidance just for you.