Unable to clone repository - error: RPC failed; curl 56 Failure when receiving data from the peer

[Gullapalli Rajith]

We are trying to clone a Bitbucket repo and we get this error. We tried in multiple systems inside and outside the network. We still get the same error message. We have tried the options of changing the sslBackend to openssl and schannel.

git config --global http.sslBackend openSSL
For openssl we get this error message "fatal: unable to access : SSL certificate problem: unable to get local issuer certificate".

git config --global http.sslBackend schannel
For schannel we get the Error message "error: RPC failed; curl 56 Failure when receiving data from the peer".

We have tried the below commands too. It didn't work.

git config --global core.compression 0

git clone --depth 1 <repo_URI>

git fetch --unshallow

Please let us know if they are any other way to get this issue resolved.

[Syahrul]

G'day, @Gullapalli Rajith 

Welcome to the community!

I believe this is caused by the latest git version 2.44.0, could you check if you are running this version of git using git --version?

If yes, could you try to downgrade your git version to 2.43.* or above and see if that works? 

Regards,
Syahrul

[Gullapalli Rajith]

Hi @Syahrul Thanks for the quick response. The GIT version I am using is 2.32.0.2. Let me know if I have to try to upgrade it to 2.43.* and then try again.

[Syahrul]

Hey @Gullapalli Rajith 

Can you try upgrading the Git version to see if that helps? If not, can you raise a support ticket with us at our Support portal to investigate the issue further.

Regards,
Syahrul

[Gullapalli Rajith]

Hi @Syahrul We will try with 2.43 and get back to you. Thank you.

[Gullapalli Rajith]

Hi @Syahrul we have tried the same. But we are receiving the same error again. Please suggest on how to overcome this issue.

[Syahrul]

Hey @Gullapalli Rajith 

At this point, I think this is more of your local environment issue. There could be an issue with the local firewall, antivirus, or any other security related within the environment itself that prevents the clone. 

I would suggest raising a support ticket with us in the support portal to continue the investigation.

Regards,
Syahrul