Git 推送错误：RPC 失败：curl 52

Question

git push fails with following error

fatal: RPC failed: curl 52: Empty reply from server

The upload succeeds in case only one file was modified, added or deleted.

The following settings to don't work reliably

 git config --global --add core.compression -1

The git version is 2.8.2 running on ubuntu 14.04, and I have tried with both openssl and gnutls compilations.

ssh remotes also fail.

The problem is encountered with repositories of

bitbucket
github
gitlab

Fail safe answers appreciated

Answer 1

In terminal use sudo to clone, or type:

git config --global http.postBuffer 157286400

its worked for me

Answer 2

Following worked for me.

git config --global core.compression 0

git clone --depth 1 <repo> //  partial clone to truncate the amount of info coming down

#cd repo // go into the new directory and 

git fetch --unshallow //retrieve the rest of the clone

git pull --all //final pull

Hope, this could be helpful for someone having the same issue.

Answer 3

I had a chat with Gideon @ atlassian he suggested to use SSH over HTTPS to fix the "curl 52" error.

For me switching to SSH fixed the problem. Here's the complete answer:

This is a HTTP/HTTPS timeout issue involving either some large commit size, or a weak network. If you're cloning, can you try to see if you can clone the repository using this method:

https://stackoverflow.com/a/22317479

Can you try to see if running this command before any git operations help as well:

git config --global http.postBuffer 524288000

Also, this issue usually won't occur in SSH; so maybe it is worth trying to set up SSH and then do the operation through SSH:

https://confluence.atlassian.com/bitbucket/set-up-ssh-for-git-728138079.html

Answer 4

Following worked for me. stop WIFI and use the Network cable to connect the NetWork

Maybe it is a problem about network

Answer 5

I have the same problem on arch linux, git version 2.8.2, can't push to bitbucket repo. Cloning and pull works.

Answer 6

Appearently it's a problem with HTTPS problem. Switching to SSH fix the problem with all repositories.

Answer 7

This happened in my case during a push and it was seemingly due to duplicate consecutive commit messages. Once I amended (git commit --amend) the second message to be slightly different from the first, pushed again, and success.