Cloning into 'E:\---'... fatal: unable to access(); #21855
-
Cloning into ‘E:—’… fatal: unable to access ‘https://github.com/------.git/’: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
Is it A bug Are How Can I Fix it |
Beta Was this translation helpful? Give feedback.
-
@nihaalknight87 this is a known issue that can occur with GitHub Desktop. This error is usually caused by your network blocking the attempt by Windows to check the revocation status of a certificate, which then causes the whole operation to error. You can find a workaround for this issue here: If you have any questions about the workaround, please let me know. |
Beta Was this translation helpful? Give feedback.
-
i did’nt get clerification on this could you please help me out by providing in details |
Beta Was this translation helpful? Give feedback.
-
This is a recurrent problem on Windows, it would be good if - as at least one person has suggested - the error message was more informative eg. suggesting to look at recently installed software / updates which might be blocking it. Plus, as a naive user, I have no idea what a revocation server is, why I need it, or why it should be unavailable. Is it an actual server which might be down? From the comments on (many) past reports it is more likely blocking of access. However, in the past I have got this error then a day or so later it has gone away without me doing anything, which suggests that it is not blocking of access on my machine as most comments suggest but a fault further down the line. Perhaps this should be part of the explanation. Also, the reference to the workaround goes to a 404. |
Beta Was this translation helpful? Give feedback.
-
I’ve also been having this issue intermittently for the past two weeks, despite having no problems for the 5 prior months that I have been using it with this repository. As ‘ijohnson222’ said, it does go away after a day or two, but I still find it disconcerting and would like to see if there’s anything I can do about it. Since the link you found helpful no longer exists – could you please reproduce the solution here? (also another user recently reported the same issue so it seems it has not really been resolved: https://github.community/t5/forums/replypage/board-id/Board_1/message-id/8642) ) |
Beta Was this translation helpful? Give feedback.
-
Hi Steve, Could you please review new messages added to this tread since your solution was posted? The link with the solution no longer works. Thank you in advance! Georgia |
Beta Was this translation helpful? Give feedback.
-
Hi @georgiaoc, Thank you for being here and for reaching out! Can you try this link to see if this is the information that you are looking for: https://github.com/desktop/desktop/blob/development/docs/known-issues.md#certificate-revocation-check-fails—3326 ? |
Beta Was this translation helpful? Give feedback.
-
Great, thank you! |
Beta Was this translation helpful? Give feedback.
@nihaalknight87 this is a known issue that can occur with GitHub Desktop. This error is usually caused by your network blocking the attempt by Windows to check the revocation status of a certificate, which then causes the whole operation to error. You can find a workaround for this issue here:
https://github.com/desktop/desktop/blob/development/docs/known-issues.md#certificate-revocation-check-fails—3326
If you have any questions about the workaround, please let me know.