Git push error: RPC failed; result=56, HTTP code = 200 fatal: The remote end hung up unexpectedly fatal

Question

While doing git push, I receive this error:

Username for 'https://github.com': Newbie
Password for 'https://Newbie@github.com':
Counting objects: 11507, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8210/8210), done.
Writing objects: 100% (11506/11506), 21.75 MiB | 0 bytes/s, done.
Total 11506 (delta 2213), reused 11504 (delta 2211)
efrror: RPC failed; result=56, HTTP code = 200
atal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I also tried doing: git config http.postBuffer 524288000, but still error.. Also tried: git config --global http.postBuffer 2M by referring on git push error: RPC failed; result=56, HTTP code = 0

Please can anyone help me out with this?

Answer 1

Look here: https://flyingtomoon.com/2011/04/12/git-push-is-failed-due-to-rpc-failure-result56/

The problem is most likely because your git buffer is too low.

You will need to increase Git’s HTTP buffer by setting the git config var “http.postBuffer” to 524288000.

git config http.postBuffer 524288000

Answer 2

Increase the Git buffer size to the largest individual file size of your repo:

git config --global http.postBuffer 157286400

Answer 3

This error was caused by my corporate Firewall.

Answer 4

I faced a similar issue. When I was trying to push my branch to remote, I was seeing this error: >error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54

In my case, this issue was caused due to a proxy that I was connected to. I disconnected the VPN connection and tried to push my changes again and that worked.

Answer 5

Try re-initializing your git repository: git init

Answer 6

Try building git using openssl libraries. Refer to this post. You may have to compile git in Windows. I hope that helps.

Answer 7

I was running into a very similar issue, though I was deploying to an Azure Web App via a git push. I received this error:

RPC failed; curl 56 SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054
The remote end hung up unexpectedly

The solution for me was to change my deployment environment from a Macbook to a Windows desktop. See this answer for full details.