Failed to connect to bitbucket.org port 443: Network is unreachable

Question

I am getting issue while pushing code.

git push origin master

fatal: unable to access \'https://xxxxxxxxxx@bitbucket.org/xxxxxx/xxxxxx.git/\': 
Failed to co         


        

Answer 1

we can solve by setting proxy in command prompt before push commits to the repo.

set HTTP_PROXY=http://user:pass@your_proxy: port

Answer 2

I got that problem and even change /etc/hosts with IP address from official IP addresses https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html

Server not clone any project from bitbucket through use ip4 like that 104.192.143.1 and just slow and no response

For me SOLVED enable/add ip6 in /etc/network/interfaces . LOL, For every virtualization individual, but for kvm is looks like

iface ens3 inet6 static
        address 2a04:5200:fff5::89e
        netmask 48
        gateway 2a04:5200:fff5::1
        up ip -6 addr add 2a04:5200:fff5::8ea dev ens3
        down ip -6 addr del 2a04:5200:fff5::8ea dev ens3

For OpenVZ looks like

iface venet0 inet6 manual
    up ifconfig venet0 add 2a04:5200:fff7::bb6/128
    down ifconfig venet0 del 2a04:5200:fff7::bb6/128
    up route -A inet6 add default dev venet0
    down route -A inet6 del default dev venet0

Try active or add ip6 ip adress in your panel hosting and reinstall it, but delete all files there.

Answer 3

Flushing dns cache worked for me (Ubuntu, 18.04):

sudo systemd-resolve --flush-caches

Answer 4

TLDR; Try first git push -4 origin master

---

There are issues reporting current problems to access bitbucket through https (issue 13060, issue 12184)

The usual answer is:

"Failed to connect" errors could be anything from DNS issues to local network problems to ISPs that are incompletely routing Bitbucket traffic. Unfortunately, there isn't enough detail in any of these comments to diagnose the exact problems, which may or may not be related to each other. If you could, please open a support ticket with the results of the following commands:

For OS X, Linux, and other UNIX-based operating systems:

ping -c10 bitbucket.org
ping6 -c10 bitbucket.org
traceroute bitbucket.org
traceroute6 bitbucket.org
GIT_CURL_VERBOSE=1 git ls-remote https://bitbucket.org/bitbucket/do_not_delete

For Windows:

ping -n 10 bitbucket.org
ping -n 10 -6 bitbucket.org
tracert bitbucket.org
tracert -6 bitbucket.org

(To clarify: "ping6" and "traceroute6" are the IPv6 equivalents of "ping" and "traceroute", respectively, and "GIT_CURL_VERBOSE=1" before any git command will detail all the HTTP-specific parts of the connection.
On the Windows side of things, the "-6" in the command line specifies that your computer should use IPv6 for the ping or tracert.)

Additionally, if you suspect that your problem is related to Bitbucket's IPv6 support, then you should be able to test your overall IPv6 connectivity by opening the following links in your browser:

https://ipv6.google.com
https://www.v6.facebook.com

Those links should not work at all if your IPv6 connection is disabled or misconfigured.

---

More generally, check your /etc/hosts for any entry regarding bitbucket.org.
See "What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall?"

The IP address has recently changed:

Since July 28, 2018: IPv4 inbound for bitbucket.org, api.bitbucket.org, and altssh.bitbucket.org

18.205.93.0/25
18.234.32.128/25
13.52.5.0/25

Keep in mind ping might be blocked, triggering the same error message.

---

The IPV6 can be problematic: the same thread advises:

This is probably coming when git is trying to push over IPV6. I'm not exactly sure why getting this error with IPV6. But here are different solutions, that you can use to fix this problem.

Add any one of the following IP into /etc/hosts file to force git to use IPV4

104.192.143.2
104.192.143.3
104.192.143.1

That is,

104.192.143.2 bitbucket.org

To /etc/hosts file

(Or)

Upgrade your git to latest version. Probably this could solve the problem else use the following option when you push after you upgrade git (this feature was added newly to git)

 -4, --ipv4 use IPv4 addresses only

That is ,

git push -4 bitbucket dev

You can specify this option -4 while you push, pull or clone.

(Or)

You may configure git to use http proxy to solve this problem

 git config --local http.proxy http://proxyuser:proxypwd@proxy.server.com:8080

If you are already using latest version of git, you can simply use option -4 to force git to use IPV4 address or you can go with /etc/hosts

If you wanna see debug message while pushing or pulling code you can set following environment variable before you do so,

export GIT_CURL_VERBOSE=1

Answer 5

If you are still getting this error and the above doesn't work, it may be a firewall issue; meaning something is blocking the connection deliberately, rather than a "failure". Try double-checking your Firewall, and follow your standard steps for Network Troubleshooting.

From the basic google searching I did, the three main reasons for this error is invalid proxy settings, mishandling IPv6 Addresses, or general network error on client-side.

Answer 6

I followed the discussion on this page and added this line to my hosts file:

104.192.143.2 bitbucket.org

It works . My system is unbuntu, so the host file is in /etc/hosts and you need have root permission.