Error: Fatal: unable to access 'https://github.com/xxx.git/': schannel: The revocation function was unable to check revocation for the certificate.
See original GitHub issueWhy am i getting this?
Fatal: unable to access 'https://github.com/xxx.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:15
- Comments:14 (2 by maintainers)
Top Results From Across the Web
github - Git - The revocation function was unable to check ...
Used to enforce or disable certificate revocation checks in cURL when http.sslBackend is set to "schannel". Defaults to true if unset. Only ...
Read more >The revocation function is unable to check revocation ... - GitHub
I am running behind a corporation that self-signs its certificates, which means that I get this issue when I try to push any...
Read more >Clone failed: The revocation function was unable to check ...
When Git is cloning the repository, it uses Windows' certificate store and crypto APIs to ensure the certificates are trusted. It sounds like ......
Read more >Unknown error (0x80092012) - The revocation ... - GitHub
I get this: [Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.] er...
Read more >I can no longer push my latest commit after the February 13 ...
fatal : unable to access 'Repo name': schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was ...
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
@RacheLev the issues you are encountering occurs when using Git on a network that blocks access to the revocation checks when verifying a SSL/TLS connection is secure.
I’m working on getting a fix into Git for Windows here: https://github.com/git-for-windows/git/pull/1450 and once that is fixed we’re tracking making this experience more friendly in #3326 to help with applying that fix. Please follow along with that issue for tracking the proper resolution.
To workaround this in the meantime, you can revert to the old OpenSSL behaviour:
OpenSSL requires it’s own certificate file to use for validation, and this PEM file distributed by the cURL team should do the trick.
Thank you! Fixed it. Not getting the error anymore, but for some reason its not letting me click ‘commit to master’. Why is that? Thank you! בתאריך 31 בינו׳ 2018 4:06 לפנה״צ, “Brendan Forster” < notifications@github.com> כתב: