A faulty plugin can lock you out of wp-admin or trigger a white screen of death. Renaming the plugin’s folder deactivates it without database access because WordPress only loads plugins whose folders exist under wp-content/plugins/. Use FTP, SFTP, or SSH to perform the rename when the dashboard is unavailable.
Identify the Plugin
From debug.log, email alerts, or recent changes, note the plugin slug (folder name), e.g. woocommerce or wordfence. Path:
wp-content/plugins/{plugin-slug}/
Rename via SSH
Navigate to the site root, then rename the folder with a suffix such as .disabled:
cd /var/www/vhosts/example.com/httpdocs/wp-content/plugins
ls -la
mv problematic-plugin problematic-plugin.disabledReload the site. wp-admin should load if that plugin was the cause.
Rename via FTP/SFTP
- Connect with FileZilla or
sftp(see connect via FTP/SFTP). - Open
wp-content/plugins. - Right-click the plugin folder → Rename → add
.disabled. - Refresh the website.
Disable All Plugins at Once
Rename the entire plugins directory:
cd /var/www/vhosts/example.com/httpdocs/wp-content
mv plugins plugins.hold
mkdir plugins
touch plugins/index.phpWordPress creates an empty plugins folder; move folders back from plugins.hold one at a time to find the culprit.
Must-Use Plugins
Plugins in wp-content/mu-plugins/ load automatically and are not deactivated by renaming plugins/. Rename individual files in mu-plugins only if you understand their role.
After Recovery
- Log in to wp-admin.
- Update or replace the problematic plugin.
- Remove the
.disabledsuffix only after testing on staging. - Check Plugins screen for orphaned entries.
WP-CLI alternative: wp plugin deactivate.
Summary
Rename the plugin directory under wp-content/plugins via SSH or SFTP to force deactivation when wp-admin is down. Use bulk rename to isolate conflicts, then update or remove the offending plugin. SerVee IT support can perform safe renames during outage tickets if you provide the plugin name and site URL.