git clone error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054

I had the same problem, and @ingyhere 's answer solved my problem .
follow his instructions told in his answer here.

git config --global core.compression 0
git clone --depth 1 <repo_URI>
# cd to your newly created directory
git fetch --unshallow 
git pull --all

you need to increase the buffer size (it's due to the large repository size), so you have to increase it

git config http.postBuffer 524288000

Althought you must have an initializd repository, just porceed as the following

git init
git config http.postBuffer 524288000
git remote add origin <REPO URL>
git pull origin master
...

git config --global http.postBuffer 524288000

Work in my case - AWS code commit

This happens when you push first time without net connection or poor net connection.But when you try again using good connection 2,3 times problem will be solved.

(based on anser from Hakan Fıstık)

You can also set the postBuffer globally, which might be necessary, if you haven't checkout out the repository yet!

git config http.postBuffer 524288000

Uninstalling(version: 2.19.2) and installing(version: 2.21.0) git client fixed the issue for me.

just Disable the Firewall and start again. it worked for me

All these tips did not work for me, what worked was cloning over ssh rather than http

Following steps helped me to fix this issue, Solution 1:

1. git checkout master
2. git pull
3. git checkout [you current branch]
4. git pull

You can also set git config http.postBuffer 524288000 to increase the network buffer

Solution 2:

Sometimes it happens when you are cloning your repo using VPN and it fails to verify the SSL

Try this out it may help:

git config http.sslVerify "false"

I had the same issue and found out the problem was with my internet speed, after getting on a better connection the problem was solved solved.

Before cloning just run "git init". It will create local .git and it will allow for clone.

It's mentioned as SSL_ERROR_SYSCALL, errno 10054.

To resolve this SSL issue I went to .gitconfig file (which is located in c drive in my desktop) I changed sslverify to false and added my username and email id.

sslVerify = `false` //make sslVerify as false    
[user]
    name = `***<Enter your name>**`
    email = `**<Email Id>**`

I had the exact same problem while trying to setup a Gitlab pipeline executed by a Docker runner installed on a Raspberry Pi 4

Using nload to follow bandwidth usage within Docker runner container while pipeline was cloning the repo i saw the network usage dropped down to a few bytes per seconds..

After a some deeper investigations i figured out that the Raspberry temperature was too high and the network card start to dysfunction above 50° Celsius.

Adding a fan to my Raspberry solved the issue.

It could be an issue with your network (i.e. not an issue with any of your git configs, firewall, or any other machine settings). To confirm this, you could test the following:

1. See if this issue persists on the same network on different machines (this was true for me).
2. Try running the problematic git command (for me it was git pull) on a different network and see if it works. I brought my desktop over to a friend's and confirmed that the command did indeed work without any modifications. I also tested the command from my laptop on an open network nearby and the command also started suddenly working (so this was also true for me)

If you can confirm #1 and #2 above, it may be time to schedule an appointment with a technician from your ISP. I have fiber internet in a fairly newish building and when the technician arrived they went to my building's telecom room and switched my internet port. That somehow seemed to fix the issue. He also let me know that there were other issues at large going on in my building (so it could have nothing to do with your machine or things in your control!).

If that fails, maybe consider switching internet providers if that's an option for you. Else, just keep calling your ISP to send in more and more senior technicians until it gets resolved.

I'm hoping nobody actually has to resort to what I did to find the problem.

tl;dr: Give your ISP a call as the issue could be one with your network.

If you have VPN opened, close and try it again.

What I did is moved the dependencies list to the end of

#Pods for <app>

In Podfile. Like this:

    # Uncomment the next line to define a global platform for your project
    # platform :ios, '9.0'

    target '<app>' do
    # Comment the next line if you don't want to use dynamic frameworks
    use_frameworks!

  # Pods for <app>

  target '<app>Tests' do
    inherit! :search_paths
    # Pods for testing
  end

  target '<app>UITests' do
    inherit! :search_paths
    # Pods for testing
  end

    pod 'Firebase/Core'
    pod 'Firebase/Database'

end

In my case, its something wrong with my DNS server, after i add a new github.com record in the hosts, the problem solved.

13.114.40.48 github.com

1. Go to https://gitforwindows.org

2. Download

3. Install (no need to uninstall)

4. That's it! No more error: RPC failed; curl 56 OpenSSL SSL_read: No error

I too have faced this issue today. I have tried all the options shared in this thread but I was still having the issue.

I tried cloning after connecting to my corporate VPN and cloning got completed successfully. So, guys it might have to do with your local firewall policy. Factor in that as well :)

This is what works for me.

git config --global http.sslVerify "false"

For me, git config --global http.postBuffer 524288000 alone did not fix it, I had to run git config --global core.compression 0 as well.

this issue is resolved by cloning using SSH key. first of all set the ssh key and then add it to your git/github account. and then try to clone using ssh instead of using http. in my case this solved my problem. i tried all the other solution including increasing the buffer size, changing the git version, etc. none of these solution works in my case.

For me the issue was with my wifi extender. When I connect directly to my wifi without using extender, it started working.