Error When Setting Up Webhooks Through Proxy

[system]

Issues making requests to their Webhook server, after Orchestrator Upgrade.

Error Message: 'Could not connect to the server' appearing in Orchestrator UI when trying to setup the Webhooks URL in Orchestrator,

Symptoms where to apply this fix:

• Trying to configure proxy with Environment Variables , so Webhooks could successfully use it
• Trying to set up the Webhook in Orchestrator, we get 'Could not connect to the server' with Timed Out:

• When accessing the webhook endpoint from the Orchestrator Machine browser directly is working correctly, and the request is logged in the webhooks application. This means that there is no networking limitation between the Orchestrator Machine and Webhooks endpoint.

Root Cause: The Webhooks application is running under the wrong user or application pool in IIS. This is not permitting the service (WebhookService.API.exe) to start as expected.

Running the service manually, or changing the user and restarting IIS should fix the problem.

Tip: To verify if the service is correctly up and running, the Health Check Endpoint can be leveraged.

Resolution:
The error 'Could not connect to the server' appearing when trying to setup the Webhooks URL in Orchestrator, could mean that Webhooks application is unable to reach the webhook endpoint.

When using a proxy, this error is seen when Proxy is not configured for the Webhooks application. To configure it, use Orchestrator Installation - Using Environment Variables .

However, if the issue persists even after the Proxy settings have been applied, make sure that the service 'WebhookService.API.exe’ is correctly starting on the Orchestrator machine.

If it is not starting, try to start it manually, and check if Webhook requests can now reach the Webhook endpoint configured.

In this case, the issue is that the Webhooks application runs under the wrong user or application pool in IIS. This is not permitting the service to start as expected.