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

Question

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.

Answer 1

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.

Answer 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.schannelCheckRevoke false