Proxy Settings for Universal Module
Hello,
we are experiencing an issue with the Universal module when running it on a server behind an HTTP proxy.
(https://www.powershellgallery.com/packages/Universal/)
We use the module to connect to our PowerShell Universal server, for example with Connect-PSUServer.
The server has a system-wide proxy configuration that includes exceptions/bypass rules for certain hosts.
I observed that the module appears to retrieve the system's proxy settings, but does not honor the configured proxy exceptions.
As a result, Connect-PSUServer attempts to connect to our PSU server through the proxy, even though the PSU server is configured as a proxy exception.
Is this expected behavior, or is there currently a workaround for this?
If the proxy exceptions cannot be honored automatically, it would also be useful to have an option such as -NoProxy on the relevant cmdlets to explicitly bypass the proxy.
Universal module version: 2026.2.3
Thank you!
All Comments (1)
Hello philippkruett,
Thank you for reporting this and for the detailed description.
At this point, I have not found PowerShell Universal documentation confirming that Connect-PSUServer should automatically honor all system-level proxy bypass configurations. I would like to narrow down which proxy mechanism is being used before determining whether this is expected behavior or an issue with the Universal module.
Could you please confirm the following?
1. PowerShell version and edition where the Universal module is running, for example Windows PowerShell 5.1 or PowerShell 7.x.
2. Operating system.
3. How the system-wide proxy is configured, for example:
Windows Internet Options / GPO
PAC / WPAD
WinHTTP
Environment variables
4. Whether any of these environment variables are defined:
HTTP_PROXY
HTTPS_PROXY
ALL_PROXY
NO_PROXY
Please only confirm whether they are defined. Do not post their actual values.
From the same PowerShell session where Connect-PSUServer fails, could you also run the following test?
$Uri = [Uri]'https://<PSU_HOST>'
[System.Net.Http.HttpClient]::DefaultProxy.IsBypassed($Uri)
[System.Net.Http.HttpClient]::DefaultProxy.GetProxy($Uri)
This will help us determine whether .NET itself considers the PSU destination to be excluded from the proxy before we investigate the Universal module behavior further.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.
References:
https://learn.microsoft.com/en-us/dotnet/api/system.net.http.httpclient.defaultproxy
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/invoke-webrequest
Best regards,
Ruben Tapia