-
Notifications
You must be signed in to change notification settings - Fork 282
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
Firewall settings prevent connecting to WSL #1304
Comments
I tried rolling back VS Code to 1.36.1 and I get similar errors. Similar errors and it says it cannot connect to the extensions marketplace.. In another thread people talk about removing the () from the hostname, but I am not sure where to locate this. Or is that not relevant to WSL? |
The server seems to be running as the log shows When you open a browser on http://127.0.0.1:50902/version, does that work? |
I ended up rolling back the Windows version from 1903 to 1803 and now it works. I did try visiting those URLs but did not work. |
I have the same issue but I am unable to roll back to a previous Windows version. Any solutions? |
Following #927 (comment), I noticed that it was indeed my antivirus software as well (AVG, for those wondering) |
@mikeweltevrede you can roll back windows if no more than 10 days have past since the upgrade. https://pureinfotech.com/uninstall-windows-10-1903-may-2019-update/ |
@mikeweltevrede did you manage to make this work with your antivirus? My windows were auto-updated and I have this problem again.. |
@costas90 it is working only if I turn off my virus control before starting VS Code, unfortunately |
Anyone find a way around this that does not involve shutting down antivirus firewall? |
Closing as a WSL issue. Please file against https://github.com/microsoft/WSL/issues |
This problem appeared today after updating Windows to version 1903. Also, when I disable the firewall from Avast Antivirus it works!
But I dont know how to fix the issue because I want the firewall enabled at all times..
In the firewall logs, it seems that svchost.exe is related, but checking the application rules, all connections are allowed.
What am I missing?
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: