-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL cannot use proxy with networkingMode=mirrored #10794
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
try firewall=false? |
|
yeah,now my .wslconfig is below, but also come same problem
|
Additionally, access the external network is normal, like |
It may not help but, I tried |
yeah,even reboot computer |
I upgraded from Ubuntu 20.04 to Ubuntu 22.04, and the issue got resolved, although I don't know how it was fixed. The reason I had this idea is that my other computer, which has Ubuntu 22.04 installed, could successfully use the proxy. |
whether you set the HTTP_PROXY environment variable? |
No, it will set itself. |
我也遇到了这个问题。请问你解决了吗 |
升级到 22.04 就没问题了🤣 |
Me too, but the tip about the local proxy is not mirrored into WSL still appears.And can't |
I changed the inbound rules of the Clash for windows in firewall, that does work in Ubuntu 20. |
|
You can |
Try deleting the Linux distribution and reinstalling it. |
Windows Version
Microsoft Windows [Version 10.0.22631.2715]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu20.04
Other Software
No response
Repro Steps
.wslconfig
:wsl --shutdown
to stop WSL7890
in clash for windows and open system proxyExpected Behavior
Both WSL and Windows can successfully access
google.com
(banned in my place) by curlActual Behavior
curl google.com
succeededcurl google.com
failedDiagnostic Logs
The text was updated successfully, but these errors were encountered: