Since a few days I got an issue with Mac OS High Sierra 10.13.3 :
When I run a
git clone like
git clone github.com/xxx.git failed
LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
Same issue with
npm i command
Even when I try to install brew like so:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
I also tried the alternative setup: same.
I had this similar error when using
wget ..., and after much unfruitful searching in the Internet, I discovered that it was happening when hostnames were being resolved to IPv6 addresses. I discovered this by comparing the outputs of
wget ... in two machines, one was resolving to IPv4 and it worked there, the other was resolving to IPv6 and it failed there.
So the solution in my case was to run
networksetup -setv6off Wi-Fi on macOS High Sierra 10.13.6. (I discovered this command in this page).
Hope this helps you.
Same problem here, it turned out to be my incorrectly configured proxy settings, here's how to check and remove them.
First open your git config file.
and find out whether the
[https] sections are set.
I used to set proxies for git due to slow access to Github in China, however, lately I changed my local proxy ports but I forgot my git settings.
If you have incorrect proxy settings and decide to remove it, simply execute:
git config --global --unset http.proxy git config --global --unset https.proxy
Things will work just fine.
A simple restart fixed it for me. I'm not sure what was the problem since I work with so much software but I have a feeling it was the VPN software or maybe the fact I put my laptop in sleep a lot and some file was corrupted. I really don't know but the restart fixed it.
Since you're using
LibreSSL, try re-installing
OpenSSL instead of Secure Transport.
All options have been removed from the
curl formula, so now you need to install via:
brew install curl-openssl
brew reinstall curl --with-openssl
Note: If above won't work, check
brew options curl to display install options specific to formula.
Here are few other suggestions:
curlfor more verbose output.
which -a curlto list them all.
curlin your firewall (such as Little Snitch).
I just turned off VPN and it solved the issue.
I have a similar issue and I just found that in my case it may be the antivirus that creates an issue.
At some moment I've got the same error while trying to pull some data from github.com.
I knew that Kaspersky is intercepting the SSL connections to check for malicious content from the sites and I decided to disable it, but I found that KAV is hung and not really responding, so I just closed Kaspersky and tried to connect to github.com again and alas! I was able to connect successfully to GitHub.
So in you case it may be a similar issue.
Issue solved by setting this env variable:
1) Tried creating a new branch and pushing. Worked for a couple of times but faced the same error again.
2)Just ran these two statements before pushing the code. All I did was to cancel the proxy.
$ git config --global --unset http.proxy $ git config --global --unset https.proxy
3) Faced the issue again after couple of weeks. I have updated homebrew and it got fixed
same issue with KAV. Restart it solved the pb.
I would suggest updating git. If you downloaded the
.pkg then be sure to uninstall it first.
for me, that's caused by the SSL certificate not enabled in the K8S ingress. hope this helps someone
I experienced this while trying to clone from an enterprise repository, and simply restarting the terminal solved it for me.
If anyone gets this issue while using the integrated terminal in Visual Studio Code then there is a good chance it's updating. Restart Visual Studio Code and you will likely see the "New Version" tab and it should all start working again.
The problem for me seems to have been how the user has been setup on my local machine to. Using the command
git push -u origin master
was causing the error. Removing the switch
-u to have
git push origin master
solved it for me. It can be scary to imagine how user setup can result in an error related to LibreSSL.
Hi everyone I found the solution regarding this github issue and it works for me no longer able to use private ssh key
Try following theses steps:
1 - Use HTTPS if possible. That will avoid SSH keys entirely.
2 - Manually add the SSH key to the running SSH agent. See manually generate ssh key
3 - If the two others doesn't work, delete all your ssh keys and generate some new one thats what I did after weeks of issues.
Hope it will help you..