You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't reproduce this on my personal devices, but the issue always occurs on my work machine when ever I launch WSL - e.g. opening Ubuntu in a terminal. That's the only step necessary.
Expected Behavior
WSL should not detect HTTP proxy changes that don't occur. Or, alternately, if the change is setting the same proxy IP and port it shouldn't trigger a notification.
Actual Behavior
When launching WSL, WSL reports the notification "An Http Proxy change has been detected on the host. Please restart WSL to apply the change". The notification repeats forever, approximately every second, nonstop until the machine is rebooted or wsl --shutdown is run. Over the course of a few minutes, I receive thousands of notifications.
This is a corporate machine that has a corporate-inspection proxy (ZScaler) installed. ZScaler sets a machine-wide proxy for the "127.0.0.1:9000" but as far as I know that's constant and never changes.
My ISP issues both Ipv6 and Ipv4 addresses. Due to connectivity failing with any Ipv6 host in wsl, I had to apply the following configuration to my .wslconfig:
[experimental]
networkingMode=mirrored
The issue still occurs even if the .wslconfig file is blanked out.
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
I would like to also add to this that I also receive the same notification from WSL regularly on a personal computer. The only thing related to a proxy I have one my network is a wpad deployment. Otherwise, there is no corporate proxy or any software to that nature deployed.
I could not find any information about what triggers this notification and any way to turn it off.
Windows Version
Microsoft Windows [Version 10.0.22631.3447]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-microsoft-standard-WSL2
Distro Version
22.04
Other Software
Ivanti Secure Access Client 22.7.28369
Microsoft Intune Management Extension 1.78.103.0
Nexthink Collector 24.2.03002
Rapid7 Insight Agent 4.0.7.26
ZScaler 4.3.0.181
ZScaler-Network-Adapter 1.0.2.0
Repro Steps
I can't reproduce this on my personal devices, but the issue always occurs on my work machine when ever I launch WSL - e.g. opening Ubuntu in a terminal. That's the only step necessary.
Expected Behavior
WSL should not detect HTTP proxy changes that don't occur. Or, alternately, if the change is setting the same proxy IP and port it shouldn't trigger a notification.
Actual Behavior
When launching WSL, WSL reports the notification "An Http Proxy change has been detected on the host. Please restart WSL to apply the change". The notification repeats forever, approximately every second, nonstop until the machine is rebooted or wsl --shutdown is run. Over the course of a few minutes, I receive thousands of notifications.
This is a corporate machine that has a corporate-inspection proxy (ZScaler) installed. ZScaler sets a machine-wide proxy for the "127.0.0.1:9000" but as far as I know that's constant and never changes.
My ISP issues both Ipv6 and Ipv4 addresses. Due to connectivity failing with any Ipv6 host in wsl, I had to apply the following configuration to my
.wslconfig
:The issue still occurs even if the
.wslconfig
file is blanked out.Diagnostic Logs
Diagnostic logs are available at Feedback Hub item https://aka.ms/AAq6z97
The text was updated successfully, but these errors were encountered: