It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sourcetree 3.2.6 FATAL ERROR: Server unexpectedly closed network connection

Hello,

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 git@bitbucket.org:company/project.git 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.

1 answer

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. 

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 https://crypted2.com/2018/01/06/fix-sourcetree-git-over-ssh/

Not sure which one fixed the problem.

Like durval_pires likes this

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Sourcetree for Windows - CVE-2019-11582 - Remote Code Execution vulnerability

A vulnerability has been published today in regards to Sourcetree for Windows.  The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...

4,935 views 0 12
Read article

Community Events

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

Events near you