Mid Server is down with connection error between MID server host and OCSPCheck authorityDescriptionMID server is down with OCSP errorsRelease or EnvironmentQuebec Patch 7 Hot FixCauseReviewed Agent logs and found communications error between MID server host and OCSPCheck authority 11/30/21 11:18:34 (738) RefreshMonitor.65 WARNING *** WARNING *** OCSPCheck HTTP status: 403, error message: Method failed: (/) with code: 403 - Forbidden username/password combo 11/30/21 11:18:34 (738) RefreshMonitor.65 WARNING *** WARNING *** OCSP revoke check IOException for *.service-now.com 11/30/21 11:18:34 (738) RefreshMonitor.65 WARNING *** WARNING *** org.apache.commons.httpclient.HttpException: unknown tag 28 encountered 11/30/21 11:18:34 (738) RefreshMonitor.65 SEVERE *** ERROR *** getRecords failed (org.apache.commons.httpclient.HttpException: unknown tag 28 encountered) 11/30/21 11:18:34 (738) RefreshMonitor.65 WARNING *** WARNING *** MIDRemoteGlideRecord.query failed, retrying in 120 seconds 11/30/21 11:18:40 (501) ECCQueueMonitor.1 WARNING *** WARNING *** OCSPCheck HTTP status: 403, error message: Method failed: (/) with code: 403 - Forbidden username/password combo 11/30/21 11:18:40 (501) ECCQueueMonitor.1 WARNING *** WARNING *** OCSP revoke check IOException for *.service-now.com 11/30/21 11:18:40 (501) ECCQueueMonitor.1 WARNING *** WARNING *** org.apache.commons.httpclient.HttpException: unknown tag 28 encountered 11/30/21 11:18:40 (501) ECCQueueMonitor.1 SEVERE *** ERROR *** getRecords failed (org.apache.commons.httpclient.HttpException: unknown tag 28 encountered) If the MID server cannot reach the accessLocation URIName the revocation test will not pass.ResolutionPlease review communication between MID server and OCSP server, and review certStatus result: Confirm the MID server can communicate to the OCSP server, may need to involve your network team if communication is being blockedReview the traffic and confirm the server replied with a certStatus= good. Or create a policy for the target url so that the OCSP check is not performed, this is not the suggested workaround. Note: Your security team would need to determine what they consider the safest solution out of the two above. If the MID server is down due to OCSP errors, you could also set following mid server parameter on the config.xml as a temporary workaround: <parameter name="mid.ssl.bootstrap.default.check_cert_revocation" value="true"/> Refer to this document Click here for more details on SSL issues .