Hello everyone,
We are currently trying to query a “Bridge Technologies VB Series” probe (VB330) located at a different site for our customer, using a proxy, without success (WINHTTP_TIMEOUT).
The proxy is reachable via the URL "proxy.edv.int" on port 8088 (not real values, just to explain here), and HTTP requests are basically successfully answered, for example via Postman or using PowerShell’s Invoke-WebRequest:

The proxy is configured to allow the remote probe’s IP address.
To provide the proxy to DataMiner, it has also been configured for the Windows SYSTEM user:

The settings of the probe element (based on latest connector version 1.4.2.5) are as follows:

As said above, without success(WINHTTP_TIMEOUT). It also doesn’t work with any other combination of strings/Ips/Ports in the edit mask (other issues then).
So our questions are:
• Is this the correct way to configure and use a proxy for the element?
• If not, what would be the correct configuration or solution to enable this http polling via proxy?
• What other issue could potentially be causing this issue?
Streamviewer output comes like this:

Ping on the probe is not answered, but the Web interface is accessible and operable in the element.
DataMiner is version 10.6.0 CU2.
Maybe one more thing to consider:
We are accessing the probe with http authentication, as shown in screenshot below.
Don’t know if the combination of proxy and authentication is maybe part of the problem.

Excerpt of the log output:
2026/06/01 16:59:32.577|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|7992|CProtocol::AddToExecute|DBG|2|Group 250 not added, it is already on the stack.
2026/06/01 16:59:32.577|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|7992|CProtocol::AddToExecute|DBG|2|Group 105 not added, it is already on the stack.
2026/06/01 16:59:32.577|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|7992|CProtocol::AddToExecute|DBG|2|Group 140 not added, it is already on the stack.
2026/06/01 16:59:32.577|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|28424|CParameter::RunQActions|DBG|5|QAction 21000 finished
2026/06/01 16:59:32.690|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|12320|CProtocol::ProcessHttpResult|INF|3|Error : 12002. [ERROR_WINHTTP_TIMEOUT]
2026/06/01 16:59:32.690|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|12320|CProtocol::LogHttpRequest|INF|3|<- 16:59:32 - GET http://1xx.xx.x.x1:80/probe/generaldata
2026/06/01 16:59:34.576|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|28424|CParameter::RunQActions|DBG|5|Find QAction 21000
2026/06/01 16:59:34.576|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|28424|CParameter::RunQActions|DBG|5|Run QAction 21000
2026/06/01 16:59:34.576|SLProtocol - 10808 - BridgeTech VB330 - xxx - Copy|28424|CQAction::Run|INF|2|QAction [21000] triggered by [pid=20985/idx=-1/pk=/user=]
Input: new = <NULL>
Input: old = <NULL>
Input: extra = <NULL>
We are running out of ideas, so any suggestion is very welcome.
Thanks, Regards
Jörg
Your element configuration looks right and proxy authentication has been ruled out.
Some additional things you can try in Powershell/Postman.
- A request that is typically not behind authentication. Do you get response data ? If yes, do you see data on the General page of the connector ?
curl.exe -k -v -x http://proxyIP:8080 http://<probeIP>/probe/status
- A request that requires HTTP authentication. Do you get response data ?
curl.exe -k -v -x http://proxyIP:8080 http://<probeIP>/probe/generaldata -u user:password
This will also help rule out if the proxy is doing any path filtering e.g. only allowing /probe