Live-share: Visual Studio Live Share was unable to download needed dependencies

[rtumac]

Product and Version [VS/VSCode]: VS Code 1.24.1
OS Version [macOS/Windows]: Windows
Live Share Extension Version: 0.3.319
Target Platform or Language [e.g. Node.js]:

Steps to Reproduce / Scenario:

1. Install the Live Share extension
2. Click Reload button

After reload the following error message is displayed:

Visual Studio Live Share was unable to download needed dependencies to finish installation. Ensure you have network connectivity and restart VS Code to retry.

[lostintangent]

@rtumac Hey! This typically indicates you're behind a firewall/proxy that has blocked access to domains that Live Share downloads its dependencies from. Could you confirm whether you're able to access download.microsoft.com:443 from a browser? If not, that would seem to be the issue.

Otherwise, could you run the Live Share: Export Logs command and attach the resulting zip to this issue? Thanks!

[akanieski]

Also, how can they configure VSCode to use the corporate proxy? Or does it just use the proxy settings defined in IE?

[Chuxel]

@rtumac @akanieski If you are behind a proxy, you can check out https://aka.ms/vsls-docs/proxy for more information. 0.3.319 attempts to auto-detect, but if this fails you can set a couple of environment variables.

[rtumac]

Fixed after I set HTTP_PROXY and HTTPS_PROXY environment variables globally.

[worc4021]

I have the same issue and I don't sit behind a proxy. This only happens on my Windows 10 desktop, on my Windows 7 laptop it works fine. Both are connected to the same network.

[schovi]

I am getting the same error. I have OSX Mojave, VS Code Insider. I am trying different networks with the same result. One of them is my home, other in work and even mobile network.

[lensonsaldanha]

Same error here, Windows 10

[redenz]

For Mac users that have Little Snitch installed check your rules. I had a rule I didn't remember setting that was causing this error

[bera5186]

Same here for ubuntu 18.04

[TheDevMinerTV]

Same here for Linux Mint 19.

[maorjuela73]

Same here for Win10, I'm not using a proxy. Any idea about how to fix this? I tried to access http://download.microsoft.com:443/ but it failed.

[crummy]

Try https://download.microsoft.com - does that work?

[borgdylan]

Same issue on Ubuntu 19.04. Even if going to download.microsoft.com works.

[petergi]

I was experiencing the same issue on macOS Mojave but thanks to the suggestion above (looking at the logs), was able to get it to work. Your best bet is to `rm -rf '/Users/whatever/.vscode/extensions/ms-vsliveshare.vsliveshare-audio-X.X.XX' and then restart vscode. It should give it the kick in the pants it needs. Well, it did for me. Hope this helps... someone.

[polyglotdev]

@petergi I literally just filed an issue with that same fix!
https://github.com/MicrosoftDocs/live-share/issues/2475

[theblang]

@Chuxel I think this issue might need to be reopened. My coworker and I (as well as a couple other users reporting here) are running into this without a proxy involved. I did the fix mentioned by @petergi , but have now run into the issue again; I think after a VSCode update.

macOS Mojave 10.14.6
VSCode 1.38.0
Live Share Audio 0.1.64

[mwtrigg]

I have the same issue - I can hit the website without an issue, but my suspcion is that the problem is that when doing so, I am presented with an internally-signed certificate (to allow for SSL inspection by the transparent proxy) -- essentially a bona-fide man-in-the-middle.

[mwtrigg]

Suspicion confirmed. I was able to download the files after I was able to get the extension to trust the Windows trusted roots (by installing extension "win-ca")

[SemenovA1exander]

Same here and I can't access download.microsoft.com:443

[psakievich]

same issue here. No proxy being run right now.

MacOS 10.14.6
VScode 1.43.2

I can access https://downloads.microsoft.com from a browser but not http://download.microsoft.com:443/.
I tried from a personal computer as well and could not access this site.

I've also tried removing the extensions files from ~/.vscode.extensions but with no change in behavior