error: RPC failed; curl 56 Failure when receiving data from the peer

[agnibi]

The problem

I'm trying to clone a repository with URL from Azure Git Hub.

After some time I got error:

Cloning into 'C:\Github\HMDP'...
remote: Azure Repos
remote: Found 172304 objects to send. (2057 ms)
Receiving objects: 100% (172304/172304), 13.17 GiB | 7.79 MiB/s, done.
error: RPC failed; curl 56 Failure when receiving data from the peer
Resolving deltas: 100% (51828/51828), done.

Release version

3.0.8 (x64)

Operating system

Windows 10

Steps to reproduce the behavior

No response

Log files

stderr:
Cloning into 'C:\Github\abcde'...
remote: Azure Repos
remote:
remote: Found 172304 objects to send. (2057 ms)
Receiving objects: 0% (1/172304)
Receiving objects: 1% (1724/172304)
Receiving objects: 2% (3447/172304)
Receiving objects: 3% (5170/172304)
Receiving objects: 4% (6893/172304)
Receiving objects: 5% (8616/172304)
Receiving objects: 6% (10339/172304)
Receiving objects: 7% (12062/172304)
Receiving objects: 8% (13785/172304)
Receiving objects: 9% (15508/172304)
Receiving objects: 10% (17231/172304)
Receiving objects: 11% (18954/172304)
Receiving objects: 12% (20677/172304)
Receiving objects: 13% (22400/172304)
Receiving objects: 14% (24123/172304)
Receiving objects: 15% (25846/172304)
Receiving objects: 16% (27569/172304)
Receiving objects: 17% (29292/172304)
Receiving objects: 18% (31015/172304), 8.00 MiB | 15.31 MiB/s
Receiving objects: 19% (32738/172304), 8.00 MiB | 15.31 MiB/s
...
...
...
Receiving objects: 100% (172304/172304), 13.17 GiB | 8.02 MiB/s
Receiving objects: 100% (172304/172304), 13.17 GiB | 7.79 MiB/s, done.
error: RPC failed; curl 56 Failure when receiving data from the peer

Screenshots

No response

Additional context

No response

[sergiou87]

Hello @agnibi !

We've seen this issue in the past when users have some kind of antivirus, firewall or proxy installed. If so, trying to disable or properly configure them usually gets things working. We've also seen this when users have unstable internet connection.

Please, let us know if that's your case!

[agnibi]

Hi,

thanks for quick reply.

As this is my company PC, there is antivirus running and PC is behind a firewall. I cannot change that.

I'm not using a proxy and my internet connection is stable.

Receiving objects is 100% and the issue happens afterwards. Any ideas what I could do to get it running?

[sergiou87]

Only things I can think are:

1. Trying to clone from command line to see if you get the same error (my bet is you will)
2. Ask a coworker to clone it to see if it works on a different company machine.

That will get us some more data points 🤞

[bjlay2000]

Hi, I am actually having the same error. I am testing out tools for non technical users. Using Sourcetree and also command line both work without issues.

I am cloning from an Azure DevOps url using PAT.

Command Line

This seems to be the error when there is a network issue:

[bjlay2000]

A little more info. We are using Zscaler and I was able to have our security guys disable the tool while I tested the clone process. It worked successfully. So the issue is definitely with an antivirus software but there is room for improving GitHub Desktop. As I said earlier, Sourcetree and some other tools work without disabling the AV software.

[agnibi]

It is not be possible to do anything without AV software in my company. I'm hoping for a solution in GitHub Desktop.

[steveward]

@agnibi unfortunately it's possible that your firewall/proxy is filtering traffic and causing this issue -- are you able to clone the repository from the command line? You could try performing the initial clone from the command line and then see if you are able to push changes via GitHub Desktop. That would help narrow down the issue.

[agnibi]

Hi,

good news: Cloning the repository with "git clone" on command line is working fine.

Thanks for help

[ParthMovaliya]

i have issue like this :

Cloning into 'D:\portfolio\node_modules.cache\gh-pages\https!github.com'...
error: RPC failed; curl 56 Recv failure: Connection was reset
error: 2325 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

now what i can do?
thanks in advance

[aloyziuz]

Disabling my antivirus works for me (i'm using Kaspersky Free)

[dsrink]

it seems that this is a compatibility issue on TLS layer, which is fixed in more recent curl versions (which git client relies on for the https/TLS part). For me, problem was solved by upgrading libcurl package to 8.3.0.