Locked Out of WordPress Dashboard

Locked Out of WordPress Dashboard? Disable Plugins via cPanel or FTP

A faulty plugin update, a conflict between extensions, or a PHP error can cause your WordPress website to stop loading correctly or prevent you from logging into your dashboard. In such cases, the standard method via Plugins > Installed Plugins is no longer accessible.

The good news is: you can also disable WordPress plugins from the "outside" – directly via the cPanel File Manager, using FTP/SFTP, or in advanced cases, through the database. This method is particularly helpful when a plugin blocks the website, triggers a critical error, or makes the admin area unreachable.

When is this method useful?

Manually disabling plugins is an emergency measure. You should use it when normal access to WordPress is no longer possible.

Typical situations:

• WordPress displays a critical error.
• The dashboard remains white or does not load completely.
• The website is no longer reachable after a plugin update.
• The login works, but an error message appears immediately afterward.
• A security plugin accidentally locks you out.
• WooCommerce or a payment plugin causes an error.
• A page builder blocks the editor.
• A caching plugin delivers broken pages.
• You suspect a plugin conflict but cannot disable any plugins in the dashboard.

Method 1: Disable all plugins via cPanel File Manager

This method is usually the fastest way to proceed if you do not know which plugin is causing the error. It involves temporarily renaming the entire plugin folder.

1. Log into your cPanel.
2. Open the File Manager.
3. Navigate to the WordPress root directory of your website.
4. Open the wp-content folder.
5. Look for the plugins folder.
6. Right-click on the folder and select Rename.
7. Rename the folder to something like plugins_old.
8. Afterward, call up your WordPress login page again.

If the error was caused by a plugin, you should now have access to the dashboard again.

What happens when you rename the plugin folder?

By default, WordPress expects plugins to be in the following folder:

wp-content/plugins/

If this folder is renamed, WordPress can no longer find the installed plugins. As a result, they are deactivated. Your plugin files are not deleted during this process, and most settings remain preserved in the database.

Once you rename plugins_old back to plugins, the plugins will reappear in WordPress but will generally remain deactivated. You can then reactivate them one by one.

Method 2: Disable only a specific plugin

If you already know or strongly suspect which plugin is causing the error, it is better to disable only that specific plugin. This reduces the risk of unnecessary side effects.

1. Open the File Manager in cPanel.
2. Navigate to wp-content/plugins/.
3. Look for the folder of the affected plugin.
4. Rename only this folder.
5. Example: contact-form-7 becomes contact-form-7_disabled.
6. Call up the website or the dashboard again.

WordPress will no longer be able to load this plugin. If the plugin was the root cause, the website should function normally again.

Method 3: Disable plugins via FTP or SFTP

If you prefer not to work with the cPanel File Manager, you can perform the exact same process using FTP or SFTP.

1. Connect to your hosting using an FTP program like FileZilla.
2. Open the WordPress directory.
3. Navigate to wp-content/plugins/.
4. Rename either the entire plugins folder or just the folder of the faulty plugin.
5. Test your website afterward.

For security reasons, SFTP is preferable to FTP if your access credentials support it.

Method 4: Disable plugins via the database

This method is only suitable for advanced users. WordPress stores active plugins in the database within the option named active_plugins. If file access is not possible, you can disable plugins via phpMyAdmin.

Basic procedure:

1. Open phpMyAdmin in cPanel.
2. Select the database belonging to your WordPress installation.
3. Open the wp_options table. The prefix may vary, for example cw_options.
4. Search for the entry active_plugins.
5. Carefully edit the value or reset it.

For most customers, the method using the File Manager or FTP is significantly simpler and safer.

After gaining access: Reactivate plugins individually

Once you are back in the dashboard, you should identify the root cause systematically.

1. Rename the folder plugins_old back to plugins.
2. In the dashboard, open Plugins > Installed Plugins.
3. Activate one plugin after another.
4. Check the website after each activation.
5. As soon as the error reoccurs, you have found the likely culprit.
6. Deactivate this plugin again.
7. Check if an update or an alternative is available.

Do not activate all plugins at the same time. Otherwise, you won't know which plugin triggered the error again.

Narrowing down the cause of the error

If a specific plugin causes the error, check the following points:

• Is the plugin up to date?
• Is your WordPress version up to date?
• Is your PHP version compatible?
• Was there a plugin update shortly before?
• Was there a theme update?
• Was a new plugin installed?
• Are there error messages in the error log?
• Is the plugin compatible with WooCommerce or your theme?
• Are there known issues reported to the plugin developer?

If the error occurs after an update, a rollback or an update fix from the developer might be required.

Checking Error Logs in cPanel

Server error logs can provide clues about which plugin caused the error. Especially with PHP errors, the path to the affected file is frequently displayed there.

Typical path in an error message:

/wp-content/plugins/plugin-name/file.php

If you repeatedly see the same plugin folder in an error log, that plugin is a likely trigger.

Pay special attention to Caching Plugins

Caching plugins can keep errors visible even after the actual problem has been resolved. Therefore, clear the cache after every change.

Check the:

• WordPress cache,
• Plugin cache,
• Server cache,
• CDN cache, if used,
• Browser cache.

If a caching plugin itself is causing the error, deactivate that plugin first and then delete the cache files if necessary.

Security Plugins and Locked Out Administrators

Sometimes the cause is not a technical bug, but rather a security plugin blocking the login. This can happen if too many failed login attempts were detected, an IP address was blocked, or a two-factor configuration is faulty.

In such cases, manually disabling the security plugin can help you regain access. Afterward, you should check the settings carefully before reactivating the plugin.

WooCommerce Shops: Caution in Live Operations

If you run a WooCommerce shop, disabling all plugins can affect payment methods, shipping options, product features, or checkout processes. Therefore, proceed with extreme caution.

Rules for shops:

• Use a staging site first whenever possible,
• Do not unnecessarily disable plugins while orders are actively being placed,
• Perform a test order after resolving the error,
• Check payment providers,
• Test shipping and tax calculations,
• Monitor order confirmation emails.

What you should not do

• Delete plugin folders without knowing if the plugin contains important data.
• Reactivate all plugins simultaneously.
• Immediately reactivate faulty plugins without checking the cause.
• Modify database values without creating a backup.
• Disable and reactivate WooCommerce payment plugins without testing.
• Ignore error messages.
• Install a plugin from an unknown source as a replacement.

SEO and User Experience during Plugin Errors

If your website is unavailable due to a plugin error, it can negatively impact visitors and search engines. Fast troubleshooting is therefore essential.

Particularly critical issues include:

• Homepage not reachable,
• Contact form not working,
• Shop checkout blocked,
• SEO plugin disabling important meta data,
• Redirection plugin failing,
• Cache serving error pages,
• Mobile display broken.

After fixing the error, you should manually test the most important pages.

Recommended Procedure

1. Stay calm: Plugin errors can often be fixed without any loss of data.
2. Check backup: Secure a backup before making changes if possible.
3. Open cPanel File Manager: Navigate to the wp-content folder.
4. Disable plugins: Rename either the entire plugin folder or the individual plugin folder.
5. Test dashboard: Try logging in again.
6. Rename folders back: Make plugins visible again.
7. Activate plugins individually: Identify the culprit.
8. Check error logs: Look for clues pointing to PHP errors or plugin conflicts.
9. Update or replace the problematic plugin: Do not simply ignore it.
10. Test the website completely: Check forms, shop, login, pages, and cache.

Frequently Asked Questions about Externally Disabling Plugins

Are plugins deleted when I rename the folder?

No. Renaming does not delete the files. WordPress is simply temporarily unable to load the plugins.

Will plugin settings be lost?

In most cases, settings remain preserved in the database. However, individual plugins may behave differently.

Can I disable just one plugin?

Yes. Just rename the folder of the affected plugin under wp-content/plugins/.

What do I do if I don't know which plugin is to blame?

First, rename the entire plugins folder. Once access is restored, activate the plugins one by one until the error reappears.

Can I also perform this method via FTP?

Yes. The process is identical: rename the plugin folder via FTP or SFTP.

Why does the error persist despite disabled plugins?

If so, the cause might not lie within a plugin, but rather with the theme, the PHP version, the .htaccess file, the database, a cache, or a server configuration.

Should I delete the faulty plugin?

Not immediately. First check if it contains important data or if an update is available. If you no longer need it or if it is unsecure, you can delete it after creating a backup.

Can CURIAWEB see which plugin is causing the error?

In many cases, server logs provide clues pointing to the faulty plugin path. CURIAWEB support can assist you with the analysis.