-
Notifications
You must be signed in to change notification settings - Fork 868
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
portproxy not systematically correctly configured for localhost #8707
Comments
same issue |
Any updates or fixes? Running netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=PORT connectaddress=localhost connectport=PORT
# or
netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=PORT connectaddress=0.0.0.0 connectport=PORT Don't work, unless I use the correct static IP, but WSL ips aren't static, meaning that I'll have to run this command on every wsl startup. I did a tempfix by setting WSL with a static ip. |
netsh interface portproxy add v4tov4 listenport=7860 listenaddress=0.0.0.0 connectport=7860 connectaddress=$(wsl hostname -I) But it doesnt always work... |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
cmd.exe /c ver
wsl.exe --status
lsb_release -r
I would like to mention the last comment from a closed issue although there is as of August 2022 still an issue with this:
See post by @rehantoday in #4636 (comment)_
The solution he or she quotes does work. We then need to manually add the proxy, e.g. doing
netsh interface portproxy set v4tov4 8080 172.24.133.133 8080 0.0.0.0
localhost forwarding should be automatic.
Last week, there was no such issues. It appeared randomly as mentioned in above closed issue by several people within this year 2022.
The text was updated successfully, but these errors were encountered: