curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_REVOCATION_OFFLINE (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
Hello,
While build my app on AppVeyor and uploading to Nexus repository, the following message is displayed.
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_REVOCATION_OFFLINE (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
I called a cURL command to upload a binary file to Nexus repository.
The cURL command:
curl.exe -Ss -o NUL -F "raw.directory=$DirectoryName" -F "raw.asset1.filename=$BaseFileName" -F "raw.asset1=@$FileName" -H $BasicAuthHeader $Uri
It works well a few days ago, but does not work now.
I did not modify the AppVeyor pipeline and updated other part of source code.
Please help me to fix this problem.
Thank you.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 18 Mar, 2025 05:08 PM
This error occurs because curl, when using the Windows Schannel backend, is attempting to check the certificate revocation status of the server’s SSL certificate and is unable to reach the revocation server. The error code CRYPT_E_REVOCATION_OFFLINE (0x80092013) indicates that the revocation function couldn’t verify the certificate’s revocation status because it couldn’t contact the CRL (Certificate Revocation List) server.
A few things to try:
Disable certificate revocation check with
--ssl-no-revokeoption. This tells curl not to perform the revocation check. Note that while this bypasses the error, it does reduce the level of security verification.Adjust PowerShell settings by
$ErrorActionPreference = "Continue". However, this only suppresses the error output—it doesn’t fix the underlying SSL issue.Alternatively, it might be just a temporary issue with the revocation server or the connection between it and the AppVeyor datacenter, considering that it worked a few days ago.