Outbound rest call stopped working today: No issuer certificate found for subject null

[Sean57]

Two weeks ago I created a simple outbound REST call from service now to our production server.  I tested it many times and also configured a business rule to call it via the javascript rest api script method whenever an incident is inserted.  This all worked like a charm as of two days ago.  Today, I noticed that the business rule no longer called into our system, so I went into the REST call itself and ran one of the   tests, which had been working as of two days ago.  The test failed with the following error message: org.apache.commons.httpclient.HttpException: No issuer certificate found for subject null  The HTTP status is 0 and the error code is 1.

On our side of the fence I didn't even see any attempts in the haproxy logs to reach the server.  Our endpoint's certificate is a valid CA issued cert (godaddy) and good through April 2020.  No changes have been made to our production servers.

Is there a limit to the number of outbound requests or time of use of service now sandbox instances?  I've searched for answers online and have seen many people with similar issues, but no responses that would explain why it worked a couple of days ago but not today.  Help would be greatly appreciated, thanks.

[Tony Chatfield1]

Hi, I am not aware of any sub-production transaction limitations and don't beleive http status 0 is a valid response code, which possibly indicates that there was no connection from your SNC instance to your server.

[Sean57]

Right, that's what I figured as well.  I also just discovered that ServiceNow patched our sandbox right before I started having trouble.  The incident we received from SN: 

Install New York Patch 3 on SNC Instance -

The change was created as part of the 2019 Jakarta End of Life Upgrade program.

I'm waiting for our contact here to get online so that we can escalate this with SN, but I'm hoping a representative will see this.

Thanks Tony

[Tony Chatfield1]

If you have access to the server try a tracert back to the instance, just incase it sheds some light

[Tony Chatfield1]

Also if utilising ECC queue you can confirm the outbound message/destination address from the outbound payload.