Mirror node is not coming up with error code 409 while trying to register with Bitbucket Data Center.
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
Attempting to initialize the Mirror node fails, accompanied by error code 409, during the registration process with the Bitbucket Data Center or the upstream server.
1
2
3
2025-02-21 10:53:10,768 WARN [Caesium-1-1] @D5GUB4x123x4567568052x1 c.a.b.i.m.m.UpstreamRegistrationJob Registration with the upstream server failed (A request to the configured upstream server failed because the response was unexpected. (Status code: 409, message: '')). Retrying in 21s
2025-02-21 10:53:10,768 DEBUG [Caesium-1-1] @D5GUB4x123x4567568052x1 c.a.b.i.m.m.UpstreamRegistrationJob Registration error:
com.atlassian.bitbucket.internal.mirroring.mirror.UpstreamRequestFailedException: A request to the configured upstream server failed because the response was unexpected. (Status code: 409, message: '')Environment
Tested on Bitbucket Data Center 8.9.6 and also applicable to other versions of Bitbucket Data Center.
Cause
This issue generally occurs when Mirror is configured behind the reverse proxy or load balancer and the reverse proxy or its relevant service is not running.
Solution
Resolving the issue with the reverse-proxy or reverse-proxy service, should resolve this issue.
Was this helpful?