WordPress Crashed After Plugin Install Fix

Disable All Plugins via FTP/File Manager

This is the most common and effective first step. If a plugin caused the crash, deactivating it will often bring your site back. Since you can't access your admin dashboard, you'll need to do this manually.

• Access your server: Use an FTP client (like FileZilla) or your hosting provider's cPanel File Manager.
• Navigate to plugins: Go to the wp-content directory, then find the plugins folder.
• Rename the folder: Rename the plugins folder to something like plugins_disabled. This effectively deactivates all plugins.
• Check your site: Try accessing your WordPress admin area (yourdomain.com/wp-admin) and your front-end. If your site comes back, you've confirmed a plugin conflict.

mv wp-content/plugins wp-content/plugins_disabled

✓ 5-10 minutes. This is generally safe and non-destructive.

Enable WordPress Debugging to Identify the Error

If renaming the plugins folder didn't fix it, or if you want to pinpoint the exact issue, enable WordPress debugging. This will log errors instead of displaying a generic 'critical error' message or a white screen.

• Access wp-config.php: Connect via FTP/File Manager and open the wp-config.php file in your WordPress root directory.
• Add debug constants: Just before the line /* That's all, stop editing! Happy publishing. */, add the following lines.
• Check debug.log: After adding these, try to load your site again. A file named debug.log will be created in the wp-content directory. Open it to find specific error messages, often pointing to a file path and line number within the problematic plugin or core.

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

✓ 5 minutes. Remember to set WP_DEBUG to false once fixed for security.

Manually Isolate and Revert the Problematic Plugin

If you know which plugin caused the issue (e.g., your site went down immediately after installing a security plugin like Wordfence, activating WooCommerce, or updating Elementor/Divi), you can try to isolate it.

• Revert Step 1: If you renamed plugins to plugins_disabled, rename it back to plugins.
• Identify the culprit: Go into the wp-content/plugins folder. If you suspect a specific plugin like wordfence, woocommerce, elementor, divi, wpml, or a membership plugin, rename only that plugin's folder (e.g., wordfence to wordfence_temp).
• Test: Check your site. If it comes back, you've found the problematic plugin. You can then delete the renamed folder and try reinstalling a fresh copy or an older version if available and compatible.

✓ 5-15 minutes. This helps narrow down the cause if multiple plugins were active.

Check PHP Version Compatibility

Many plugin crashes, especially after updates, are due to PHP version incompatibilities. A plugin might require a newer PHP version than your server is running, or it might be incompatible with a very new PHP version.

• Access your hosting control panel: Look for a 'PHP Selector,' 'MultiPHP Manager,' or similar tool (often in cPanel).
• Check and adjust PHP version: See what PHP version your site is currently using. Try switching to a slightly older stable version (e.g., if on 8.2, try 8.1 or 8.0) or a newer one if you're on a very old version (e.g., 7.4).
• Test your site: After changing the PHP version, clear any server-side cache and check your site.

For more in-depth PHP version troubleshooting, refer to our guide: WordPress Crashed After PHP Version or Server Update.

✓ 10-15 minutes. Incorrect PHP versions are a frequent cause of fatal errors.

Inspect .htaccess for Malicious or Corrupted Rules

Some plugins, especially security plugins or caching plugins, can modify your .htaccess file. If these modifications are malformed or conflict with server settings, they can bring your site down.

• Access .htaccess: Via FTP/File Manager, locate the .htaccess file in your WordPress root directory. (It's a hidden file, so ensure 'Show Hidden Files' is enabled).
• Backup and replace: Download a copy of your current .htaccess. Then, delete its contents and replace them with the default WordPress .htaccess rules.
• Test your site: If your site comes back, the issue was in the .htaccess file. You can then try to identify the specific problematic rules by re-adding sections one by one, or by reinstalling the plugin and letting it generate new rules.

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

✓ 5-10 minutes. Always back up .htaccess before editing.

Clear All Caching (Server, Plugin, CDN)

Even after resolving the underlying issue, your site might still appear broken due to aggressive caching. This is especially true if you're seeing outdated content or persistent errors after making changes.

• Server-side caching: Check your hosting control panel for options to clear server cache (e.g., LiteSpeed Cache, Varnish).
• Plugin caching: If you managed to get into your admin, clear any caching plugin's cache (e.g., WP Super Cache, WP Rocket).
• CDN caching: If you use a CDN like Cloudflare, log into its dashboard and purge the cache for your domain.
• Browser cache: Clear your browser's cache and cookies, or try accessing your site in an incognito/private window.

✓ 5 minutes. Essential for seeing the results of your fixes immediately.