Home › Knowledgebase › KB-1127

WordPress Site Crash After Plugin Update: How to Restore Access via FTP

Summary

This guide helps you troubleshoot and resolve: WordPress Site Crash After Plugin Update: How to Restore Access via FTP. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Important: Before making any changes to your site files, create a full backup of your WordPress files and database. Renaming folders or editing configuration files can cause further issues if something goes wrong. A backup ensures you can restore your site to its previous state if needed.

When a WordPress plugin or theme update causes a site crash, you may be locked out of your dashboard and see a white screen or a critical error message. Because you cannot access the WordPress admin panel to reverse the change, you must use File Transfer Protocol (FTP) to manually deactivate the problematic plugin or theme. This guide walks you through restoring access to your site using an FTP client, with specific context for Australian small business hosting environments such as cPanel.

Quick Fix Steps

  1. Connect to your server via FTP using your hosting credentials.
  2. Navigate to the /wp-content/plugins/ directory.
  3. Rename the folder of the plugin you suspect caused the crash.
  4. Refresh your website to check if access is restored.
  5. Log into your WordPress dashboard and remove or update the faulty plugin.

Detailed Instructions

1. Gather your FTP credentials

Before you begin, ensure you have the following details from your hosting account. Most Australian hosting providers include these details in cPanel under FTP Accounts:

If you do not have your FTP credentials, you can retrieve them via your hosting control panel, such as cPanel, or open a support ticket with your provider.

2. Connect to your server via FTP

  1. Download and install an FTP client such as FileZilla or WinSCP.
  2. Open the FTP client and enter your hostname, username, password, and port.
  3. Use SFTP (port 22) if available for a secure connection.
  4. Click Quickconnect or Connect to establish the connection.
  5. Once connected, you will see your local files on the left and your server files on the right.

3. Locate the WordPress installation

Navigate through the directories on the right-hand panel until you find the folder containing your WordPress installation. This is often named public_html, www, or your domain name. Open this folder, then navigate to /wp-content/plugins/.

4. Deactivate the problematic plugin

WordPress automatically deactivates any plugin whose folder name has been changed.

  1. Right-click the folder of the plugin you believe caused the crash.
  2. Select Rename.
  3. Change the name to something like plugin-name-old (e.g., change contact-form-7 to contact-form-7-old).
  4. Press Enter to save the change.
Do not delete the folder entirely unless you have a backup. Renaming the folder is safer as it preserves your plugin settings and data.

5. Test your site and dashboard

  1. Open your website in a web browser to see if the front end is loading.
  2. Navigate to yourdomain.com.au/wp-admin to attempt to log into your dashboard.
  3. If the site loads, log in using your administrator credentials.

6. Remove or update the faulty plugin

Once you are back in the WordPress admin area:

  1. Go to Plugins > Installed Plugins.
  2. Locate the plugin you renamed via FTP. It will likely show as inactive or missing.
  3. Click Delete to remove the plugin completely.
  4. If you wish to keep the plugin, download a fresh version from the official WordPress repository and upload it via Plugins > Add New > Upload Plugin.

Diagnosing the Cause

Check error logs and enable WP_DEBUG

If you are unsure which update caused the crash, check your hosting error logs via cPanel or enable debugging in WordPress:

  1. Connect via FTP and navigate to your WordPress root directory.
  2. Locate and download the wp-config.php file.
  3. Open the file in a text editor and look for the line define( 'WP_DEBUG', false );.
  4. Change false to true so it reads define( 'WP_DEBUG', true );.
  5. Save the file and upload it back to the server, overwriting the existing file.
  6. Refresh your website to view any PHP errors or warnings displayed on screen.
Remember to set WP_DEBUG back to false once you have finished troubleshooting, as displaying errors on a live site can expose sensitive information.

Troubleshooting

What if I don't know which plugin caused the crash?

If you are unsure which update caused the issue, you can deactivate all plugins at once:

  1. Connect via FTP and navigate to /wp-content/.
  2. Rename the entire plugins folder to plugins-old.
  3. Refresh your site. If it loads, the issue was definitely plugin-related.
  4. Rename the folder back to plugins.
  5. Go into the folder and rename each plugin folder one by one, refreshing your site after each change until the crash returns.

What if the theme caused the crash?

If deactivating plugins does not work, the issue may be your active theme:

  1. Navigate to /wp-content/themes/ via FTP.
  2. Rename the folder of your active theme.
  3. WordPress will automatically revert to a default theme, restoring your dashboard access.
Warning: Renaming the active theme may reset your widgets, menus, and customizer settings. Before proceeding, take note of your current theme settings, widget placements, and menu configurations so you can reconfigure them after restoring access.

File permission issues

If you rename a folder via FTP but the change does not take effect, the issue may be related to file permissions. Ensure that your WordPress directories have the correct permissions (typically 755 for folders and 644 for files) so that the web server can read the updated structure.

What if neither plugin nor theme deactivation restores access?

If renaming plugin and theme folders does not restore access to your dashboard, the issue may be caused by database corruption, a server configuration problem, or a corrupted core WordPress file. In these cases:

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket