Connecting to bitbucket.org over IPv6

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Problem

Diagnosis

  • When performing GIT operations, you may encounter errors such as:

    "error: RPC failed; curl 52 Empty reply from server" 
    "Failed to connect to bitbucket.org port 443: Network is unreachable"
  • Attempting to execute the following commands results in errors (we recommend you verify this to determine if you are experiencing this issue):

    > ssh -v git@bitbucket.org 
    "port 22: Operation timed out"
    
    > "GIT_CURL_VERBOSE=1 git ls-remote https://bitbucket.org/bitbucket/do_not_delete"
    "Hostname was not found in DNS cache" 

For SSH, please also see this article for more details: Troubleshooting SSH issues


Resolution

In case you are behind a firewall blocking IPv6 traffic, you will need to add our IPv6 addresses to your allowlist:

Workaround

If you are still encountering errors after allowlisting our IPv6 addresses, then forcing the connection to use IPv4 can be achieved by adding the following line to your hosts file and attempting to connect again:

104.192.141.1 bitbucket.org
DescriptionConnecting to bitbucket.org over IPv6
ProductBitbucket Cloud
Last modified on Jan 24, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.