Git push fails with RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054

Hi Everyone,

Git push fails every time with the output below, it appears to be timing out This issue has come up before with this repository and I tried a number of suggestions such as increasing the buffer size. I ended up creating a new repository and pushing to it. I don’t want to keep creating new repositories so any help would be much appreciated. I have the latest git installed. My local repo is about 400MB with no file over 10MB.

Enumerating objects: 177, done.
Counting objects: 100% (177/177), done.
Delta compression using up to 2 threads
Compressing objects: 100% (143/143), done.
Writing objects: 100% (151/151), 48.96 MiB | 3.99 MiB/s, done.
Total 151 (delta 59), reused 0 (delta 0), pack-reused 0
POST git-receive-pack (51336851 bytes)
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

Thanks,
David

Hi @DavidLong65 :wave:

This error usually occurs when one reaches the maximum size limit of 2GB for a single push on GitHub.com.

I’m afraid it isn’t possible to push more than 2GB of content at a time to GitHub.com. More details about our size limits can be found here:

We have some recommendations on how to configure Git Large File Storage here:

If the problem is that there are no large files, it’s just that the whole project is large, then I would recommend breaking the git push operations up into a few pushes so that you can upload the project piece by piece. The first answer in this Stack Overflow article describes how best to do this:

Hi and thanks for the reply. The push was only a relatively small one and the total project size is certainly well below 2gb. For now, I’ve moved the project to GitLab and I no longer have push issues. I’ll look into it again when I have more time.
Thanks,
David.

1 Like