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

FATAL ERROR: Server unexpectedly closed network connection


I'm trying to push some changes to bitbucket but getting this error constantly: 


Git LFS: (0 of 38 files, 8 skipped) 0 B / 2.14 MB, 12.36 MB skipped
FATAL ERROR: Server unexpectedly closed network connection
fatal: sha1 file '<stdout>' write error: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly


I'm using SSH and my PrivateKey is loaded in Pageant, not sure where can be problem.


1 answer

1 accepted

0 votes
Answer accepted

This suggests that there's something wrong with the server you are trying to connect to, or the network you are connecting over.

You'll need to read the logs on the server side, probably the system ones to see if the connection was severed or the service stopped.

Is it possible that it's related to size of LFS files? I didn't get any problem to push single file (gitattribute), but when I tried to push several LFS files (one of them close to 10mb's) it gave me this.

EDIT: Ok I checked there is no limitation to LFS file for bitbucket. Will follow your advice thanks.

Like Neokron likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events