For a few months now I think, whenever I'm pushing/pulling/cloning (or i guess doing other network related GIT operations) it takes forever before anything actually seems to happen. That is, it takes around 1 minute before it starts fulfilling the task.
I'm using GIT through "Bash on Ubuntu on Windows" and if I clone using HTTPS there's no problem, however, with SSH it takes too long before it starts. I have tested both HTTPS and SSH for Bitbucket and GitHub and it only seems to be SSH for Bitbucket that is slow.
Example: cloning a repo of less than 2MB takes around 1m10s, while only in the last second the files are actually written to the disk.
I don't know if this could have anything to do with the relatively recent update to the Bitbucket IPs, but deleting my "known_hosts" in ~/.ssh didn't not help either. Is this a known issue? Common GIT tasks are becoming quite cumbersome.
After breaking my head for a day, have figured out the root cause of the issue.
SSH supports both IPv4 and IPv6 and prefers IPv6 if the DNS retrieves AAAA record, but my ISP doesn't support IPv6, which results in huge delays
We can solve it in two ways
After changing ssh_config do restart ssh client, on Ubuntu the command is
"sudo service ssh restart"
It was driving me crazy. Doing "git pull" in any of my repositories was taking 18 minutes... 18 MINUTES!!! to just show "Already up-to-date.".
I just moved to a new home on Feb 29th and I started noticing this in my new home. I was totally sure the problem was with the new internet configuration (a router acting as a switch behind the ISP router) and I tried a lot of configurations but nothing fixed the error. Only today, when I connected my PC with an ethernet cable directly to the ISP router and it didn't fix the error, I started thinking the problem was Bitbucket and not my home network. That made me look for a solution here.
Once I added your setting suggestion to ssh_config, it immediately worked.
Thank you, thank you, thank you.
Navigate to this folder C:\Users\<username>\.ssh
Create new config file if it not presented.
To create a new config file.
Open git bash from the folder and enter below command.
Once you created the file, open the file and add the below text.
Save it and close the file.
Reload the terminal and try here. It will work
Thanks for the suggestion. Apparently there must be something to it. At work I had no problems and turning on VPN from home also helped... question is why :/
Could it be my router or ISP that is somehow filtering that connection? Although I don't see why I would have no trouble with GitHub then...
Hmm, installing Wireshark I can see that it must be something inside bash/git itself, because no packets are captured until after a minute of silence. SSH'ing against GitHub instantly shows packets being transferred however.
Perhaps I should reinstall git or maybe even bash if there's no other way :/
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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