MID Servers are DOWN

Glenn11
Tera Contributor

Hi,

Currently i am stuck with my MID servers status are Down. When i try to open the logs i got this error.
Can someone guide what i am missing here. Apparently the port 80 is open and 443.


"2/23/21 09:27:06 (004) StartupSequencer WARNING *** WARNING *** OCSPCheck authority: http://ocsp.entrust.net, error: java.net.SocketException: Connection reset
02/23/21 09:27:06 (004) StartupSequencer WARNING *** WARNING *** Socket error
02/23/21 09:27:06 (004) StartupSequencer WARNING *** WARNING *** OCSP revoke check IOException for *.service-now.com
02/23/21 09:27:06 (004) StartupSequencer WARNING *** WARNING *** Request not sent to uri= https://Instance.service-now.com/InstanceInfo.do?SOAP : org.apache.commons.httpclient.HttpException: Connection reset
02/23/21 09:27:06 (004) StartupSequencer SEVERE *** ERROR *** SOAP Request: <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.service-now.com/GetMIDInfo" xmlns:m="http://www.service-now.com" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><m:execute></m:execute></SOAP-ENV:Body></SOAP-ENV:Envelope>
02/23/21 09:27:06 (004) StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=0, Response body=null
02/23/21 09:27:06 (004) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on https://Instance.service-now.com/: Please check that the InstanceInfo page exists in the sys_public table and active="true".
02/23/21 09:27:06 (004) StartupSequencer SEVERE *** ERROR *** Request not sent to uri= https://Instance.service-now.com/InstanceInfo.do?SOAP : org.apache.commons.httpclient.HttpException: Connection reset
(Network Configuration issue) Please check that the MID server can ping the instance: https://Instance.service-now.com/
You may also need to configure the network that the MID server uses to allow traffic over TCP port 443.
02/23/21 09:27:06 (004) StartupSequencer SEVERE *** ERROR *** test failure"

 

1 ACCEPTED SOLUTION

BhupeshG
Tera Guru

 

It might be due to authentication to the certificate trust store.

 

Mid server communicates with Instance using the high-security OCSP check. Disabling the Certification revocation will bypass this OCSP check.

1. In this case, the host machine is not able to make a successful OCSP connection against the ServiceNow certificate to the following URI:
http://ocsp.entrust.net
2. An internal firewall rule or proxy configuration prevents the OCSP call from going out, and the connection fails.
3. You will need to allow the connection as per below KA:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0813636



4. You need to allow the above url's from your Mid server firewall uni-directionally.

I hope this helps.

View solution in original post

4 REPLIES 4

Maik Skoddow
Tera Patron
Tera Patron

Hi @Glenn 

please read the following documentation page and KB article: 

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/mid-server/reference/r_M...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0813636

Kind regards
Maik

If my answer replied your question please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

Indeed this is firewall issue and the port issue.


Also do you have a proxy for this?

 

Thanks,
Ashutosh

BhupeshG
Tera Guru

 

It might be due to authentication to the certificate trust store.

 

Mid server communicates with Instance using the high-security OCSP check. Disabling the Certification revocation will bypass this OCSP check.

1. In this case, the host machine is not able to make a successful OCSP connection against the ServiceNow certificate to the following URI:
http://ocsp.entrust.net
2. An internal firewall rule or proxy configuration prevents the OCSP call from going out, and the connection fails.
3. You will need to allow the connection as per below KA:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0813636



4. You need to allow the above url's from your Mid server firewall uni-directionally.

I hope this helps.

Community Alums
Not applicable

Anyone else getting "Your role does not grant you access to this article. Please use Search to find related content" when trying to access this? Do we have to open a SN Support Case just to gain access?

Thanks