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://[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?

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 — Yag
– Yag, Commented Dec 2, 2014 at 9:26
@Newbie ,have you solved the above problem,I am also facing same error. — Giresh
– Giresh, Commented Jul 25, 2016 at 6:47

James Shi · Accepted Answer · 2016-04-25 14:19:31Z

105

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

answered Apr 25, 2016 at 14:19

James Shi

2,0442 gold badges16 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

tfrascaroli Over a year ago

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.

user28864 Over a year ago

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

Manab Kumar Mal Over a year ago

Showing not in a Git Directory, what to do?

user2031111 Over a year ago

@ManabKumarMal add the global tag to the git command git config --global http.postBuffer 524288000

Roy Wasse Over a year ago

This worked :-) Note: navigate to the root folder of the GIT project that causes the above mentioned issue

|

Mateusz Piotrowski · Accepted Answer · 2018-09-19 10:36:47Z

26

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

git config --global http.postBuffer 157286400

edited Sep 19, 2018 at 10:36

Mateusz Piotrowski

9,38311 gold badges61 silver badges83 bronze badges

answered Aug 27, 2018 at 6:11

Vijay Chauhan

3874 silver badges7 bronze badges

1 Comment

Ankit Kumar Gupta Over a year ago

This was the complete answer. Increase your buffer size to maximum file size on your repo. Thanks mate :)

DBD · Accepted Answer · 2018-05-07 17:14:20Z

12

This error was caused by my corporate Firewall.

answered May 7, 2018 at 17:14

DBD

23.2k12 gold badges63 silver badges87 bronze badges

1 Comment

Shawn Over a year ago

This is quite frustrating though, not sure what I can do if the policy is there and not able to change.

GeekyDeveloper · Accepted Answer · 2018-08-20 03:45:08Z

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.

NIKHIL NAGRALE · Accepted Answer · 2018-03-18 10:43:08Z

6

Try re-initializing your git repository: git init

answered Mar 18, 2018 at 10:43

NIKHIL NAGRALE

871 silver badge4 bronze badges

1 Comment

Mena Over a year ago

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.

Farwa · Accepted Answer · 2020-06-21 12:56:23Z

5

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

answered Jun 21, 2020 at 12:56

Farwa

7,2149 gold badges36 silver badges50 bronze badges

Comments

S1LENT WARRIOR · Accepted Answer · 2020-06-25 04:03:43Z

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

git config http.postBuffer 524288000

Michael M. · Accepted Answer · 2019-12-09 20:10:41Z

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.

Community · Accepted Answer · 2017-05-23 11:54:28Z

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.

Hmm...someone care to tell me why you just down voted this answer? Just curious.

Community · Accepted Answer · 2017-05-23 12:25:52Z

0

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

edited May 23, 2017 at 12:25

CommunityBot

11 silver badge

answered Aug 7, 2014 at 7:33

Damian Nadales

5,0571 gold badge23 silver badges41 bronze badges

Comments

Jay varmora · Accepted Answer · 2021-01-02 18:02:36Z

0

You can try this, maybe this code is working

git config http.sslVersion tlsv1.2

answered Jan 2, 2021 at 18:02

Jay varmora

831 gold badge2 silver badges8 bronze badges

Comments

arjava · Accepted Answer · 2022-12-05 10:01:02Z

0

I tried updating curl to latest and it was awesome, it worked for me

answered Dec 5, 2022 at 10:01

arjava

1,9592 gold badges20 silver badges21 bronze badges

Comments

DigitalVoyager · Accepted Answer · 2024-11-26 07:04:24Z

Strange but the solution that worked for me is as I was using git bash to pull my repo and continuously faced the issue for 2 days. I did two thing as follows that worked for me.

1. Changed the network to office Wi-fi.

2. Switched from "git bash" to "CMD"(admin mode);

This worked for me.

Please try and check if this works for you too. First go with second method of using CMD as admin mode, if this doesn't works then try to change the wi-fi.

Collectives™ on Stack Overflow

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

13 Answers 13

6 Comments

1 Comment

1 Comment

1 Comment

1 Comment

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

13 Answers 13

6 Comments

1 Comment

1 Comment

1 Comment

1 Comment

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Linked

Related