In a Data Center installation, not all nodes appear to be connected to the mirror

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Problem

In a Data Center installation of Bitbucket Server, some nodes are not showing as connected.

Some of the nodes correctly display the mirror configuration page.

The following appears in the user interface (Administration → Mirrors):

1 Unable to connect to the mirror

Cause

The mirror add-on has been disabled or was not enabled during the startup.

Resolution

Resolution #1

Re-enable the mirror add-on on all failing nodes

  • Browse to the Manage add-ons page and locate the mirror one. This will have "Mirror - <mirror name>" as title and "bitbucket.mirror.<mirror id>" as Add-on key

  • Enable it with the provided option

Resolution #2

Restart the entire Bitbucket Server instance (including all nodes and the mirrors).

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.