Summary
This article explains the cause of the error of "The revocation function was unable to check revocation because the revocation server was offline. " and the workaround.
Synopsis
The following error or similar may be seen in FNMS logs, particularly the packageretriever.log, uploader.log, upload.log (ComplianceUpload) and others.
[10/25/2015 9:40:52 AM (G, 0)] {520} Download failure: The revocation function was unable to check revocation because the revocation server was offline.
[10/25/2015 9:40:52 AM (U, 0)] {520} ERROR: Error (s107m858)
[10/25/2015 9:40:52 AM (U, 0)] {520} ----------------
[10/25/2015 9:40:52 AM (U, 0)] {520} The following network error occurred while retrieving the application:Discussion
This error message complains of the revocation server being offline, which points to the CRL list supplied via the certificate.
Workaround
For FNMS Cloud, these URLs that are required including the CRL URLs, are available via the online help under the following section:
Inventory Beacons -> Inventory Beacon Reference -> Ports and URLs for Inventory Beacons
For FNMS On-Premise, consult your certificate provider for the list of URLs that are required to validate the certificates installed in the environment.
