How to fix git error: RPC failed; curl 56 GnuTLS

Question

I use Ubuntu 16.04. When I want to git push origin master I get:

error: RPC failed; curl 56 GnuTLS recv error (-12): A TLS fatal alert has been received.
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I don't know what happened, but I set the output to be more verbose, and somehow it worked. `export GIT_TRACE_PACKET=1; export GIT_TRACE=1; export GIT_CURL_VERBOSE=1` It probably has nothing to do with it, but it may be helpful to look in the verbose output so you can pinpoint the issue. — dayuloli, Aug 24 '16 at 09:57
similar issue. error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull — Killer, Sep 12 '17 at 05:11
please refer to this link, he's the hero. https://stackoverflow.com/a/52530617/794765 — Robert, May 05 '21 at 08:10

score 66 · Answer 1 · answered Sep 12 '17 at 08:14

The accepted answer from @harlequin might work, but I spend 2 hours and could not build git package from source code.

However, Check the below link as this works for me.

The remote end hung up unexpectedly while git cloning

just update the http post buffer value

git config --global http.postBuffer 1048576000

score 28 · Accepted Answer · edited Jun 30 '17 at 10:54

28

To solve this issue:

Rebuilding git with openssl instead of gnutls fixed my problem.

I followed these instructions

edited Jun 30 '17 at 10:54

Sachith Muhandiram

2,301
7
30
55

answered Nov 07 '16 at 12:34

Harlequin

537
5
8

6

the whole process may take ~ 1hour – XoXo Jan 26 '17 at 01:13
3

On Ubuntu 16.04 took around 10mins! For step 7, after removing the line "TEST=test" in debian/rules, I also changed NO_OPENSSL=0 in the OPTS and in step 8, added "-uc -us" for not signing the package. – Ehsan M. Kermani Nov 21 '17 at 23:36
I have the same error when performing `git clone`, and this solution saved me! – skyuuka Sep 08 '18 at 00:51
I get `error: RPC failed; curl 18 transfer closed with outstanding read data remaining` as one of the people commenting at the end of the article you linked. I confirm that removing tests spare a lot of time, while -uc -us was needed to make a custom package. However, I haven't tried NO_OPENSSL=0 yet... For now I'm satisfied with my workaround (posted as answer). – hsandt Jan 31 '19 at 22:38
do you have any short-solution for Ubuntu-18? or this above will work? – GD- Ganesh Deshmukh Apr 10 '20 at 14:36
I followed this shell script and worked for me: https://gist.github.com/pescobar/6ae5634f92d75d23c36a – Mahmoud Bahnasy Sep 15 '20 at 20:50

score 28 · Answer 3 · answered Nov 05 '18 at 02:44

28

After reading your posts, I solved it simply by

apt install gnutls-bin

answered Nov 05 '18 at 02:44

陈家胜

510
5
6

I got the same issue with same solution (installing gnutls-bin) on debian 9.11 stretch. – Honza Nov 01 '19 at 20:32
1

This doesn't fix the problem for me – robertspierre Mar 06 '21 at 10:15

hsandt · Answer 4 · 2019-07-24T19:22:21.520

21

I have a workaround if you need to clone or pull and the problem lies in the size of the repository history. It may also help when you want to push later, with no guarantee.

Simply retrieve the last commits with --depth=[number of last commits].

You can do this at clone time, or, if working from a local repository to which you added a remote, at pull time. For instance, to only retrieve the last commit (of each branch):

git clone repo --depth=1
# or
git pull --depth=1

UPDATE: if the remote is getting too much ahead of you, the issue may come back later as you try to pull the last changes, but there are too many and the connection closes with curl 56. You may have to git pull --depth=[number of commits ahead on remote], which is tedious if you're working on a very active repository.

edited Jul 24 '19 at 19:22

answered Jan 31 '19 at 22:48

hsandt

590
5
11

1

For those for which this workaround worked: maybe your Internet connection doesn't support long TLS connections for some reason. I changed provider / increased bandwidth and I don't need the workaround anymore (see https://stackoverflow.com/a/59426260/3256073) – hsandt Dec 20 '19 at 13:48
when I put `--depth=1`, the error will not come. But I need all the commits. What to do? – Gokulakannan T Jan 21 '20 at 13:09
You can try to pull incrementally higher and higher depth... Not sure if that will avoid having too long connections. If the issue comes from your connection, you can also clone the repo from a different place, put it on a USB key, bring it home, copy it back on your computer. And from here, make sure to regularly pull so you don't have to download too much at once... (yes, I really did that before I could change provider, and it worked) – hsandt Jan 21 '20 at 21:52
This solved my issue when cloning large git repos (specifically bootstrap and Font-Awesome) from within WSL2. Thanks. – Inyoka Oct 30 '20 at 09:02

score 12 · Answer 5 · edited Mar 24 '18 at 17:17

12

You can set some option to resolve the issue

Either at global level: (needed if you clone, don't forget to reset after)

$ git config --global http.sslVerify false
$ git config --global http.postBuffer 1048576000

or on a local repository

$ git config http.sslVerify false
$ git config http.postBuffer 1048576000

edited Mar 24 '18 at 17:17

wargre

4,042
1
16
31

answered Sep 19 '17 at 13:46

Ramesh Kotkar

629
9
10

5

turning off `sslVerify` doesn't sound secure? – jmunsch Nov 21 '19 at 00:56

score 6 · Answer 6 · answered May 03 '17 at 11:40

6

I also encountered same and restart of the system resolved it :)

answered May 03 '17 at 11:40

RootCode

531
7
12

1

what do you mean? A simple reboot? – KansaiRobot Oct 27 '20 at 05:30
@KansaiRobot I assume you have this sorted by now. However, for anyone else wondering the same, yes, a simple reboot of my local machine resolved this issue for me. – Andrew Hardiman Jan 06 '21 at 11:40

user218867 · Answer 7 · 2018-03-29T08:40:51.033

5

I am also using Ubuntu based system (Mint mate 18), got the similar issue when clone large repo from github.

The simple solution worked for me is to use ssh protocol instead of http(s) protocol.

e.g

git clone git@github.com:xxx/yyy.git

edited Mar 29 '18 at 08:40

answered Mar 20 '18 at 00:22

user218867

16,252
12
112
156

score 4 · Answer 8 · answered Dec 05 '19 at 10:37

4

WSL2 users getting this with Ubuntu 18, read this. Basically you need to update your wireless driver.

answered Dec 05 '19 at 10:37

SM79

1,115
1
13
30

score 3 · Answer 9 · answered Jul 28 '18 at 03:16

3

Try to upgrading openssl modules

I solved it by doing that

sudo apt install openssl

answered Jul 28 '18 at 03:16

Adithya Visnu

43
5

score 2 · Answer 10 · answered Sep 28 '18 at 19:15

2

I faced this issue on Ubuntu 18.04 when cloning CppCheck using https.

A workaround to it was to use http instead.

answered Sep 28 '18 at 19:15

Bruno Alexandre Rosa

368
3
14

score 2 · Answer 11 · answered Nov 02 '18 at 05:58

2

All I did was disconnect and reconnect my pc from the wifi and it worked. Sometimes the answer might be very simple. Mine works now

answered Nov 02 '18 at 05:58

tushortz

1,972
1
14
25

score 2 · Answer 12 · answered Oct 09 '20 at 16:00

2

I solved this problem by disconnecting my VPN (My OS is ubuntu-16.04).

answered Oct 09 '20 at 16:00

M.Namjo

298
1
10

score 1 · Answer 13 · answered Apr 30 '19 at 07:12

1

Check your Network is properly working...this problem also occures because of internet issues

answered Apr 30 '19 at 07:12

score 1 · Answer 14 · answered Aug 13 '19 at 08:52

1

I just managed to solve this by cloning using SSH.

To do that I had to add my machine's SSH key to my account.

answered Aug 13 '19 at 08:52

Leo Tavares

307
3
6

chenlola · Answer 15 · 2019-08-21T16:34:24.017

1

Additionally,this error may occurs in you are using any proxy in command line.

if you export any proxy before , unset it .

$ unset all_proxy && unset ALL_PROXY

edited Aug 21 '19 at 16:34

answered Aug 21 '19 at 16:27

chenlola

51
4

score 0 · Answer 16 · edited Jun 20 '20 at 09:12

0

Another way here：please try it again, sometimes it happen just result from your network status.

My situation is as below.

edited Jun 20 '20 at 09:12

Community

1
1

answered Jun 13 '18 at 15:56

Chase07

411
3
10

score 0 · Answer 17 · answered Oct 10 '19 at 01:39

0

Try to disable your IPV6 for that and disable after. I think this is your problem.

answered Oct 10 '19 at 01:39

Thiago Lúcio

39
4

score 0 · Answer 18 · answered Mar 03 '20 at 12:55

0

I tried all the above without success. Eventually I realised I had a weak WiFi connection and therefore slow download speed. I connected my device VIA Ethernet and that solved my problem straight away.

answered Mar 03 '20 at 12:55

Josh

1,132
15
20

score 0 · Answer 19 · answered Jun 09 '20 at 14:31

I got this error while i tried to push a new branch upstream

git push --set-upstream origin xyz

I tried almost all of the git config edits suggested above including a system reboot. Nothing worked.

So I went back to master and did a pull, went back to my xyz branch, did a merge with master and was able to push.

* currently on branch xyz
git checkout master
git pull
git checkout xyz
git merge master
git push --set-upstream origin xyz

I have to say nothing in master conflicted with any of my changes in my new branch "xyx". Only a couple of new commits from master were merged to my "xyz" branch. This shouldn't have been a problem on normal days.

score 0 · Answer 20 · answered Sep 21 '20 at 07:28

0

I met the same question, and solved it by using SSH protocol.

git clone git@github.com:micro/micro.git

answered Sep 21 '20 at 07:28

simple

1

score 0 · Answer 21 · answered Oct 25 '20 at 15:57

Had the same problem hosting Go Git Server behind nginx and cloning:

remote: Enumerating objects: 103, done. remote: Counting objects: 100% (103/103), done. remote: Compressing objects: 100% (47/47), done. remote: Total 103 (delta 52), reused 99 (delta 51), pack-reused 0 Receiving objects: 100% (103/103), 11.56 KiB | 1.16 MiB/s, done. Resolving deltas: 100% (52/52), done. error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.

After searching RPC based issues, there appears to he a requirement to use HTTP2

Therefore this line in my nginx site configuration:

listen 443 ssl; # managed by Certbot

Was changed to this, to enable http2 - which is not a default:

listen 443 ssl http2; # managed by Certbot

And TLS in general seems happier (i.e. I had other errors regarding curl and TLS, when inspecting verbose output)

I have verified this as a root cause by removing http2, which reproduces the error and reinstating http2 resolves the problem.

score 0 · Answer 22 · answered Nov 28 '20 at 16:06

I had a similar fault:

error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.

when trying to clone a repository from Github.

After trying most of the solutions posted here, none of which worked, it turned out to be the parental controls on our home network. Turning these parental controls off solved the problem.

score 0 · Answer 23 · answered Dec 01 '20 at 13:25

0

I saw similar issues (particularly with depth) on some legacy projects when we were cloning that used to live on TFS. Enabling long paths resolved our issue and may be something else worth trying.

git config --system core.longpaths true

answered Dec 01 '20 at 13:25

James Jones

1

score 0 · Answer 24 · answered Feb 17 '21 at 04:21

For Linux: Simple you can run below commands:

1) git config -l
2) git config --global http.postBuffer 524288000
        Or set double value  1048576000
3) git config --global https.postBuffer 
4) git config --global core.compression -1 
5) service apache2 restart

Then again check the config of git

git config -l

now you can run clone command

git clone yourrepo

I hope this will be solved the issue.

score -1 · Answer 25 · answered Oct 14 '20 at 10:22

-1

My mac was connected to a 2.5GHZ network, I had to enable my wifi to 5GHz. And the problem disappeared.

answered Oct 14 '20 at 10:22

Siddharth

8,842
13
79
133

score -5 · Answer 26 · edited Sep 06 '18 at 07:13

-5

Simply executing command

git init

before cloning resolved it for me.

edited Sep 06 '18 at 07:13

Pang

8,605
144
77
113

answered Sep 06 '18 at 06:21

Rayies Banka

26
2

score -7 · Answer 27 · edited Sep 06 '18 at 07:13

-7

Reinstalling git will solve the problem.

sudo apt-get remove git
sudo apt-get update
sudo apt-get install git

edited Sep 06 '18 at 07:13

Pang

8,605
144
77
113

answered Jun 13 '18 at 03:17

Zhui Wang

19
1

How to fix git error: RPC failed; curl 56 GnuTLS

27 Answers27

Linked

Related