Why am I getting this error: “remote end hung up unexpectedly”?

Question

$ git push -u origin master   
Counting objects: 321523, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (85111/85111), done.
error: RPC fai         


        

Answer 1

I encountered this message when we converted a mercurial repository to git and tried to push it to GitHub. The cause turned out to be that we had previously committed some libraries' .git folders into our repository and folders with that name are forbidden by git. The repository seemed to work fine locally and we even pushed it to CodeCommit successfully but GitHub is stricter about that rule and pushes to it would always fail with error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053

To see if that's your issue, you can run git fsck and look for instances of The tree contains an entry with an invalid path of '.git'

The solution for us was to use BFG Repo-Cleaner to get rid of the offending folders and we were then able to push to GitHub without issue.

$ bfg --delete-folders .git --delete-files .git  --no-blob-protection  my-repo.git

FYI, please thoroughly read the BFG information page before using it because it can create merging nightmares if used improperly.

Answer 2

Well, this is caused by some bad network status or some large files included in your commit. In my case, I have tried after some mins, it worked.

So I suggest you should do push several times in some intervals, or increase buffer size and then try to push again?

git config --global http.postBuffer 15728640

Answer 3

Posting the solution that worked for me...

In Short

Just change your network connection and then try again.

The Story

I was also getting this exception on command line (GIT Bash) as well as on TortoiseGIT, when my laptop was connected to Office WiFi. Then I just disconnected my laptop from there and connected it to my SmartPhone's HotSpot. That's it, and error got resolved.

It could be weird for some techies, but no harm in try.

Answer 4

I had fixed similar issues for myself by increasing the memory and packsize limits:

git config --global pack.windowMemory 1048576000

git config --get pack.packSizeLimit 1048576000

Answer 5

MSDN says that errno 10053 is "Software caused connection to abort".

An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

It looks like your server and/or network is unstable. Try to copy large amounts (> 1GB) of data using scp to isolate the problem.

Answer 6

After about 3 hours of trying, the problem was solved after using a VPN