[Error] InitializeSecurityContext failed: Unknown error (0x80092013)
See original GitHub issuehi i can’t clone repository in desktop.
desktop error
Cloning into '...\abolfazl-ziaratban\azDoublyLinkedList'...
fatal: unable to access 'https://github.com/abolfazl-ziaratban/azDoublyLinkedList.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
Issue Analytics
- State:
- Created 6 years ago
- Comments:19 (5 by maintainers)
Top Results From Across the Web
curl: (35) schannel - Unknown error (0x80092013)
curl: (35) schannel: next InitializeSecurityContext failed: Unknown error (0x80092013). I have a Cisco ISE application which does posture of ...
Read more >The revocation function was unable to check ... - Stack Overflow
Anyway this bug suggests that an option to turn revocation checking off was merged and is available in git 2.16.1.windows.4.
Read more >schannel: next InitializeSecurityContext failed: Unknown error ...
schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) The revocation function was unable to check revocation because the revocation ...
Read more >git - revocation server was offline - Visual Studio Feedback
On VS 2017 git is failing to clone repository when using windows certificate ... next InitializeSecurityContext failed: Unknown error (0x80092013) - The ...
Read more >Out of solutions: InitializeSecurityContext failed (0x80092013)
... unfortunately this morning I got this error when I tried to login ... InitializeSecurityContext failed (0x80092013): Unknown error ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kunalrsinha
As a workaround, you can revert to the classic OpenSSL behaviour by opening the repository in a shell and running these two commands.
The PEM file distributed by the cURL team should do the trick.
Copy cert path from configuration git
Add to global configuration