After Orchestrator upgrade, why are Webhooks not going through Proxy, even after making the correct configurations?
Issue Description
Following an upgrade to Orchestrator, there are instances where Webhooks may not properly function through a proxy despite having the correct configurations in place.
Signs of this problem and aspects to examine include:
- While the request is transmitted via Webhooks can reach the endpoint in the browser and receive a 200 status (indicating that the proxy permits the request and the browser's proxy settings are correctly configured), the Webhooks application cannot communicate with this endpoint.
- Proxy configurations in the "web.config" file (C:\Program Files (x86)\UiPath\Orchestrator\Webhooks) for Webhooks are appropriately set up (using uppercase).
- Running a ping test to the endpoint using the CMD command is not an accurate indicator, as the proxy may not authorize TCP transmissions.
Root Cause
.NET Core may not acknowledge Environment Variable values in uppercase, under certain conditions.
Resolution
- The procedure for setting up Proxy environment variables is discussed in the Orchestrator - Installation Considerations' documentation.
- However, it looks like in certain .NET Core versions, uppercase OS values may not function as expected.
- To address this issue, use lower-case values as shown below in the configuration files when defining the Proxy. This adjustment should resolve the problem.
e.g: 'http_proxy', 'https_proxy', 'all_proxy', 'no_proxy'