Sometimes a plugin update or conflict locks you out of your own dashboard, so you can’t deactivate the plugin causing the problem — a maddening chicken-and-egg situation. The way out is to disable plugins directly through the filesystem. No dashboard required.
The nuclear option: disable everything at once
This is the fastest way to get back in.
- Log in to cPanel and open File Manager (or connect via FTP).
- Navigate to
wp-content. - Rename the
pluginsfolder to something likeplugins-off.
WordPress can no longer find any plugins, so it deactivates them all. Try logging into wp-admin now — it should work. Once you’re in, rename the folder back to plugins. Your plugins reappear, still deactivated, and you can reactivate them one at a time.
The surgical option: disable one plugin
If you already know which plugin is the problem, you don’t need to disable all of them:
- Open
wp-content/plugins. - Rename just the offending plugin’s folder (e.g.
broken-plugintobroken-plugin-off).
WordPress deactivates only that plugin, leaving the rest running.
Finding the culprit
If you disabled everything to regain access, reactivate plugins one by one from the dashboard, reloading the site after each. When the problem returns, the plugin you just activated is the cause. Leave it off and either find an alternative or wait for a fixed update.
Why File Manager beats FTP here
You can do all of this over FTP, but cPanel’s File Manager is quicker and needs no FTP client — you’re already logged into cPanel to manage your hosting anyway. Just make sure Show Hidden Files is on if you’re also poking around config files.
A safer habit going forward
Plugin lockouts almost always follow an update. Update plugins one at a time rather than in a batch, take a backup first, and test on staging for anything critical. That way a bad update is caught before it can lock you out of production.
If renaming the folder doesn’t restore access, the issue may be a theme or a deeper error — send us the details and we’ll investigate.
