Git “efrror: RPC failed; result=55, HTTP code = 0” on push
I’ve spent all day on this one and could really use some help. When I try to push a relatively large commit,
Writing objects: 100% (21/21), 908.07 KiB | 0 bytes/s, done. Total 21 (delta 17), reused 0 (delta 0)
git takes a very long time to respond and then gives
- Rejected git push
- Link Heroku commits to Github?
- git - Your branch is ahead of 'origin/master' by 1 commit
- Can GITHub commits be pushed to a new branch? Or are they already committed to the original?
- How to push to a new branch in Git carefully
- Push a commit in two branches with Git
"efrror: RPC failed; result=55, HTTP code = 0 atal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date"
I have searched this error code, and the most likely solution seems to be extending the buffer size
git config http.postBuffer 524288000
I have tried this solution with no success. After VonC’s suggestion, I tried switching from http to ssh. From ssh, I get a long hang up at the same point. Eventually, the following error message appears
Read from remote host github.com: Connection reset by peer fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly
Could this be a router issue? I have tried pushing from a different computer on a different network and am able to do so successfully.
I am away from my Linux machine on a Windows host and using the terrible poshGit Windows PowerShell interface.
2 Solutions collect form web for “Git “efrror: RPC failed; result=55, HTTP code = 0” on push”
You can follow the debug advices from the BitBucket article:
Specifically, the ‘
This is the error code coming from libcurl, the underlying library used in http communications with Git. From the libcurl documentation, a result code of 55 means:
CURLE_SEND_ERROR (55) Failed sending network data.
This can be caused by a variety of network related issues or even the Bitbucket service itself. It essentially means that the connection was dropped unexpectedly. Things to check would be to attempt the push from a machine on a ‘clean’ network outside of any corporate firewalls or proxies. Check all proxy servers to ensure they are properly moving SSL data and are fully permitted to complete.
To help troubleshoot this issue, try running the push with the command
GIT_CURL_VERBOSE=1 git push
If after checking all connections and proxy configurations the connection still fails consistently, please report the information above to support. Then switch to SSH. We have a guide to getting it setup for Git at Set up SSH for Git. If you should run into any configuration issues while setting up SSH, please refer to our SSH Troubleshooting guide.
I experienced the issue due to a misconfiguration, where I pointed to a remote prefixed with http:// instead of https:// the answer hinted on SSL and this helped me to a solution for my issue.
So my remote configuration should be written:
$ git remote add origin https://github.com/jonasbn/perl-workflow.git
$ git remote add origin http://github.com/jonasbn/perl-workflow.git