Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket Data Center Mirror Won't Connect to Main Server Edited

Hi everyone,

I'm currently evaluating how the Bitbucket Data Center mirror works, so that we can then order a license for our company, but it seems all attempts to get it to work have failed.

Both the main server [] and the mirror [] are running under Ubuntu 20.04, are now using HTTPS and the ssl-keystores are available on both.

I'm using self-signed certificates on both the server and the mirror and I imported them into 2 keystores on the mirror and server respectively, with these commands: 

keytool -import -alias $alias -trustcacerts -file file.pem -keystore /var/atlassian/application-data/bitbucket/shared/config/ssl-keystore


keytool -import -alias $alias -trustcacerts -file file.pem -keystore /opt/atlassian/bitbucket/7.6.0/jre/lib/security/cacerts


The main server is running properly.


Before starting the mirror service (systemctl start atlbitbucket), I've edited the file manually to switch to https (according to Bitbucket documentation) and to point to the generated keystore.


However, the mirror doesn't connect with the main server and there is this error message in the log:


"... Signature does not match ..."



Any idea where to start debugging this?


Thank you.



1 answer

1 accepted

0 votes
Answer accepted

Ok, problem solved in the meantime by first exporting the certificates on primary and mirror with this command from ssl-keystore:

keytool -export -alias $alias -keystore $keystore -rfc -file certificate.cert

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

601 views 15 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you