How to Set Up a WordPress Staging Site and Push Changes Live Safely
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
A WordPress 500 internal server error after a plugin update is a generic server message. Read the server and PHP logs, find the fatal error, roll back the plugin safely and check memory and hosting limits.
WordPress 500 internal server error after plugin update is a frustrating message because it says almost nothing. A 500 is a generic server response: something failed on the server, and the page could not be produced. After a plugin update, the most common reasons are a PHP fatal error in the new plugin code, a memory or resource limit, or a changed server rule. The logs name the actual cause, so this guide reads them first rather than guessing.
Do not keep clicking update or reinstall. First find the error in your host’s error log or the PHP error log, and look for a plugin file name. If you can log in to the admin area, deactivate the plugin you updated. If you cannot, rename that plugin’s folder inside wp-content/plugins using your host’s file manager, or use WP-CLI. Reload the site, and if it works, the plugin update is the cause. Then roll back to the previous version, check memory and PHP version requirements, and update again on staging.
How this guide was prepared: the steps follow the WordPress documentation listed under Sources, read on October 19, 2026. We did not reproduce your exact error, so the steps are research-based. Server logs, file managers and rollback tools differ between hosts, and a 500 can also come from the server itself.

| What you see | Likely cause | Start with |
|---|---|---|
| 500 on every page after updating one plugin | PHP fatal error in that plugin | Steps 1 to 3 |
| 500 only on the admin or one feature | A specific plugin function or heavy task | Steps 2 and 5 |
| Log says “Allowed memory size exhausted” | PHP memory limit too low | Step 5 |
| Log mentions .htaccess or rewrite rules | A corrupted or changed rule | Step 6 |
| Critical error message instead of a 500 | WordPress caught a fatal error | See WordPress critical error |
| Nothing in any log | Server-level problem | Step 7 |
The cause is written down somewhere. Look at your host’s control panel for the error log or PHP error log, and the WordPress debug log if it is enabled (wp-content/debug.log). WordPress documents turning on WP_DEBUG and WP_DEBUG_LOG with WP_DEBUG_DISPLAY set to false, so errors go to the log instead of the page, but it says debug tools belong on staging and local installs, not live sites. If you must use it, turn it off afterwards and delete the log. Look for lines with “Fatal error” near the time of the update.
A line such as “Fatal error … in /wp-content/plugins/plugin-name/file.php” names the plugin. Typical reasons are a new version that needs a newer PHP version, a missing or old dependency, or a conflict with another plugin or theme. Note the message, then open the plugin’s changelog and support page for known issues with that version.
If you can log in, deactivate the plugin on the Plugins screen. If not, the WordPress troubleshooting FAQ describes renaming the folder via FTP or a file manager. To disable one plugin, rename its folder inside wp-content/plugins (for example add -off), and reload the site. To disable all plugins, rename the plugins folder and rename it back after logging in; all plugins stay deactivated until you reactivate them. WP-CLI offers wp plugin deactivate. If the site returns, you have found the cause.
Restore the plugin version that worked. Options: restore from your backup or your host’s snapshot, or download the earlier version from the plugin’s page in the WordPress.org directory (its Advanced view lists previous versions for plugins hosted there) and replace the plugin folder. Use the rollback on staging first if you can. Then check the plugin’s changelog, the required PHP version and whether other plugins need updating together. Do not skip security updates for long: report the problem to the plugin author, and update again once it is fixed.
The WordPress handbook says the WP_MEMORY_LIMIT setting specifies the maximum memory PHP can use, and may help if you see a message like “Allowed memory size of … bytes exhausted”. On shared hosting you may have to ask your host to raise the limit. A plugin that does heavy work during an update, such as database changes, can also hit time or memory limits. Raise the limit only to a sensible value and only after you saw the memory message in the log.
The WordPress handbook says the most likely cause of an Internal Server Error is a corrupted .htaccess file. Plugins that add rewrite rules, caching or security rules can change that file. Make a copy, then rename the file to .htaccess_old and reload. If the site works, go to Settings → Permalinks and save to regenerate a clean file, then restore any custom rules you need, one at a time. This applies to Apache or LiteSpeed servers; other servers use different files.
If logs are empty or unclear, send your host the time of the 500, the URL, the plugin name and versions, and your PHP version. Ask for the server error log for that time, and ask whether a firewall, resource limit or PHP version change might apply. Also ask whether they can restore a snapshot from before the update. That is quicker than trial and error.
.htaccess, and others use different configuration.Usually not. It is a generic failure, and after a plugin update it is most often that plugin.
Often yes: your host’s file manager, WP-CLI or a one-click restore can do the same job.
Not at first. Deactivate and roll back, and keep the data until you know what the plugin stores.
PHP version, other plugins, the theme and server limits differ between sites.
Related guide: ERR_TOO_MANY_REDIRECTS in WordPress: Find the Redirect Loop
Related guide: “Error Establishing a Database Connection” in WordPress: Causes and Fixes
Read the log, name the plugin, roll back and test. If the WordPress 500 internal server error after a plugin update persists, send your host the log lines, times and versions with secrets removed. If you would like a person to look, wpallsolution offers emergency WordPress fixes and independent plugin support. We cannot promise a fix without seeing your setup.
Last reviewed: October 19, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
Care plans give agencies steady work after launch. See how white label WordPress maintenance works, what to include and what to agree…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout