The revocation function was unable to check revocation because the revocation server was offline

▲
4
▼

fatal: unable to access 'https://gitlab.com/********/******.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

When trying to push my latest changes to GitLab from the GitHub desktop client I receive this error? I've never received this before and its always gone smoovly. When pushing after 1 week not committing its throwing this error?

I'm unsure how to fix this, it doesn't really give you much information.

git
github
asked on Stack Overflow Mar 3, 2018 by 0b9ff4fb

5 Answers

▲
4
▼

Using git version 2.24.0.windows.2, and this workaround is available:

git config --global http.schannelCheckRevoke false

From the docs:

We do not recommend setting this config value for normal Git usage. This is intended to be an "escape hatch" for situations where the network administrator has restricted the normal usage of SChannel APIs on Windows that Git is trying to use.

answered on Stack Overflow Nov 16, 2019 by Brannon
▲
2
▼

Seems like a problem with your revocation server. Active Directory, may be?

Anyway this bug suggests that an option to turn revocation checking off was merged and is available in git 2.16.1.windows.4.

git config --global http.schannel.checkRevoke false
answered on Stack Overflow Mar 3, 2018 by phd
▲
0
▼

Your PKI is misconfigured. You must make the CRL/OCSP service available to any client using your certificate.

  1. Setup CRL and OCSP available for all clients.
  2. Issue a new certificate using those.

It's best to just do it right from the beginning. I've setup many CA's and you can't miss the 1000's of lines of text about how you configure CRL and OCSP. Don't ignore them the next time.

answered on Stack Overflow Mar 20, 2019 by Mikael Dúi Bolinder
▲
0
▼

Have you tried checking the firewall settings, in my case antivirus was blocking the connection between the server and client(windows machine).

answered on Stack Overflow Nov 18, 2019 by Arjun Londhey
▲
-1
▼

I fixed the issue manually deleting all expired certificates from my PC (certmgr.msc). I read this in some forum and it worked however at this point I'm not sure why expired certificates cause this problem in some situations.

answered on Stack Overflow Oct 9, 2019 by Edgar Alejandro Navarro Garcia

User contributions licensed under CC BY-SA 3.0