Free Preview
Buy Now
WordPress 500 error troubleshooting

Table of Contents

How to Fix the WordPress 500 Internal Server Error: Complete Guide

Few WordPress errors are as frustrating as seeing a blank page or a message saying:

“500 Internal Server Error”

The problem is especially frustrating because a 500 error doesn’t immediately tell you what went wrong. Your website may have been working perfectly a few minutes ago, and suddenly the homepage, WordPress dashboard, or a specific page stops loading.

The good news is that a WordPress 500 Internal Server Error is usually fixable.

The cause can range from a problematic plugin or theme to an exhausted PHP memory limit, corrupted .htaccess file, incompatible PHP version, server configuration issue, or a recent change that introduced a fatal PHP error.

In this guide, you’ll learn how to diagnose and fix a WordPress 500 error step by step, starting with the safest and easiest solutions before moving into more advanced troubleshooting.

What Is a WordPress 500 Error?

A 500 Internal Server Error is a server-side error indicating that the server encountered an unexpected condition while processing a request.

Unlike a 404 error, which generally means a requested resource could not be found, a 500 error means the server couldn’t successfully complete the request.

The error may appear as:

  • 500 Internal Server Error
  • HTTP 500 Internal Server Error
  • Internal Server Error
  • A completely blank page
  • A generic server error message

The exact appearance depends on your hosting provider, web server, WordPress configuration, and browser.

Importantly, the 500 status code itself doesn’t identify the underlying cause.

That’s why troubleshooting is about finding the specific server-side problem responsible for the error.

What Causes a WordPress 500 Internal Server Error?

Some of the most common causes include:

  • A broken or incompatible plugin
  • A theme conflict
  • A PHP fatal error
  • PHP memory exhaustion
  • An incompatible PHP version
  • A corrupted .htaccess file
  • Incorrect file permissions
  • Corrupted WordPress core files
  • Server configuration problems
  • Hosting resource limitations
  • A failed WordPress update
  • Custom PHP code or snippets causing an error

You don’t need to try every possible solution randomly.

The best approach is to diagnose the problem first, then apply the appropriate fix.

Before You Start: Don’t Panic

If your WordPress website suddenly shows a 500 error, don’t immediately start changing multiple settings.

Making several changes at once can make troubleshooting much harder because you won’t know which change fixed or caused the problem.

Instead:

Identify → Backup → Test → Fix → Verify

If possible, take a backup before making significant changes.

For more information about safely making WordPress changes, see our guide to WordPress staging environments and safe website updates.

1. Check Whether the Error Is Temporary

Before making technical changes, refresh the page.

Try:

  • Refreshing the browser
  • Opening the page in an incognito window
  • Trying another browser
  • Checking the website from another device
  • Opening another page on the website

Sometimes a temporary server problem can cause a 500 response.

If the error disappears immediately, monitor the website to determine whether it was an isolated server issue.

If it keeps happening, continue troubleshooting.

2. Check Whether the Entire Website Is Down

Determine how widespread the problem is.

Is only one page affected?

If the homepage works but one specific URL returns a 500 error, the problem may be related to:

  • That page
  • A plugin
  • Custom code
  • A specific template
  • A database query
  • A page builder

Is the entire website affected?

If every page returns a 500 error, investigate:

  • Plugins
  • Themes
  • .htaccess
  • PHP
  • WordPress core
  • Server configuration
  • Hosting resources

Is only /wp-admin/ affected?

If the frontend works but WordPress admin returns a 500 error, the issue may be related to an admin-specific plugin, PHP process, memory limit, or custom functionality.

Understanding the scope of the problem gives you an important clue.

3. Disable WordPress Plugins

A broken plugin is one of the most common causes of WordPress errors.

This can happen after:

  • Updating a plugin
  • Installing a new plugin
  • Updating WordPress
  • Changing PHP versions
  • Activating a plugin with conflicting functionality

If you can access:

WordPress Dashboard → Plugins

deactivate your plugins one at a time and test the website after each change.

When the website starts working again, you’ve likely identified the problematic plugin.

What if you can’t access WordPress?

If the 500 error prevents you from opening the dashboard, you can usually deactivate plugins through your hosting file manager or FTP.

Navigate to:

/wp-content/plugins/

You can temporarily rename the plugins folder:

plugins

to:

plugins-disabled

WordPress will no longer be able to load the plugins normally.

Then test the website.

If the website starts working, plugins are likely involved.

You can then restore the folder name and isolate the problematic plugin individually.

4. Check for Plugin Conflicts

Sometimes the problem isn’t one obviously broken plugin.

Two plugins may conflict with each other.

For example, conflicts can occur between:

  • Caching plugins
  • Security plugins
  • Optimization plugins
  • Page builders
  • WooCommerce extensions
  • SEO plugins
  • Custom functionality plugins

If you’re dealing with a plugin-related error, don’t immediately assume the plugin itself is defective.

It may be an interaction between two plugins.

For a detailed troubleshooting workflow, see How to Diagnose and Resolve WordPress Plugin and Theme Conflicts.

5. Switch to a Default WordPress Theme

Your active theme can also cause a 500 error.

This is particularly common after:

  • Theme updates
  • PHP updates
  • Adding custom PHP
  • Editing theme files
  • Installing a new plugin
  • Changing page builder settings

If you can access WordPress, temporarily activate a default WordPress theme such as a current Twenty Twenty-* theme.

Then test the website.

If the error disappears, your theme or theme-related functionality is likely involved.

If you cannot access the dashboard, you can change the active theme through the WordPress database or appropriate hosting tools, but this is more advanced and should be done carefully.

6. Increase the WordPress PHP Memory Limit

Another common cause is PHP memory exhaustion.

WordPress and its plugins require server memory to execute PHP processes.

Complex websites can require significantly more memory than a basic WordPress installation.

Memory-intensive functionality can include:

  • WooCommerce
  • Elementor
  • Large plugins
  • Image processing
  • Imports
  • Backups
  • Complex database operations

Depending on your hosting environment, you may see errors related to:

Allowed memory size exhausted

If that appears in your error logs, you’ve found an important clue.

You can increase WordPress’s memory limit if your hosting environment allows it.

For example, WordPress configuration may include:

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

However, don’t blindly increase memory to an enormous value.

The actual available PHP memory is controlled by your hosting/server configuration, so changing WordPress’s setting doesn’t necessarily increase the server’s real limit.

If you’re repeatedly hitting memory limits, investigate why the website is consuming so much memory.

7. Check Your PHP Version

An incompatible PHP version can cause serious problems in WordPress.

For example, a plugin or theme may contain code that isn’t compatible with the PHP version currently running on your server.

This can happen after a hosting provider changes PHP versions.

Check your hosting control panel for the active PHP version.

You should also make sure:

  • WordPress is up to date
  • Your theme is maintained
  • Your plugins are updated
  • Your plugins support your PHP version

If the 500 error appeared immediately after a PHP version change, that timing is a major clue.

In that situation, check the PHP error logs before changing multiple other settings.

8. Check the .htaccess File

A corrupted or incorrectly configured .htaccess file can cause server errors.

This is especially relevant on Apache-based hosting environments.

WordPress commonly uses .htaccess for rewrite rules and permalinks.

A typical WordPress .htaccess configuration looks similar to:

# 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

Don’t replace your .htaccess blindly.

First create a backup.

You can then test whether the file is causing the problem by temporarily renaming it, for example:

.htaccess

to:

.htaccess-backup

If the website begins working, regenerate the .htaccess file through:

Settings → Permalinks → Save Changes

This allows WordPress to generate its rewrite rules again.

9. Check WordPress Debug Logs

One of the most useful ways to diagnose a WordPress 500 error is to look at the error log.

WordPress has a built-in debugging system that can help identify PHP errors.

You can enable debugging in wp-config.php:

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

This configuration logs errors without displaying them publicly to visitors.

The log is commonly located at:

/wp-content/debug.log

Look for entries immediately before or around the time the 500 error occurred.

You may find messages mentioning:

  • A plugin
  • A theme
  • A PHP function
  • A specific file
  • Memory exhaustion
  • Deprecated functionality
  • Fatal errors

Important security note

Don’t leave verbose debugging information publicly displayed on a production website.

WP_DEBUG_DISPLAY should normally remain disabled on a live site.

10. Check Your Hosting Error Logs

WordPress’s debug log isn’t always enough.

Your hosting provider may have server-level logs containing additional information.

Depending on your hosting environment, you may find:

  • PHP error logs
  • Apache logs
  • Nginx logs
  • Application logs
  • Resource usage information

If the error appears to originate at the server level, your hosting provider may be able to identify the exact cause.

This is especially important if:

  • The entire server is affected
  • Multiple websites have problems
  • PHP processes are failing
  • Resources are exhausted
  • The server recently changed configuration

11. Check File and Folder Permissions

Incorrect permissions can prevent WordPress from accessing files or directories correctly.

Typical WordPress installations commonly use permissions along the lines of:

Files: 644

Directories: 755

Exact permissions can vary depending on your hosting environment.

Don’t recursively change every permission on your website without understanding the server setup.

Incorrect permission changes can create additional security and functionality problems.

If permissions were recently changed and the 500 error started afterward, investigate them with your hosting provider or server administrator.

12. Reinstall WordPress Core Files

If WordPress core files are corrupted or incomplete, reinstalling the WordPress core can sometimes resolve the problem.

This can happen after:

  • Failed updates
  • Interrupted updates
  • File corruption
  • Manual file changes
  • Incorrect deployments

If you can access the dashboard, WordPress provides options for reinstalling core files.

You can also use appropriate hosting or WP-CLI tools.

Don’t overwrite wp-content

Your:

  • Themes
  • Plugins
  • Uploads

are stored under wp-content.

Be careful when replacing WordPress files manually.

Always maintain a current backup before performing core file operations.

13. Check Your PHP Error Log for Fatal Errors

A PHP fatal error is often the actual reason behind a WordPress 500 response.

For example, you might see something similar to:

PHP Fatal error: Uncaught Error: Call to undefined function...

or:

PHP Fatal error: Allowed memory size exhausted...

These messages are much more useful than simply knowing that the browser returned HTTP 500.

Look for:

What file caused the error?

What plugin or theme owns that file?

What function failed?

Did the error begin after a recent update?

Once you identify the component responsible, you can focus your troubleshooting on that component instead of changing unrelated settings.

14. Undo the Most Recent Change

Think about what happened immediately before the website stopped working.

Did you:

  • Install a plugin?
  • Update a plugin?
  • Update WordPress?
  • Update your theme?
  • Change PHP versions?
  • Add custom code?
  • Change .htaccess?
  • Modify DNS?
  • Move hosting?
  • Install an optimization plugin?
  • Change caching settings?

The timing can provide a powerful clue.

If the website broke immediately after one specific change, temporarily reversing that change can be one of the fastest diagnostic tests.

Don’t permanently leave outdated software installed just because rolling back fixed the problem.

Once the site is stable, determine why the update or change caused the conflict.

15. Check Your Hosting Resources

Sometimes the WordPress installation itself isn’t the primary problem.

Your hosting account may be reaching resource limits.

Depending on your hosting plan, resources may include:

  • CPU
  • RAM
  • PHP workers
  • Processes
  • Disk space
  • Database resources
  • I/O

A resource-heavy WordPress website can experience intermittent 500 errors when it reaches hosting limits.

This can happen with:

  • High traffic
  • WooCommerce
  • Large imports
  • Backup processes
  • Image processing
  • Poorly optimized plugins
  • Bots and attacks
  • Cron jobs

If your hosting panel provides resource monitoring, check it around the time the errors occurred.

16. Clear Your Cache

Caching usually isn’t the root cause of a server-side 500 error, but cached responses can sometimes make troubleshooting confusing.

If you use a caching system, clear:

  • WordPress cache
  • Plugin cache
  • Server cache
  • CDN cache
  • Browser cache

If you’re using a CDN or reverse proxy, temporarily bypassing the cache can help determine whether the error originates from the origin server or the caching layer.

Don’t make large caching configuration changes while you’re still trying to identify the original problem.

17. Check Your CDN or Cloudflare Configuration

If your website uses a CDN or proxy service such as Cloudflare, the error may not originate directly from WordPress.

Depending on the exact error and configuration, you may need to determine whether:

Browser → CDN → Server → WordPress

is failing at the CDN layer or origin server.

Check:

  • SSL configuration
  • DNS
  • Proxy status
  • Origin server availability
  • Firewall rules
  • Recent CDN configuration changes

If WordPress works correctly when accessed directly at the origin but fails through the CDN, investigate the CDN configuration rather than changing WordPress files unnecessarily.

18. Check Your Database

Although a database problem more commonly produces a specific database connection error, database issues can also contribute to broader WordPress failures.

Look for:

  • Database connection errors
  • Corrupted tables
  • Failed queries
  • Excessive database size
  • Plugin-generated database problems

Don’t run database repair or optimization operations blindly on a live production website.

Create a backup first.

19. Check Custom Code and Code Snippets

Custom PHP code is another common source of WordPress 500 errors.

A single syntax error or incompatible function can break a page or the entire website.

This is particularly relevant if you recently added:

  • PHP snippets
  • Theme customizations
  • Functions in functions.php
  • Custom WooCommerce code
  • API integrations
  • Custom plugin functionality

If the error appeared immediately after adding custom code, temporarily disable that code and test again.

For safer management of custom WordPress functionality, see our guide on How to Add Custom Features in WordPress Using Code Snippets.

20. Check Recent WordPress Updates

WordPress updates are important for security and functionality, but compatibility issues can occasionally appear.

A WordPress core update can expose problems in:

  • Outdated plugins
  • Outdated themes
  • Custom PHP
  • Old APIs
  • Unsupported PHP versions

If a 500 error appeared directly after a WordPress update, check whether your plugins and theme are compatible with the new version.

Avoid keeping the entire website permanently outdated just to avoid compatibility problems.

A better long-term solution is to test updates safely.

For a safer update workflow, see How to Safely Update & Test WordPress Websites Using Staging Environments.

How to Fix a WordPress 500 Error Without Losing Your Website

One of the biggest mistakes you can make during troubleshooting is making changes without a backup.

Before:

  • Editing wp-config.php
  • Changing .htaccess
  • Modifying the database
  • Replacing WordPress files
  • Changing PHP versions
  • Disabling important functionality

create a backup whenever possible.

If the website is a production business site or WooCommerce store, consider testing significant changes on a staging environment first.

This is particularly important if the website handles:

  • Orders
  • Payments
  • Customer accounts
  • Forms
  • Memberships
  • Important business data

WordPress 500 Error Troubleshooting Checklist

Work through these steps in order:

Basic checks

  • Refresh the page
  • Test another browser
  • Test another device
  • Check whether the entire website is affected
  • Check whether /wp-admin/ works

Plugins and themes

  • Disable recently installed plugins
  • Test for plugin conflicts
  • Switch to a default theme
  • Check recent updates

PHP and server

  • Check PHP version
  • Check PHP memory limit
  • Check PHP error logs
  • Check hosting resource usage
  • Check server error logs

WordPress files

  • Check .htaccess
  • Check file permissions
  • Check WordPress core files
  • Check wp-config.php
  • Check custom code

Infrastructure

  • Clear caches
  • Check CDN configuration
  • Check SSL configuration
  • Check DNS if relevant
  • Check database health

After fixing

  • Test homepage
  • Test important pages
  • Test WordPress admin
  • Test forms
  • Test WooCommerce checkout if applicable
  • Check error logs again
  • Disable debugging display on production

How to Prevent WordPress 500 Errors

You can’t prevent every server error, but you can significantly reduce the risk.

Keep WordPress Updated

Use current versions of:

  • WordPress
  • Plugins
  • Themes
  • PHP

But test major changes where possible.

Use a Staging Environment

A staging website gives you a safer place to test:

  • Plugin updates
  • Theme updates
  • PHP changes
  • Custom code
  • Major configuration changes

Read our complete guide to WordPress staging environments for a safer workflow.

Maintain Reliable Backups

Your backup strategy should allow you to recover quickly if a change causes a critical problem.

Ideally, maintain backups that are:

  • Automated
  • Tested
  • Stored separately
  • Easy to restore

Monitor Your Website

Website monitoring can alert you when your website begins returning errors.

This is particularly useful for business websites and online stores where downtime can directly affect revenue.

Keep Your Plugin Stack Under Control

More plugins don’t automatically mean a bad website.

However, unnecessary, abandoned or overlapping plugins can increase complexity and compatibility risks.

Review your plugins regularly and remove software you no longer need.

When Should You Contact Your Hosting Provider?

Sometimes the problem is beyond WordPress itself.

Contact your hosting provider if:

  • Server logs show infrastructure errors
  • Your account is exceeding resource limits
  • PHP processes are failing
  • Multiple websites are affected
  • The server recently changed configuration
  • You cannot access important server logs
  • The problem continues after WordPress-level troubleshooting

Give your hosting provider as much useful information as possible.

Instead of saying:

“My website is broken.”

provide:

  • The exact URL
  • Approximate time the problem started
  • HTTP status code
  • Recent changes
  • PHP version
  • Error log messages
  • Whether the entire website is affected
  • Whether /wp-admin/ works

This makes it much easier for support to investigate.

Final Thoughts

A WordPress 500 Internal Server Error can look like a catastrophic problem, but in many cases the underlying cause is relatively straightforward.

The most common culprits are:

  • Plugins
  • Themes
  • PHP errors
  • Memory limits
  • .htaccess
  • Custom code
  • WordPress updates
  • Hosting resources
  • Server configuration

The key is to troubleshoot systematically.

Start with the most recent change and the error logs. Then work through plugins, themes, PHP, .htaccess, WordPress files and hosting resources.

Most importantly, don’t randomly change ten settings at once.

Identify the cause first, make one controlled change, and test the result.

Once your website is working again, take the opportunity to improve your maintenance process with regular backups, staging, updates and monitoring.

That way, the next WordPress error is much easier to diagnose—and much less stressful to fix.

Take Your WordPress Skills Further

Fixing individual WordPress errors is useful, but understanding why WordPress websites break and how to prevent those problems is even more valuable.

WP Flow Mastery is a practical resource for learning WordPress, SEO, performance, security and WooCommerce.

📖 160+ pages of practical WordPress knowledge

Learn how to:

  • Build WordPress websites
  • Optimize website performance
  • Improve WordPress SEO
  • Secure your website
  • Work with WooCommerce
  • Troubleshoot common problems
  • Maintain WordPress websites professionally

Ready to master WordPress?

Get the WP Flow Mastery eBook →

Written by Nemanja Stosic

WordPress Developer & Website Optimization Specialist

Nemanja helps businesses and freelancers build, optimize, and maintain professional WordPress websites focused on performance, SEO, security, and usability.