How to fix a 500 Internal Server Error after a plugin update
Summary
This guide helps you troubleshoot and resolve: How to fix a 500 Internal Server Error after a plugin update. Follow the steps below to fix the issue.
Common Causes
Introduction
A 500 Internal Server Error after updating a plugin or theme usually means your content management system (CMS) has encountered a conflict it cannot resolve. This is common when a new plugin version is incompatible with your current theme, another active plugin, or your server's PHP version. Because the error occurs on the server side, your website may become completely inaccessible, including the administrative dashboard. The following steps will help you identify the problematic extension, restore access to your site, and safely roll back updates without losing content.
Step-by-Step Instructions
Step 1: Connect to your hosting account
You will need FTP credentials or access to your hosting control panel. Most Australian hosting providers offer a File Manager within cPanel, Plesk, or a proprietary dashboard. If you are using FTP, connect using an application such as FileZilla or Cyberduck.
Step 2: Check hosting error logs
Before making changes, identify the specific cause of the 500 error by reviewing your server logs:
- Log in to your hosting control panel (cPanel or Plesk).
- In cPanel, navigate to Metrics > Errors or click Raw Access Logs.
- In Plesk, go to Websites & Domains > Log Files and select the error log for your domain.
- Look for entries occurring at the time the error appeared. These logs often specify the exact file and line number causing the failure, which can confirm if a specific plugin is the culprit.
Step 3: Locate the plugin or theme directory
For WordPress sites, navigate to the following path via File Manager or FTP:
/wp-content/plugins/
If you updated a theme instead, navigate to:
/wp-content/themes/
Step 4: Rename the affected folder
Locate the folder for the plugin or theme you updated immediately before the error appeared. Right-click the folder and select Rename. Add a suffix such as -disabled to the end of the folder name. For example:
contact-form-7-disabled
Renaming the folder deactivates the extension without deleting your settings or content.
Step 5: Test your website
Open your website in a browser. If the homepage and administrative dashboard load correctly, you have identified the conflicting plugin or theme.
Step 6: Log into your CMS dashboard
Navigate to your site's login page, typically found at /wp-admin, and sign in using your administrator credentials.
Step 7: Check for available updates
Once logged in, go to Plugins > Installed Plugins or Appearance > Themes. Look for a newer version of the affected extension that may resolve the compatibility issue. If an update is available, apply it and then rename the folder back to its original name.
Step 8: Roll back to a previous version
If no fixing update is available, you may need to reinstall a previous version of the plugin or theme.
To obtain an older version from the WordPress.org plugin repository:
- Visit wordpress.org/plugins and search for the plugin name.
- Open the plugin page and click Advanced in the right-hand sidebar.
- Select Previous Versions from the dropdown menu.
- Choose the version you wish to reinstall and click Download.
If the plugin is a premium product, visit the developer's website and log into your account to access the version history and download archive. Upload the older version via your CMS dashboard under Plugins > Add New > Upload Plugin, or via FTP, and activate it. Monitor your site for stability before making further changes.
Step 9: Increase PHP memory limit
If the error persists and your error logs indicate a memory exhaustion issue, increase the PHP memory limit:
- Log in to your hosting control panel (cPanel or Plesk).
- In cPanel, select Software > Select PHP Version > Options.
- Locate
memory_limitin the list of directives. - Change the value from
128Mto256Mor512M. - Click Save and refresh your website.
Step 10: Enable debugging if renaming the folder does not work
If renaming the plugin or theme folder does not resolve the 500 error, the issue may be related to server configuration or a core file. Enable debugging to identify the specific error:
- Connect to your site via FTP or File Manager.
- Locate and open the
wp-config.phpfile in the root directory. - Find the line
define( 'WP_DEBUG', false );. - Change it to:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
- Save the file and refresh your website to trigger the error.
- Navigate to
/wp-content/debug.logvia FTP or File Manager to read the specific error message. - Once you have identified the issue, change
WP_DEBUGback tofalseto prevent sensitive information from being displayed on your live site.
Still Having Issues?
💻 Open a Ticket