Getting 404 Error in Production Instance.

[sapnapraveen]

Hi ,

Using REST API's we have intergrated ServiceNow to 3rd party. From ServiceNow to 3rd party the folders are getting created once request is submitted. It was successful but it stopped working in production environment and throwing 404 error in the log.

The same works good in Dev, QA, Stage envrionments. Can anyone suggest a fix. 

[Fernando Koenra]

Hi Sapnapraveen,

From your short description I understand you are getting a 404 error when posting something to the 3rd party via REST.

Typically a 404 indicates that the REST API can’t find the target URL/resource - or it doesn't exist. 

- Are you using the same endpoints on your other environments compared to the Production instance?

- Or are are you using different endpoints for the subproduction instances, and perhaps a subproduction endpoint for the 3rd party? 

Without further information on the 3rd party you are integrating with this would be hard to find out.

- Have you contacted the 3rd party to validate if the endpoint is correct and/or if they are perhaps not allowing the connection from your production instances? 

Kind regards,
Fernando

[sapnapraveen]

Hi Fernando,

Are you using the same endpoints on your other environments compared to the Production instance?-- >  For the snow lower environment the 3rd party dev endpoint has been used. for snow producion 3rd party prod endpoint has been used.

Or are are you using different endpoints for the subproduction instances, and perhaps a subproduction endpoint for the 3rd party?

--> Yes different endpints has been used depends on the prod and lower environments.

Have you contacted the 3rd party to validate if the endpoint is correct and/or if they are perhaps not allowing the connection from your production instances? 

--> Yes, when we try to direclty navigate the base URL  from the browser getting as "Authorization has been denied" . But the service account is an admin account.

[Hitoshi Ozawa]

Hi Sapnapraveen,

404 error implies the url can not be reached. Since the url is working in other instances, it may be that the url in the production instance was changed or there is a firewall blocking traffic from the production instance to the 3rd party API endpoint.

Re-check the url to make sure it is correct.

Next, check if there is a firewall that may be blocking access to the 3rd party api endpoint.

[sapnapraveen]

Hi Hitoshi,

Yes, Checked with Network Team, firewall is not blocking the endpoint.