This is a follow-up question for https://community.dataminer.services/question/c-api-connection-using-proxy/
The initial problem was that an automation script was not using the proxy for reaching an API in the cloud (using HttpClient). The solution was to configure the proxy for the NT_AUTHORITY/SYSTEM user. That works fine now.
However now we also have a driver installed on the DMA which is also talking to the cloud API, but apparently this driver is also not using the configured proxy for the SYSTEM user, as we get timeouts for outgoing http calls. Probably drivers use a different communication mechanism for HTTP?
So how could this be fixed?
The HTTP engine used by DataMiner connectors is WinHTTP. To configure the proxy server there you can either add it manually with the following command:
netsh winhttp set proxy myproxyserver:port
Or import it from Internet Explorer with the following command:
netsh winhttp import proxy ie
When you want to verify if the settings are configured as desired, you can use the following command:
netsh winhttp show proxy
In the end it turned out to be the issue, additionally we also had to remove the bypassproxy value in the bus address field of the element config. Thanks for the help Jeroen!