Windows
System-wide HTTP/HTTPS proxy — all apps that honor Windows proxy settings (Edge, Chrome by default, .NET apps, most CLI tools) will route through helodata.
Settings UI (Windows 10/11)
Settings → Network & Internet → Proxy → Manual proxy setup.
Toggle Use a proxy server on.
Address:
gate.helodata.io(or your ISP IP). Port:7777.Click Save.
The next outbound request prompts for credentials:
Username: full proxy username (e.g.
helo_s1a2b3c4d5e-type-res-region-us)Password: sub-user password
The Settings UI does not persist proxy credentials — they're stored per app. For unattended use, prefer PowerShell or netsh.
[screenshot: Windows 11 Proxy settings pane]
PowerShell (programmatic)
$proxy = "http://gate.helodata.io:7777"
Set-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' `
-Name ProxyServer -Value $proxy
Set-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' `
-Name ProxyEnable -Value 1To remove:
CLI tools
curl on Windows reads HTTP_PROXY / HTTPS_PROXY:
For permanent envvars use System Properties → Environment Variables.
WinHTTP (system services, .NET)
For Windows services and .NET HttpClient (which uses WinHTTP, not the user proxy), set the system-level proxy:
To revert:
WinHTTP cannot embed credentials in the proxy URL — the calling app must supply them via IWebProxy.Credentials.
Verify
Or browse to that URL in Edge.
Common pitfalls
Two proxy systems (WinINet for user apps vs WinHTTP for services) — you may need both.
VPN clients often install themselves as a higher-priority proxy hook. Disconnect VPN to test.
.localand corporate suffixes bypass automatically — useful but watch the bypass list.
Last updated
Was this helpful?