Mirror fails to synchronise with upstream Bitbucket even though user is able to access the Bitbucket web application
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
Summary
When a user accesses the Bitbucket web application from the client's system, the user is able to access the Bitbucket web application. However, the mirror status is not synchronized.
Environment
Bitbucket Data Center 7.13.0
Bitbucket upstream server and mirror server are both hosted on a different server.
Diagnosis
1
curl -v https://<mirror_url>/statusCurl command to the mirror server from the client system returns below error:
curl: (7) Failed to connect to <mirror_url> port 443: Connection timed out
Cause
The mirror page in the Bitbucket web application (Administration > Mirror > Mirror Name) is embedded in the administration panel via the iframe.
Therefore, the mirror page is a web document from the mirror server embedded in the Bitbucket web application.
Even though the client's system is able to access the Bitbucket web application through the upstream Bitbucket server, it needs to be able to access the mirror server as well because the mirror page is served through an iframe.
The iframe webpage is served from the mirror server and it is not served from the upstream Bitbucket server.
This shows that the client's system needs access to both the upstream Bitbucket server and the mirror server.
Because of that, the mirror status is not synchronized because the client's system does not have access to the mirror server.
Solution
Allow the required port at the mirror server to be opened to the client's system.
If there is a firewall between the client's system and the mirror server, check with your network administrator to configure the firewall to allow traffic from the client's system.
Was this helpful?