Why am I getting this error: "the remote end hung 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 failed; curl 55 SSL_write() returned SYSCALL, errno = 10053 fatal: The remote end hung up unexpectedly Writing objects: 100% (321523/321523), 4.29 GiB | 17.11 MiB/s, done. Total 321523 (delta 159406), reused 320112 (delta 158718) fatal: The remote end hung up unexpectedly Everything up-to-date 

Answer 1

Well, this is due to incorrect network status or some large files included in your commit. In my case, I tried in a few minutes, it worked.

Therefore, I suggest you do it several times several times, or increase the size of the buffer, and then try to click again?

 git config --global http.postBuffer 15728640 

Answer 2

I came across this post when we converted the mercury repository to git and tried to push it to GitHub. The thing turned out to be that we previously transferred the .git library folders to our repository, and folders with this name are forbidden by git . The repository seemed to work fine locally, and we even successfully clicked on CodeCommit, but GitHub is more strict on this rule and clicked on it, it will always fail with error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053 error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053

To find out if this is a problem, 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 the BFG Repo-Cleaner to get rid of the corrupted folders, and then we could click on GitHub without any problems.

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

FYI, please read the BFG information page carefully before using it, because it can create a nightmare merge if used improperly.

Answer 3

MSDN says errno 10053 is "Software caused by disconnection."

The connection was interrupted by the software on your host computer, possibly due to a data transfer timeout or protocol error.

It appears your server and / or network is unstable. Try copying large volumes (> 1 GB) of data with scp to isolate the problem.

Answer 4

Publishing a solution that helped me ...

In short

Just change your network connection and try again.

Story

I also got this exception on the command line (GIT Bash) as well as in TortoiseGIT when my laptop was connected to Office WiFi. Then I just turned off my laptop and connected it to my SmartPhone HotSpot. Here it is, and the error has been resolved.

This may be strange for some techies, but to no avail.