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

K

12

55

While doing git push, I receive this error:

Username for 'https://github.com': Newbie
Password for 'https://[email protected]':
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?

Kepler answered 25/7, 2014 at 9:42 Comment(2)

I'm having the exact same error. By using the GIT_CURL_VERBOSE=1 I got the following extra details: SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054 – Bellona 2/12, 2014 at 9:26

@Kepler ,have you solved the above problem,I am also facing same error. – Monogenesis 25/7, 2016 at 6:47

E

106

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

Euridice answered 25/4, 2016 at 14:19 Comment(6)

This worked fantastically! After this issue was resolved, we ran into a different one (we're using Bonovo Git Server). It was resolved changing what's stated in this other answer. So, odds are some of you may have the same issue, so I thought of posting it here. – Typeset 4/5, 2016 at 14:54

I had a similar problem on Windows 7. After hours of googling, comming accross this post and doubling the buffer size, I discovered it was my antivirus software that was causing the issue – Hispania 15/2, 2017 at 23:37

Showing not in a Git Directory, what to do? – Begotten 20/7, 2017 at 5:47

@ManabKumarMal add the global tag to the git command git config --global http.postBuffer 524288000 – Dubenko 6/11, 2018 at 14:38

This worked :-) Note: navigate to the root folder of the GIT project that causes the above mentioned issue – Clactonian 4/11, 2020 at 7:37

I am MAC User and it works fine for me. git config http.postBuffer 524288000 – Grizelda 13/9, 2022 at 5:33

R

24

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

git config --global http.postBuffer 157286400

Riancho answered 27/8, 2018 at 6:11 Comment(1)

This was the complete answer. Increase your buffer size to maximum file size on your repo. Thanks mate :) – Canuck 29/3, 2020 at 16:28

C

12

This error was caused by my corporate Firewall.

Cerebellum answered 7/5, 2018 at 17:14 Comment(1)

This is quite frustrating though, not sure what I can do if the policy is there and not able to change. – Voltmeter 6/8, 2019 at 1:23

M

8

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.

Melodeemelodeon answered 20/8, 2018 at 3:45 Comment(2)

Refresh (Disconnect/Reconnect) your VPN. It worked for me. – Imogen 15/10, 2018 at 13:15

I disconnected my vpn. it worked. thanks – Nadianadine 16/11, 2022 at 11:1

U

6

Try re-initializing your git repository: git init

Unconformity answered 18/3, 2018 at 10:43 Comment(1)

This actually worked and I am curious, so i have questions...what triggered the error even though the repository was already initialized? In my case I was trying to push to a new repository. – Pydna 9/2, 2021 at 9:25

F

4

It will work after increasing Git’s HTTP buffer by setting the git config var http.postBuffer to 524288000.

git config http.postBuffer 524288000

Fultz answered 22/11, 2019 at 11:42 Comment(0)

J

4

Poor network connection was the issue for me. Check your internet strength.

Jedlicka answered 21/6, 2020 at 12:56 Comment(0)

R

3

This happened to me when I was cloning a git repo that was taking a long time. I went to do something else and my computer went to sleep, terminating the connection. Turning off auto sleep on my computer worked for me.

Ricercar answered 9/12, 2019 at 20:10 Comment(0)

S

1

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.

Sheff answered 2/9, 2016 at 13:55 Comment(1)

Hmm...someone care to tell me why you just down voted this answer? Just curious. – Sheff 6/12, 2019 at 21:32

V

0

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

Victorie answered 7/8, 2014 at 7:33 Comment(0)

M

0

You can try this, maybe this code is working

git config http.sslVersion tlsv1.2

Recommended topics

Hot tags