Get started with Bitbucket Cloud
New to Bitbucket Cloud? Check out our get started guides for new users.
Smart mirroring is being deprecated
Starting on April 21, 2021, smart mirroring in Bitbucket Cloud will no longer be available for new installations. Existing installations will continue to function as usual, but we will no longer be supporting this feature.
This page describes how to identify and solve problems you may have with Bitbucket Cloud Smart Mirroring: For further reference, read the Bitbucket Data Center FAQ.
This table lists the basic problems that can prevent communication between Bitbucket Cloud and your Smart Mirror:
Possible cause | Action you can take |
---|---|
The mirror server is not running. |
|
The mirror server is not actually connected to the network. |
|
A firewall or other network device is blocking connections that use the particular combination of host address and port. | Note that outgoing calls from Bitbucket are incoming calls for the mirror. Similarly, outgoing calls from the mirror are incoming calls for Bitbucket. Both need to work.
|
The protocol being used to make the connection is incorrect (for example, it uses HTTP instead of HTTPS). |
1
2
3
4
5
server.port=7990
server.proxy-name=<mycompany.com>
server.secure=true
server.scheme=https
server.proxy-port=443 See Bitbucket Data Center config properties for more information. |
The mirror application is running, but it's not listening on the port that Bitbucket Cloud is trying to connect to. |
There are some minimum requirements that your SSL certificate must meet:
The certificate common name (CN) must match the host name (the URL address) for the application.
The certificate timestamp must still be valid.
The certificate must be installed into the correct Java trust store (Bitbucket Data Center is a Java application that bundles the Tomcat application server). To check that certificates are present in the Java trust store see Check the SSL certificate location.
Make sure that your key and certificate are correctly configured in either the mirror or your HTTPS proxy. See See of the options in Securing a reverse proxy using HTTPS for SSL configuration details.
To see details of a certificate, visit the application in your browser and click the padlock in the browser address bar. You can also check SSL certificate details online (for example using https://www.digicert.com/help/).
Under some circumstances you may experience problems when using the mirror administration UI, such as:
Adding projects to, or removing projects from, the mirror fails to add some projects and displays an error message prompting you to refresh the page to try adding the projects again.
When trying to use the Mirror Support tools, you receive an error message notifying you that you are not logged in and to log in to continue using this tool.
Both of these problems can occur if your browser does not allow third-party cookies. The workaround is to enable third-party cookies – see BSERV-8558 for details.
Your mirror must be configured for HTTPS access in order to use a mirror instance. See Proxying and securing Bitbucket Data Center for more information.
If appropriate, see Setting up SSH port forwarding.
The property Mirror base URL can only be set once. It gets set by the wizard that runs when you first start Bitbucket Data Center. If configured incorrectly, or you need to change it, you'll need to delete your mirror and set it up again.
When cloning or pulling from the Bitbucket mirror you may see the following error message in a terminal:
1
2
3
Cloning into 'local-repo'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Possible causes | Actions you can take |
---|---|
Missing public key |
|
Unsupported SSH key type |
|
Was this helpful?