Git push error :RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053. internet connection is ok, tried increasing buffer size

Question

Enumerating objects: 282, done.
Counting objects: 100% (282/282), done.
Delta compression using up to 4 threads
Compressing objects: 100% (231/231), done.
Writing objects: 100% (282/282), 33.54 MiB | 126.73 MiB/s, done.
Total 282 (delta 52), reused 263 (delta 44)
error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

I have already tried the git config buffer increment command and lfs. Also, my internet connection is good git is working fine in other long projects. the problem is only in this project, I have tried deleting the old repo and making a new one but fails. project size is 85MB and it's a small front-end page, I am using githubpages for this project for serving live, but now this error .. Please give me the solution for this.

Answer 1

I had the same problem I tried increasing the buffer size for both http as well as https but it did not work what I finally did was

git push --force

this worked.

Answer 2

This error means that your operating system returned an error code, in this case, Windows socket error 10053. The description of that error message is this:

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

That means that you could be experiencing a timeout or other network problem. Since you're on Windows, these are often caused by third-party antivirus and firewall programs, which are a common source of Git problems there, as well as network proxies or monitoring software. You can try completely uninstalling any of these pieces of software and restarting, which may fix the problem, or if you have a network proxy, try running from a different network without it.

You could also try using WSL 2, which often bypasses the standard Windows networking and may avoid a lot of these problems.

Otherwise, this is probably just a garden variety network issue which requires standard troubleshooting steps. What will not help is increasing http.postBuffer, as you suggested you'd done, because that only works if you have a known broken HTTP setup.