Clone failed: The revocation function was unable to check revocation because the revocation server was offline.

[quocb14005xx]

Description

[Description of the issue]

Version

GitHub Desktop version: [version here]

OS version: [version here]

Steps to Reproduce

1. [First step]
2. [Second step]
3. [and so on]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Reproduces how often: [What percentage of the time does it reproduce?]

Logs

Additional Information

[shiftkey]

Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

When Git is cloning the repository, it uses Windows' certificate store and crypto APIs to ensure the certificates are trusted. It sounds like the revocation server isn't available when you're cloning, so it fails rather than continue to clone. This feels like the expected behaviour when the client cannot trust the server.

@quocb14005xx is this issue repeatable? Could you provide more details about your setup?

[AlxrMironovOldAcc]

Check the IE settings, i had same problem becouse of IE Proxy settings.

[shiftkey]

@quocb14005xx thank you for your issue!

We haven't gotten a response to the questions in our comment here. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.

[jmporter34]

Hi,
I'm having a similar error trying to clone from a Git Bash window:
$ git clone https://github.com/NordicSemiconductor/IOS-nRF-Toolbox.git
Cloning into 'IOS-nRF-Toolbox'...
fatal: unable to access 'https://github.com/NordicSemiconductor/IOS-nRF-Toolbox.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

I also tried from a Windows Command prompt, same result.
I tried each at least 5 times (Bash + Command prompt), it's 100% reproducible.

Some background:

1. The problem occurred on my personal Windows 7 laptop on my home WiFi network.
2. I just confirmed that I am able to clone the same repo successfully on my employer-assigned Windows 7 laptop on my home WiFi network.
3. I was able to clone the same repo successfully a few days ago on my employer-assigned Windows 7 laptop on my employer's network.
4. I can't test with my personal laptop on my employer's network, it's forbidden.
5. A little earlier today, I was able to successfully clone a different repo from a different hosting service on my personal Windows 7 laptop on my home WiFi network (i.e. same setup that's failing for the Nordic GitHub repo).

Does this info help you troubleshoot the problem and suggest a fix or workaround ?
Thanks
John Porter

[shiftkey]

@jmporter34 we've traced this issue to some corporate networks that block certificate revocation lookups when Git is configured to using SChannel (rather than OpenSSL).

I've contributed a patch to Git for Windows which lets you bypass the revocation check git-for-windows/git#1450 and this is available in Git for Windows 2.16.1.windows.4.

To disable the revocation check:

$ git config --global http.schannel.checkRevoke false

[jmporter34]

Hi shiftkey,
Thanks for the quick response. I checked that I already had 2.16.1.windows.4 installed (I did), added the checkRevoke statement as specified, closed and re-opened both Bash and Cmd and tried again from both. I got the same results as before, which I've pasted below. Again, I tried both Bash and Cmd at least five times each.
Just FYI, the problem is not on my corporate network, it's with my personal laptop on my home WiFi. My corporate laptop is able to clone the same repo successfully from work, and from my home WiFi.
Thanks

jporter@jporter-W530 MINGW64 /c/_projects/git/github/nordic
$ git version
git version 2.16.1.windows.4

jporter@jporter-W530 MINGW64 /c/_projects/git/github/nordic
$ git config --global --list
winupdater.recentlyseenversion=2.16.1.windows.4
user.name=John Porter
user.email=jmporter34@gmail.com
merge.tool=p4merge
mergetool.p4merge.path=C:/Program Files/Perforce/p4merge.exe
mergetool.prompt=false
diff.tool=p4merge
difftool.p4merge.path=C:/Program Files/Perforce/p4merge.exe
difftool.prompt=false
http.schannel.checkrevoke=false

jporter@jporter-W530 MINGW64 /c/_projects/git/github/nordic
$ git clone https://github.com/NordicSemiconductor/IOS-nRF-Toolbox.git
Cloning into 'IOS-nRF-Toolbox'...
fatal: unable to access 'https://github.com/NordicSemiconductor/IOS-nRF-Toolbox.
git/': schannel: next InitializeSecurityContext failed: Unknown error (0x8009201
3) - The revocation function was unable to check revocation because the revocati
on server was offline.

[shiftkey]

@jmporter34 please open an issue over on the Git for Windows project and also include the system Git config (git config --system -l).

I don't have access to a network to really test this behaviour, so I'm flying in the dark a bit...

[jmporter34]

Hi, I just finished creating the issue, #1505. Thanks

…

On Mon, Feb 19, 2018 at 3:24 AM, Brendan Forster ***@***.***> wrote: @jmporter34 <https://github.com/jmporter34> please open an issue over on the Git for Windows <https://github.com/git-for-windows/git> project and also include the system Git config (git config --system -l). I don't have access to a network to really test this behaviour, so I'm flying in the dark a bit... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2414 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ai0l944itLhEGJiTce0Dj1S0W_aHp6A4ks5tWS_HgaJpZM4OwLsD> .

[prasannadas143]

I encountered same issue for my repository.
fatal: unable to access : schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

Any update on this issue?

[AndyGee]

Check your "C:\Users<user>.gitconfig" for proxy configuration, or anything else that might be providing wrong credentials - Had the same issue, and it turned out to be the corporate proxy settings.

[mobajunior]

Description

[Description of the issue]

Version

GitHub Desktop version: [version here]

OS version: [version here]

Steps to Reproduce

1. [First step]
2. [Second step]
3. [and so on]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Reproduces how often: [What percentage of the time does it reproduce?]

Logs

Additional Information

Resolved in this link: https://stackoverflow.com/questions/45556189/git-the-revocation-function-was-unable-to-check-revocation-for-the-certificate

[minotalen]

Happened to me when my windows date was 7 days in the future.

[soorena110]

I removed git and again install it ... then the problem solved :))