Migration assistant times out when trying to connect to Bitbucket port 443
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
Bitbucket Cloud Migration Assistant fails with an incomplete status with the following error -
1
Failed to connect to bitbucket.org port 443: Timed outDiagnosis
The BCMA Logs might have an entry that looks like this -
1
2
3
4
5
22-10-21 11:32:10,988 WARN [bcma-0] c.a.b.plugin.bcma.plan.PlanService Migration failed for plan 'TestMigration' with error: bitbucketRepositoryDataUpload:
'C:\Program Files\Git\cmd\git.exe -c core.abbrev=40 -c credential.helper= -c credential.username=x-container-token push --porcelain --progress
https://x-container-token@bitbucket.org/test-workspace/test-repository.git refs/*:refs/*' exited with code 128 saying: fatal: unable to access
'https://bitbucket.org/test-workspace/test-repository.git/':
Failed to connect to bitbucket.org port 443: Timed out [abcdefg-1234-1039-9577-dwidwdhadwe::bitbucketRepositoryDataUpload]
The above error indicates that the Bitbucket Server instance is unable to push the repository from Server to Cloud via port 443. This might be due to a variety of reasons such as -
The firewall on the instance/VM of the Bitbucket Server does not allow outbound traffic on port 443
The proxy if any, may not be configured to allow traffic to Bitbucket Cloud
The proxy is incorrectly configured and git is not using the proxy leading to dropped network packets
We can do a network test to diagnose the issue properly. The output of both the commands on successful connections should be as shown below -
1
2
3
4
5
6
7
8
nslookup bitbucket.org
-------------------------------
Server: 10.1.4.20
Address: 10.1.4.20#53
Non-authoritative answer:
Name: bitbucket.org
Address: 104.192.141.11
2
3
4
5
6
telnet bitbucket.org
-------------------------------
telnet bitbucket.org 443 21s
Trying 104.192.141.1...
Connected to bitbucket.org.
Escape character is '^]'.Solution
If the above network diagnostic commands show that bitbucket.org is not reachable, you must configure the server instance network so that packets can travel over port 443 to bitbucket.org.
This maybe done by opening up firewall/security group via TCP port 443 to bitbucket.org or the IP addresses mentioned in our documentation.
If you have a proxy, git must be configured separately to use the proxy. You can do that with the instructions mentioned here.
Was this helpful?