Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to sync repositories using GitHub Desktop: fatal error 0x80092012
See original GitHub issueDescription
Hi I was trying to use GitHub Desktop to work with my repos, but I get an error like this (when cloning from or publishing to new repos):
fatal: unable to access ‘https://github.com/askbow/contact-expand.git/’: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - ������� ������ �� ������ ���������� �������� ������ ��� �����������.
Version
GitHub Desktop version: 1.0.4
OS version: Microsoft Windows [Version 6.1.7601]
Steps to Reproduce
- create new repo in the application
- add files
- commit
- press “publish”
Expected behavior: the repo syncs up to Github
Actual behavior: Unknown error (0x80092012)
Reproduces how often: everytime
Logs
2017-10-25T08:40:09.832Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: contact-expand - askbow (has token) 2017-10-25T08:40:10.404Z - error: [ui] git -c credential.helper= push origin master --set-upstream --progress exited with an unexpected code: 128. fatal: unable to access 'https://github.com/askbow/contact-expand.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - ������� ������ �� ������ ���������� �������� ������ ��� �����������.
Additional Information
I tried to curl the URI in the error, and I get this: `>curl https://github.com/askbow/contact-expand.git/
<html> <head><title>301 Moved Permanently</title></head> <body bgcolor="white"> <center>301 Moved Permanently
</center><center>nginx</center> </body> </html>`
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Nice. im fix its problem, down Kaspersiky
Confirmed it by installing the crypto provider back. This breaks desktop operation as I described above.
On their support forum I found a workaround: disable validation by setting DWORD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders\SCHANNEL\ManualCredValidationto 1.Probably not best practice, but will work for the time being.