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

90,803

Solution 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

Solution 2

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

git config --global http.postBuffer 157286400

Solution 3

This error was caused by my corporate Firewall.

Solution 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.

Solution 5

Try re-initializing your git repository: git init

Share:
90,803
Newbie
Author by

Newbie

Updated on July 14, 2022

Comments

  • Newbie
    Newbie almost 2 years

    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?

  • tfrascaroli
    tfrascaroli about 8 years
    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
    user28864 about 7 years
    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
    Manab Kumar Mal almost 7 years
    Showing not in a Git Directory, what to do?
  • Victor R. Oliveira
    Victor R. Oliveira over 5 years
    Refresh (Disconnect/Reconnect) your VPN. It worked for me.
  • Admin
    Admin over 5 years
    @ManabKumarMal add the global tag to the git command git config --global http.postBuffer 524288000
  • Shawn
    Shawn almost 5 years
    This is quite frustrating though, not sure what I can do if the policy is there and not able to change.
  • Tod Birdsall
    Tod Birdsall over 4 years
    Hmm...someone care to tell me why you just down voted this answer? Just curious.
  • Ankit Kumar Gupta
    Ankit Kumar Gupta about 4 years
    This was the complete answer. Increase your buffer size to maximum file size on your repo. Thanks mate :)
  • Roy Wasse
    Roy Wasse over 3 years
    This worked :-) Note: navigate to the root folder of the GIT project that causes the above mentioned issue
  • Mena
    Mena about 3 years
    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.