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

[Gbadebo Ogunleye]

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

This is for our VM sandbox environment with isolated network connection from the rest of the network. I can successfully clone/push/push from the rest of the network, but I am unable to clone from the sandbox area. I figure it has to be because this area is isolated, but I can't pin it down as to why I keep getting the error above. Checked firewalls, disabled antivirus all to no avail.

Appreciate any suggestions.

[Gbadebo Ogunleye · Accepted solution]

1) Run the command

git config --global http.sslBackend openssl

Afterwards, try cloning a Bitbucket Cloud repo again and see if it works.

[Gbadebo Ogunleye]

Thanks Thoedora.

[Theodora Boudale · Accepted solution]

Hi @Gbadebo Ogunleye,

I would like to ask if you could provide some additional details so we can better help you:

1) Are you using HTTPS or SSH to clone the repo?

2) Could you please try cloning with one of the following commands, which will provide verbose output, and post the full output here?

In case you are using HTTPS:

GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 <git command>

Please make sure to remove the line that starts with Authorization: from the output prior to sharing here, as it includes credential info. Please also sanitize any other private info, like workspace-id and repo name.

In case you are using SSH:

GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_SSH_COMMAND="ssh -vvv" <git command>

3) Does the issue occur with one specific repo only, or with multiple Bitbucket repos?

4) What version of Git do you have on this virtual machine? You can find that with the command git --version

Kind regards,
Theodora

[Gbadebo Ogunleye]

Hello Theodora and thanks for the response.

1. HTTPS

2. Please see attached. The folder appears at the start of the process and disappears mid way before the error (RPC failed; curl 56 failure........).

3. All repo when you try to clone from the sandbox environment

4. 2.39.0.windows.2

Thanks for the support.

[Gbadebo Ogunleye]

remote: Enumerating objects: 355, done.
remote: Counting objects: 100% (355/355), done.
remote: Compressing objects: 100% (335/335), done.
remote: Total 355 (delta 18), reused 355 (delta 18), pack-reused 0
Receiving objects: 100% (355/355), 2.49 MiB | 4.97 MiB/s
Receiving objects: 100% (355/355), 6.93 MiB | 7.63 MiB/s, done.
error: RPC failed; curl 56 Failure when receiving data from the peer
Resolving deltas: 100% (18/18), done.

[Theodora Boudale]

Hi @Gbadebo Ogunleye,

Thank you for the info. I suspect that the issue may be caused by a bug in the version of Git you are using that occurs with Bitbucket Cloud.

I found these two bug reports here:

• https://github.com/git-for-windows/git/issues/4194
• https://github.com/git-for-windows/git/issues/4202

Based on the feedback provided there, you can try the following:

1) Run the command

git config --global http.sslBackend openssl

Afterwards, try cloning a Bitbucket Cloud repo again and see if it works.

2) Alternatively, uninstall Git and then try installing it again using the latest snapshot from this page:

• https://wingit.blob.core.windows.net/files/index.html

It is mentioned in the comments that the bug was fixed 4 days ago and the latest snapshot should include the fix.

Kind regards,
Theodora

[Gbadebo Ogunleye]

Hello Theodora,

Thanks for the support. I was able to get it working with option 1. I tried like 3 different repositories and I was able to successfully clone without the curl 56 failure error.

Appreciate the support and enjoy the rest of the day.

[Theodora Boudale]

You are very welcome Gbadebo, it's good to hear that the issue is resolved.

Have a great day, and please feel free to reach out if you ever need anything else!

Kind regards,
Theodora

[rajputj3@bv.com]

I am still having this problem. I have installed git version 2.45.2.Windows.1.8

Please help me. It was working few hours ago.

[Theodora Boudale]

Hi rajputj3@bv.com,

Please create a new question in the community, and we can look into your issue. It's best to have a separate question if you need assistance, otherwise a post will become difficult to follow if we troubleshoot multiple users' issues with potentially different root causes.

Alternatively, you can create a ticket with the support team since you have access to a workspace on a paid billing plan. You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.

Kind regards,
Theodora