Azure spoke issue
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
We are getting this issue , when try to test azure spoke
{
"Action Status": {
"code": 1,
"message": "Request not sent to uri= https://stamiddlewarewe.blob.core.windows.net/package-request/test567 : org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 10000"
}
}
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited an hour ago
1)The default 10000ms (10 seconds) is often too short for Azure cloud APIs, which may have higher session wait times.
- Navigate to Connections & Credentials > Connection & Credentials Aliases in your ServiceNow instance.
- Open the Alias record used by your Azure Spoke and go to the Connection Attributes related list.
- Click New and create an attribute with the name http_timeout and a value of 30000 or 60000 (representing 30 or 60 seconds)
2)If the timeout occurs while using an on-premise network or a MID Server, ensure the firewall is not dropping the packets.
- Ensure your MID Server can reach https://xxxxxxx.azure.com and https://login.microsoftonline.com on port 443 ( check the port used in config.xml of mid server)
- Test the connection from the MID server itself (like hit the API using a browser client )
3)The connection may drop during the handshake if Azure denies the request.
- Verify that you are using the actual Azure Client Secret Value (not the Secret ID) in your ServiceNow OAuth Credential record.
- Ensure that you have granted the proper API permissions in the Azure portal
