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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sourcetree 3.2.6 FATAL ERROR: Server unexpectedly closed network connection


Whenever I try and clone anything through Sourcetree 3.2.6 it outputs this error, on any computer. However, I can access the repositories through the command line just fine.


"git -c filter.lfs.smudge= -c filter.lfs.required=false -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks clone --branch master D:\Dev\Repos\project
Cloning into 'D:\Dev\Repos\project'...
FATAL ERROR: Server unexpectedly closed network connection
fatal: early EOF
fatal: the remote end hung up unexpectedly
fatal: index-pack failed

Completed with errors, see above."


I have run out of steps to try and fix this, my Google-Fu has failed thus far.

2 answers

Did you find a fix for this?

Not yet, it seems to be better now a little bit but if you just keep retrying it eventually goes through, it only happens on the first clone.


You can also pull the Repo via command line and then hook it up in SourceTree, I have been doing that for now when it happens.

Yes, git bash command line works.

Through Sourcetree, it seems to throw the error only for our large project. The Sourcetree clone operation works for all other (regular-sized) projects.

I've found that it does work in Sourcetree if you change the clone depth to 1 (under Advanced Options > Clone depth). This is a git "shallow" clone, which lets you pull down just the latest commits, not the entire repo history. A depth of 1 copies only the latest revision of a repo.

I've also read something about changing the git http.postBuffer size, but I haven't explored that. We're using SSH, so I'm not sure if that has any impact. 

Like # people like this

I will give that a try next time I encounter this problem.

Just to let you guys know, we had the same problem but changing clone depth to 1 did not help. Our repo size is around 300MB.

It turns out the issue is that folder that we clone into did not exist. We had to create on Windows. We also tried

Not sure which one fixed the problem.

Like # people like this

@Freeh you saved my life, the one that did it was the putty reinstall. Thank youuuu

Like # people like this

@Sarah Bailey You are a life saver. Who knew updating Putty will work.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events