Replies: 1 comment
-
|
The fix for the user was that their system was set to use SSL over a non-standard port. Normally the port for SSL is 443 out of the box, and you only deviate if you've got an advanced oddball setup. The user swapped it back to 443 on their system and Synthesis was able communicate normally with GitHub again. It has been reported that using some VPNs will be what causes the non-standard SSL port to be active. Can look at tweaking their settings, or overriding Git configuration on your to forcibly use 443 as the port anyway. Depends on the VPN and your setup |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Failure while checking/cloning repository LibGit2Sharp.LibGit2SharpException: failed to connect to github.comVarious patchers and patcher browser functionality fails to work with the above error
You're able to visit github.com webpage in a browser, but actually doing a
git clonecall fails.Beta Was this translation helpful? Give feedback.
All reactions