The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

FATAL ERROR: Server unexpectedly closed network connection

Harikrishna.Pasavala1
November 21, 2023

Hi, I am getting this below error and tried multiple solutions, but they didn't work for me. Can any one help me on this ?

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@git.ng.bluemix.net:**********/wcs9.git C:\wcs9
Cloning into 'C:\wcs9'...
FATAL ERROR: Server unexpectedly closed network connection
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: index-pack failed
Completed with errors, see above.

Thanks inadvance!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Martin Runge
Community Champion
June 23, 2026

Hi @Harikrishna.Pasavala1

The remote host is git.ng.bluemix.net, which is IBM Cloud's Git service. The "server unexpectedly closed network connection" combined with early EOF and index-pack failed almost never points to a Sourcetree bug itself. It usually means the connection was dropped mid-transfer, and Git couldn't finish assembling the packfile on your end.

There is a high chance that the repo is very large. I would try a shallow clone first to confirm that connectivity is the issue and not something structural.

I would add these two Git config options globally in Sourcetree under Tools > Options > Git or via your ~/.gitconfig:

git config --global core.compression 0
git config --global http.postBuffer 524288000

TAGS
AUG Leaders

Atlassian Community Events