How to disable WordPress plugins from phpMyAdmin in cPanel
If your site stops opening after you install or update a plugin, you can disable all plugins from phpMyAdmin without logging in to /wp-admin. This method helps when you see a white screen, error 500, or a dashboard lockout caused by a plugin.
Make this change carefully: you will edit a database value. Before changing it, export a copy so you can return to the previous state if something does not work as expected.
Before you start
- Have access to cPanel for the account where the site is installed.
- Identify the site folder, usually
public_htmlor the domain folder. - Download a copy of
wp-config.phpbefore checking connection details. - Export the database from phpMyAdmin before editing the
active_pluginsvalue.
Steps
- Log in to cPanel and open File Manager.
- Go to the folder where the site is installed and open
wp-config.phpfor reference only. - Copy the
DB_NAMEvalue; that is the name of the database you will edit. - Return to cPanel and open phpMyAdmin from the databases section.
- Select the database that matches
DB_NAMEin the left panel. - Export the database before making changes: use Export, SQL format, and save the file on your computer.
- Find the table that ends in
_options. The prefix can vary, for examplewp_options,nh_options, or a custom one. - Inside that table, find the
active_pluginsrow in theoption_namecolumn. - Edit the
option_valuefield for that row and replace its contents witha:0:{}. - Save the change and open the site in a private window.
- If the site loads, log in to
/wp-admin/and reactivate plugins one by one until you find the one that caused the issue.
Final verification
- The site stops showing the white screen, error 500, or plugin-related lockout.
- You can access
/wp-admin/with your administrator user. - The
active_pluginsrow keeps thea:0:{}value until you reactivate plugins from the site dashboard. - By reactivating plugins one by one, you can identify which one breaks the site again.
Common errors
- You cannot find the
wp_optionstable → your installation uses another prefix → look for the table that ends in_optionsinside the correct database. - The site still shows an error after saving → the problem may come from the theme, PHP memory, or the
.htaccessfile → check errors from cPanel before changing more values. - The dashboard fails again when you enable a plugin → that plugin or version is causing the conflict → leave it disabled and update it, replace it, or ask support for help.
Recommended reading
Still need help?
If this guide didn’t solve your issue, our team can help you via ticket.