Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Why does git fetch take forever to complete on Bitbucket only?

I have the problem where `git fetch` takes an enormous time to complete - always 13 minutes, and 9 seconds ± a few ms -, which does not happen on other git origins like e.g. Github repos - to eliminate issues caused by network. The consistent time taken to complete the operation makes me assume the establishing of the connection takes slightly over 13 minutes and the actual response is what makes the variation in completion time, but I have no idea what causes this.

This problem occured a few days ago, before fetch worked as usual, but there has been no significant event that would explain why this change in speed occured.

I work with SSH, I have not tried using HTTPS yet because I work with SSH on all repos I contribute to.

1 answer

1 accepted

0 votes
Answer accepted
Erez Maadani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 29, 2022

I suggest to start by changing your SSH debug level to more verbose. Depending on your git client version, you can use one of the following:

1. From Git version 2.3.0, you can use the environment variable GIT_SSH_COMMAND and pass the -v verbose argument:

GIT_SSH_COMMAND="ssh -v" git clone example

2.  From Git version 2.10.0, you can save this configuration globally, or per repo:

git config core.sshCommand "ssh -vvv"
git pull

See original answer here 

Thanks, I was unaware you could do that!
That pointed me into the right direction, which leads me to the problem of my network refusing connection to bitbucket's IPv6 addresses, documented here:

I have solved the issue with the mentioned workaround, thanks a lot!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events