Git push error: RPC failed: 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

This problem appears to have many causes, including the server going down or using an old version of Git. — Tim Biegeleisen
– Tim Biegeleisen, Commented May 7, 2016 at 6:28
<status.bitbucket.org/> says 'via https' is operational, and 2.8.2 is latest available stable git version — sulimo
– sulimo, Commented May 7, 2016 at 6:31
Same here and it looks like it's doing it only on certain repos, I have 6 repos on bitbucket it's only doing it on one of them. Everything up to date. Support ticket sent but still not heard back. — Dado
– Dado, Commented May 8, 2016 at 23:45

Learn Swift · Accepted Answer · 2016-09-09 15:01:51Z

17

In terminal use sudo to clone, or type:

git config --global http.postBuffer 157286400

its worked for me

edited Sep 9, 2016 at 15:01

Learn Swift

5805 silver badges15 bronze badges

answered Sep 8, 2016 at 14:17

Eduardo Oliveros

8669 silver badges21 bronze badges

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

4 Comments

razzed Over a year ago

Worked for me as well on Mac OS X on repo on BitBucket

Bobby_Cheh Over a year ago

using sudo to clone did not fix this for me

Papooch Over a year ago

This worked for me also. Any idea what makes it happen and why this fix works?

8ctopus Jan 29 at 6:21

This guy explains it stackoverflow.com/a/79013573/10126479

f-society · Accepted Answer · 2016-12-01 18:33:31Z

16

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.

answered Dec 1, 2016 at 18:33

f-society

3,0281 gold badge29 silver badges18 bronze badges

3 Comments

Yi Xin Over a year ago

YOU SAVED MY REPOS!

Kiran Kumar Kotari Over a year ago

git config --global core.compression 0 solved saved my repo.

Dmitry Orlov Over a year ago

Looks like it helps when remote hungs up due to something blocking too big requests. Thank you!

Community · Accepted Answer · 2020-06-20 09:12:55Z

7

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

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered May 9, 2016 at 14:52

Dado

1,2071 gold badge15 silver badges31 bronze badges

1 Comment

Zing Lee Over a year ago

Thanks, it works. I found the way to switch to SSH at: help.github.com/articles/changing-a-remote-s-url/…

user8415640 · Accepted Answer · 2017-08-04 06:27:24Z

1

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

Maybe it is a problem about network

answered Aug 4, 2017 at 6:27

user8415640

211 bronze badge

1 Comment

Anuar Maratkhan Over a year ago

I had the same issue. Your statement about the problem with the network was right. But I had vice-versa: I stopped LAN connection and started Wi-Fi, it resolved the issue. Many thanks!

Usern4me · Accepted Answer · 2016-05-08 19:04:11Z

0

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

answered May 8, 2016 at 19:04

Usern4me

1272 bronze badges

2 Comments

Usern4me Over a year ago

@Dado: Sorry for commenting here, I can't comment your answer yet. I tried earlier with changing postBuffer size, but it didn't work, I have a good internet connection and, and I modified only 4 not too big files (few hundred lines c++ code ~50 lines changed all in all). I nevertheless tried ssh, but it also fails with: fatal: The remote end hung up unexpectedly

Dado Over a year ago

Interesting I had problems pulling instead ;) Try to open a ticket with them they are quite good with customer service. (the only thing I can think of is just make sure that you aren't accidentally still using HTTPS)

Fares Benhamouda · Accepted Answer · 2016-12-30 08:37:42Z

0

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

answered Dec 30, 2016 at 8:37

Fares Benhamouda

61910 silver badges22 bronze badges

Comments

programmer1983 · Accepted Answer · 2020-09-10 17:07:49Z

0

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.

answered Sep 10, 2020 at 17:07

programmer1983

355 bronze badges

Comments

user2173353 · Accepted Answer · 2024-01-03 09:24:31Z

I had the same problem but for pull and fetch. Fetching or pulling from anywhere (Visual Studio, command line, etc) was failing with this error. Re-cloning the repository using the "Git GUI" for Windows was failing with the same error too.

For whatever reason, re-cloning the repository from the command line worked (either due to luck or due to some different git version being used between the two?) and I got a new working local repository.

I have fetched/pulled from the new local repository to the old (using the first method mentioned here), in order to minimize the things the old repo had to pull from the remote in order to get in sync, but it was still failing after the update. So, this appeared to be something with the repository, not with HTTP for me...

I could not try with SSH to see if there was any difference.

Yaween De Silva · Accepted Answer · 2024-09-23 07:25:47Z

0

The cause for the push failure can be either the size of the buffer that Git uses when pushing data is lower than expected or your network issues.

First check your current buffer size by running the following command.

git config --get http.postBuffer

If its too low try increasing it to a higher level by running the following command.

git config --global http.postBuffer 524288000

If none of the options listed above delivered the desired result, try pushing your work with a different internet connection, preferably a private one, as occasionally a public connection can also impact this.

answered Sep 23, 2024 at 7:25

Yaween De Silva

1

Collectives™ on Stack Overflow

Git push error: RPC failed: curl 52

9 Answers 9

4 Comments

3 Comments

1 Comment

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

9 Answers 9

4 Comments

3 Comments

1 Comment

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related