REST connection - Name or service not known error

[shivmano]

Hi Team,

I am seeing an issue with a REST application (cookie based authentication) which was working fine for many months is throwing an error "Name or service not known error" now 

here is what I see in logs: 

2023-11-10/05:46:33.180 [{}] [https-jsse-nio-443-exec-658] DEBUG rest.RestProvisioningService - Got Webservice API Response: [error:Error stage-alm.***.net: Name or service not known]

Looks like suddenly Saviynt is unable to reach the target host. I have also tried replacing the hostname with the IP and get connection timeout error. Please can someone advise what should be done to fix this 

Note: From postman this works just fine and also on Saviynt it was working fine so far 

[amit_krishnajit]

Validate the URL - mostly an incorrect URL causes a service not known error. 

Another probability is that Saviynt is unable to reach the target. You may want to validate that if you are able to make a curl command to the target from the SC2 client which is deployed in the customer network. 

[DixshantValecha]

It seems like you are facing an issue with your REST application that uses cookie-based authentication. The error message “Name or service not known” indicates that the application is unable to resolve the hostname of the target server.

You mentioned that you have tried replacing the hostname with the IP address and still get a connection timeout error. This could indicate that there is a network issue preventing your application from reaching the target server.

Here are a few things you can try to resolve the issue:

Check if the hostname or IP address of the target server has changed recently. If it has, update your application configuration accordingly.

Ensure that your application has the necessary network connectivity to reach the target server. You can try pinging the server from your application server to check if there is any network issue.

Check if there are any firewall rules or security policies that might be blocking your application from accessing the target server.

Verify that the SSL certificate used by the target server is valid and not expired.

Check if there are any recent changes to the target server that might have caused the issue.