吊销服务器脱机，吊销功能无法检查吊销 [英] The revocation function was unable to check revocation because the revocation server was offline

问题描述

致命:无法访问' https://gitlab.com/ ********/******.git/':schannel:下一个InitializeSecurityContext失败:未知错误(0x80092013)-吊销功能无法检查吊销因为吊销服务器处于脱机状态.

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.

当尝试从GitHub桌面客户端将最新更改推送到GitLab时，我收到此错误吗?我以前从未收到过它，并且总是模糊不清.在1周后进行推送时，如果未提交则会引发此错误?

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版本2.24.0.windows.2，可以使用以下解决方法:

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

git config --global http.schannelCheckRevoke false

从

我们不建议您为正常的Git使用情况设置此配置值.在某些情况下，这旨在成为逃生舱口"网络管理员已限制SChannel API的正常使用在Git尝试使用的Windows上.

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.

这篇关于吊销服务器脱机，吊销功能无法检查吊销的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！