Roll back a rolling upgrade

The steps on this page only apply if you have used the rolling upgrade method to upgrade Confluence. 

If something goes wrong during a rolling upgrade, you may be able to roll back to the original version. 

How you roll back depends on the upgrade stage you have reached, and also how you deploy Confluence. To check the current cluster status go to Administration  > General Configuration > Rolling upgrades

On this page:

Screenshot: Cluster status in the Rolling upgrades screen

Cluster upgrade statusAction to take


In the rolling upgrades screen, disable Upgrade mode.



Follow the steps below to roll back the application version on each upgraded node: 

  • Rollback steps - manual and Azure deployments
  • Rollback steps - AWS deployments
  • Rollback steps - Kubernetes deployments

Once all nodes are running the original version, the cluster status will change to Ready to upgrade. 



You can't roll back once final cluster-wide upgrade tasks have started running. If you stop Confluence on the node running the upgrade task, another node will pick up where the stopped node left off. 

If upgrade tasks fail, you will need to investigate the problem, then re-run upgrade tasks from the rolling upgrades screen. 


You can't roll back to an earlier version, because the upgrade was finalized successfully.

Roll back a rolling upgrade - manual and Azure deployments

These instructions assume your original install directory is still available. If it's not, you may need to restore it from your backup. You don't need to restore the local home directory. 

To roll back an upgraded node to its original version:

  1. Access the node through a command line or SSH.
  2. Shut down Confluence gracefully on the node. 
  3. Wait for the node to go offline. You can monitor its status on the Node status column of the Rolling upgrade page’s Cluster overview section.
  4. If you run Confluence as a service:
    • On Windows, delete the new service then re-install the old service by running <old-install-directory>/bin/service.bat. 
    • On Linux, update the service to point to the old installation directory (or use symbolic links to do this).
  5. Start Confluence (from the original install directory) on the node. You should not see the setup wizard.

Once all nodes are running the same version, the cluster’s status will revert back to Ready to upgrade. You can then turn off Upgrade mode.

Roll back a rolling upgrade - AWS deployments 

To roll back the upgraded nodes to the original version:

In the AWS console, go to Services > CloudFormation. Select your deployment’s stack to view its Stack Details.

  1. In the Stack Details screen, select Update Stack.
  2. From the Select Template screen, select Use current template and select Next.
  3. Set the Version parameter to your original version.
  4. Select Next. Click through the next pages, and then to apply the change using the Update button.

Afterwards, terminate all nodes running the new version of Confluence. AWS will replace each with a node running the original version. Once all nodes are running the same version, the cluster’s status will revert back to Ready to upgrade. This will also allow you to disable Upgrade mode.

Last modified on Mar 22, 2022

Was this helpful?

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