SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443

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
it print:

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.

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

Possible duplicate of Git pull / push - unable to access HTTPS, SSL Routines seem to be down

– phd
Feb 26 '18 at 12:57

This happened to me since a few days ago. In most of the cases, it fails the first time and succeeds the second time and third time ...

– Donald
Mar 17 '18 at 2:35

Hi @EmileCantero , did you solve the issue? starting last 2 weeks I'm also getting the same error...

– Daniyar
Apr 27 '18 at 11:58

1

hi guys it's been a while I am not sure how I fix it but I am sure I fix it so I will go search for you and comme back asap with the right infos

– Emile Cantero
Apr 30 '18 at 6:14

add a comment |

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
it print:

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.

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

Possible duplicate of Git pull / push - unable to access HTTPS, SSL Routines seem to be down

– phd
Feb 26 '18 at 12:57

This happened to me since a few days ago. In most of the cases, it fails the first time and succeeds the second time and third time ...

– Donald
Mar 17 '18 at 2:35

Hi @EmileCantero , did you solve the issue? starting last 2 weeks I'm also getting the same error...

– Daniyar
Apr 27 '18 at 11:58

1

hi guys it's been a while I am not sure how I fix it but I am sure I fix it so I will go search for you and comme back asap with the right infos

– Emile Cantero
Apr 30 '18 at 6:14

add a comment |

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
it print:

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.

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

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
it print:

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.

git npm openssl homebrew

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

edited Jan 19 at 23:25

kenorb

67.3k28404399

edited Jan 19 at 23:25

kenorb

67.3k28404399

edited Jan 19 at 23:25

kenorb

67.3k28404399

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

asked Feb 26 '18 at 11:31

Emile Cantero

5132625

Possible duplicate of Git pull / push - unable to access HTTPS, SSL Routines seem to be down

– phd
Feb 26 '18 at 12:57

This happened to me since a few days ago. In most of the cases, it fails the first time and succeeds the second time and third time ...

– Donald
Mar 17 '18 at 2:35

Hi @EmileCantero , did you solve the issue? starting last 2 weeks I'm also getting the same error...

– Daniyar
Apr 27 '18 at 11:58

1

hi guys it's been a while I am not sure how I fix it but I am sure I fix it so I will go search for you and comme back asap with the right infos

– Emile Cantero
Apr 30 '18 at 6:14

add a comment |

Possible duplicate of Git pull / push - unable to access HTTPS, SSL Routines seem to be down

– phd
Feb 26 '18 at 12:57

This happened to me since a few days ago. In most of the cases, it fails the first time and succeeds the second time and third time ...

– Donald
Mar 17 '18 at 2:35

Hi @EmileCantero , did you solve the issue? starting last 2 weeks I'm also getting the same error...

– Daniyar
Apr 27 '18 at 11:58

1

hi guys it's been a while I am not sure how I fix it but I am sure I fix it so I will go search for you and comme back asap with the right infos

– Emile Cantero
Apr 30 '18 at 6:14

Possible duplicate of Git pull / push - unable to access HTTPS, SSL Routines seem to be down

– phd
Feb 26 '18 at 12:57

This happened to me since a few days ago. In most of the cases, it fails the first time and succeeds the second time and third time ...

– Donald
Mar 17 '18 at 2:35

Hi @EmileCantero , did you solve the issue? starting last 2 weeks I'm also getting the same error...

– Daniyar
Apr 27 '18 at 11:58

hi guys it's been a while I am not sure how I fix it but I am sure I fix it so I will go search for you and comme back asap with the right infos

– Emile Cantero
Apr 30 '18 at 6:14

add a comment |

6 Answers
6

active

oldest

votes

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.

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

add a comment |

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.

vi ~/.gitconfig

and find out whether the [http] or [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.

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

add a comment |

Since you're using LibreSSL, try re-installing curl with OpenSSL instead of Secure Transport:

brew reinstall curl --with-openssl

Here are few other suggestions:

Make sure you're not using http_proxy/https_proxy.

Use -v to curl for more verbose output.

Try using BSD curl at /usr/bin/curl, run which -a curl to list them all.

Make sure you haven't accidentally blocked curl in your firewall (such as Little Snitch).

Alternatively use wget.

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

add a comment |

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.

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

add a comment |

I would suggest updating git. If you downloaded the .pkg then be sure to uninstall it first.

answered Mar 12 '18 at 3:51

Andreas GS

19811

add a comment |

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..

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48987512%2fssl-connect-ssl-error-syscall-in-connection-to-github-com443%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

6 Answers
6

active

oldest

votes

6 Answers
6

active

oldest

votes

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.

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

add a comment |

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.

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

add a comment |

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.

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

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.

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

edited Aug 6 '18 at 11:17

answered Jul 26 '18 at 17:37

mljrg

1,6771828

answered Jul 26 '18 at 17:37

mljrg

1,6771828

answered Jul 26 '18 at 17:37

mljrg

1,6771828

add a comment |

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.

vi ~/.gitconfig

and find out whether the [http] or [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.

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

add a comment |

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.

vi ~/.gitconfig

and find out whether the [http] or [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.

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

add a comment |

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.

vi ~/.gitconfig

and find out whether the [http] or [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.

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

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.

vi ~/.gitconfig

and find out whether the [http] or [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.

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

edited Apr 12 '18 at 9:55

Jesse de Bruijne

2,47861427

answered Apr 12 '18 at 6:44

Nick Zhang

515

answered Apr 12 '18 at 6:44

Nick Zhang

515

answered Apr 12 '18 at 6:44

Nick Zhang

515

add a comment |

Since you're using LibreSSL, try re-installing curl with OpenSSL instead of Secure Transport:

brew reinstall curl --with-openssl

Here are few other suggestions:

Make sure you're not using http_proxy/https_proxy.

Use -v to curl for more verbose output.

Try using BSD curl at /usr/bin/curl, run which -a curl to list them all.

Make sure you haven't accidentally blocked curl in your firewall (such as Little Snitch).

Alternatively use wget.

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

add a comment |

Since you're using LibreSSL, try re-installing curl with OpenSSL instead of Secure Transport:

brew reinstall curl --with-openssl

Here are few other suggestions:

Make sure you're not using http_proxy/https_proxy.

Use -v to curl for more verbose output.

Try using BSD curl at /usr/bin/curl, run which -a curl to list them all.

Make sure you haven't accidentally blocked curl in your firewall (such as Little Snitch).

Alternatively use wget.

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

add a comment |

Since you're using LibreSSL, try re-installing curl with OpenSSL instead of Secure Transport:

brew reinstall curl --with-openssl

Here are few other suggestions:

Make sure you're not using http_proxy/https_proxy.

Use -v to curl for more verbose output.

Try using BSD curl at /usr/bin/curl, run which -a curl to list them all.

Make sure you haven't accidentally blocked curl in your firewall (such as Little Snitch).

Alternatively use wget.

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

Since you're using LibreSSL, try re-installing curl with OpenSSL instead of Secure Transport:

brew reinstall curl --with-openssl

Here are few other suggestions:

Make sure you're not using http_proxy/https_proxy.

Use -v to curl for more verbose output.

Try using BSD curl at /usr/bin/curl, run which -a curl to list them all.

Make sure you haven't accidentally blocked curl in your firewall (such as Little Snitch).

Alternatively use wget.

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

answered Apr 12 '18 at 13:46

kenorb

67.3k28404399

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

add a comment |

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

brew will fail as well as it depends on on LibreSSL as well as curl.

– Computer Mage
Jan 19 at 23:02

add a comment |

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

add a comment |

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

add a comment |

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

answered Sep 19 '18 at 4:24

Amos Kosgei

43958

add a comment |

I would suggest updating git. If you downloaded the .pkg then be sure to uninstall it first.

answered Mar 12 '18 at 3:51

Andreas GS

19811

add a comment |

I would suggest updating git. If you downloaded the .pkg then be sure to uninstall it first.

answered Mar 12 '18 at 3:51

Andreas GS

19811

add a comment |

I would suggest updating git. If you downloaded the .pkg then be sure to uninstall it first.

answered Mar 12 '18 at 3:51

Andreas GS

19811

I would suggest updating git. If you downloaded the .pkg then be sure to uninstall it first.

answered Mar 12 '18 at 3:51

Andreas GS

19811

answered Mar 12 '18 at 3:51

Andreas GS

19811

answered Mar 12 '18 at 3:51

Andreas GS

19811

answered Mar 12 '18 at 3:51

Andreas GS

19811

add a comment |

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:

Hope it will help you..

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

add a comment |

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:

Hope it will help you..

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

add a comment |

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:

Hope it will help you..

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

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:

Hope it will help you..

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

edited May 2 '18 at 9:10

answered May 1 '18 at 0:14

Emile Cantero

5132625

answered May 1 '18 at 0:14

Emile Cantero

5132625

answered May 1 '18 at 0:14

Emile Cantero

5132625

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Brtdku