How to reset all Confluence plugins back to their default state through the database

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Prelude information

The state of a Confluence plugin is stored in the table bandana with the bandanakey plugin.manager.state.Map.

If a plugin is in the default state, its entry will not appear in the 'plugin.manager.state.Map'.

For example, atlassian-failure-cache-plugin is enabled by default; therefore, the entry state for atlassian-failure-cache-plugin does not appear in the 'plugin.manager.state.Map' unless it is disabled. The same applies for plugins that are disabled by default.

Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

How to Change a Plugin Back to Its Default State

The following is the process for resetting a plugin back to its default state:

  1. Shutdown Confluence.
  2. Backup your database in case you need to revert the changes.
  3. Run the following query in your database:

     select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map';
  4. The result should be something similar to this:


  5. Use the following SQL query to delete all non-default plugin modifications:

    update BANDANA 
    set BANDANAVALUE='<map/>'
    where BANDANAKEY='plugin.manager.state.Map';
  6. Clear Plugin Cache
  7. Restart Confluence
Last modified on Feb 3, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.