500 Error Caused by a Plugin in WordPress: Fix

What this problem is

Your site returns 500 Internal Server Error after installing, updating, or configuring a plugin.

Why it happens

• Fatal PHP error in the plugin code
• Plugin conflicts with PHP version or missing PHP extensions
• Resource exhaustion (memory/time) triggered by the plugin

Prerequisites

• FTP/File Manager access
• Access to server/PHP error logs (recommended)

Diagnosis

1. Confirm it is a 500 response.
2. Check error logs for the failing plugin file path under wp-content/plugins.

Detailed steps

Step 1) Disable the suspected plugin

Rename the plugin folder, for example:

wp-content/plugins/plugin-name → plugin-name.disabled

Expected result: the site stops returning 500.

Step 2) If unsure, disable all plugins

Rename:

wp-content/plugins → plugins.disabled

Step 3) Find the root cause in logs

Look for the first fatal error. Fix by updating the plugin, switching PHP version, or installing the required PHP extension.

Step 4) Re-enable plugins one by one

Restore plugins, then activate plugins individually to identify the offender.

Expected results

• 500 error removed
• Problem plugin identified and corrected or replaced

What to do if it fails

• If 500 persists with plugins disabled, the theme or core may be the cause
• Ask hosting support for the exact PHP error log entry

Best practices

• Update plugins on staging first
• Avoid abandoned plugins
• Keep backups for fast rollback