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

Unable to clone a specific repository - remote end hung up unexpectedly

We've been trying to clone this repository all day ( , but keep hitting this error :

git -c filter.lfs.smudge= -c filter.lfs.required=false -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree clone /Users/mahesh/Projects/ff.git 

Cloning into '/Users/mahesh/Projects/ff.git'...

warning: templates not found /usr/local/git/share/git-core/templates

packet_write_wait: Connection to port 22: Broken pipe

fatal: The remote end hung up unexpectedly

fatal: early EOF

fatal: index-pack failed

Completed with errors, see above

Not facing this error with our other repos.
What can be the cause?



2 answers

1 accepted

1 vote
Answer accepted

The problem was solved by using a faster  connection

0 votes
Manju Atlassian Team Jun 21, 2018

Are there large files in this repo and does it have LFS enabled?

Yes, there are. lfs is not enabled.

Manju Atlassian Team Jun 22, 2018

Can you enable LFS on this repository and see if it solves the issues? 

It already is.

An updated that the cloning works on a lan, but fails on our WiFi.

Manju Atlassian Team Jun 22, 2018

My best guess is that some of the files aren't being able to be downloaded on the wifi network due to its size. Please try cloning via command line and if it fails there as well, it is mostly a network issue. 

Some of the users are facing same issue,we have increased the buffer size however the issue still persist 

Kindly help us the solve the workaround

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events