Skip to content
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

Closed
costas90 opened this issue Aug 28, 2019 · 11 comments
Closed

Firewall settings prevent connecting to WSL #1304

costas90 opened this issue Aug 28, 2019 · 11 comments
Assignees
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) wsl Issue in vscode-remote WSL

Comments

@costas90
Copy link

costas90 commented Aug 28, 2019

  • VSCode Version: 1.37.1
  • Local OS Version: Windows 10, version 1903
  • Remote OS Version:
  • Remote Extension/Connection Type: WSL

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.

Capture3

What am I missing?

Steps to Reproduce:

  1. Run 'code .' in Ubuntu Bash
  2. New VS Code window opens but gives the error "Failed to connect to the remote extension host server (Error: connect ETIMEDOUT 127.0.0.1:51072)"

Capture1

Capture

@costas90
Copy link
Author

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..

Capture5

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?

#1137 (comment)

@costas90
Copy link
Author

I tried running this from the Insiders V. 1.38

In stable VS Code I cant get the log, but in Insiders I can,, here it is:

Capture6

@aeschli aeschli added the wsl Issue in vscode-remote WSL label Sep 3, 2019
@aeschli aeschli self-assigned this Sep 3, 2019
@aeschli
Copy link
Contributor

aeschli commented Sep 3, 2019

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?
Can you also try the other IPs listed and http://localhost:50902/version?

@costas90
Copy link
Author

costas90 commented Sep 4, 2019

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.

@mikeweltevrede
Copy link

I have the same issue but I am unable to roll back to a previous Windows version. Any solutions?

@mikeweltevrede
Copy link

Following #927 (comment), I noticed that it was indeed my antivirus software as well (AVG, for those wondering)

@costas90
Copy link
Author

costas90 commented Sep 4, 2019

@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/

@costas90
Copy link
Author

costas90 commented Oct 1, 2019

@mikeweltevrede did you manage to make this work with your antivirus?

My windows were auto-updated and I have this problem again..

@mikeweltevrede
Copy link

@costas90 it is working only if I turn off my virus control before starting VS Code, unfortunately

@calevans
Copy link

Anyone find a way around this that does not involve shutting down antivirus firewall?

@aeschli aeschli changed the title Failed to connect to the remote extension host server (Error: connect ETIMEDOUT 127.0.0.1:51072) Firewall settings prevent connecting to VM Oct 29, 2019
@aeschli aeschli changed the title Firewall settings prevent connecting to VM Firewall settings prevent connecting to WSL Oct 29, 2019
@aeschli
Copy link
Contributor

aeschli commented Oct 29, 2019

Closing as a WSL issue. Please file against https://github.com/microsoft/WSL/issues

@aeschli aeschli closed this as completed Oct 29, 2019
@aeschli aeschli added the upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) label Oct 29, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) wsl Issue in vscode-remote WSL
Projects
None yet
Development

No branches or pull requests

4 participants