Live-share: [VS Code] An error occurred while sending the request.

[jonathonpday]

Untitled.zip

Error:

An error occurred while sending the request.

Steps to Reproduce:

1. Try to set up VS code live
2. Will create error on VS editor after confirmation connection established online.

||Version Data|
|-:|:-|
|extensionName|VSLS|
|extensionVersion|0.3.319|
|protocolVersion|2.2|
|applicationName|VSCode|
|applicationVersion|1.24.1|
|platformName|MacOS|
|platformVersion|17.4.0|

[jonathonpday]

I have been trying to run VS Live Share but every time I log on via Github a notice appears on the editor telling me the request has failed. I see no obvious reason why this would occur and would really value any help.

[jramsay]

Thanks for letting us know about this issue (and attaching the logs!). We'll take a look and will get back to you shortly.

[jramsay]

@jonathonpday : were you able to use VS Live Share successfully before the latest update to our VS Live Share extension? Or is this the first time you've used the extension and have never been able to log in successfully?

[jonathonpday]

Hi @jramsey,

Yes I was able to use the live share and had done so about 2 weeks ago.

However, will not work at all since last update 2 days ago.

[jramsay]

@jonathonpday: Thanks for the info! From the logs it looks like it is either a proxy or curl issue. Would you be able to run the following from a cmd prompt: "curl -version" and send us the result.

@Priya91 to investigate proxy issues further

[Priya91]

From your logs, looks like there's proxy set with the configuration url,

[2018-06-22 14:53:53.438 Agent.Proxy I] Reading proxy from auto configuration url.
[2018-06-22 14:53:53.445 Agent.Proxy I] Reading proxy from auto configuration url.

Are you aware that you are behind a proxy? In your SystemPreferences, search for Proxy, and check if any proxy has been set with auto config url, otherwise, it seems like someone has set this script on your dhcp or dns a servers.

Can you also please try running the request with curl directly. Curl doesn't support pac files, so once you identify what proxy you are behind specify that in the commandline below

curl -x proxy:port https://insiders.liveshare.vsengsaas.visualstudio.com

and then, in your browser too, try accessing https://insiders.liveshare.vsengsaas.visualstudio.com.

[jonathonpday]

@jramsay @Priya91

Hi Guys, thank you for your advice. I went onto system preferences as advised and saw that under network -> Proxies the box "Automatic Proxy Configuration" was selected; no other ones. I clicked the box off and tried Live Share again...and it now works!

Not quite sure how that box became selected or why but the situation appears to be resolved for this issue. Would there be anything else I need to do or be aware of in your opinion?

Thank you again for the help.

Cheers,

Jonathon

[Priya91]

Not quite sure how that box became selected or why but the situation appears to be resolved for this issue.

We recently added support to Live Share to use a proxy if the user has set the "Automatically detect proxy settings" option in their OS preferences. Looks like you didn't want proxy to use proxy, if you are using the corporate network, double check with your network admin, if they require you to connect via a proxy.

[Lewih]

logs.zip
@setaskin here the logs.

[setaskin]

@Lewih Thank you for sending the logs. Looks like it is proxy or curl issue. @Priya91 to investigate the issue further.

[Priya91]

@Lewih Did you try the solution commented before here

[Lewih]

Solved. Automatic Proxy Research was turned-on in system preferences. Thanks for help!

[Priya91]

I've implemented a workaround, to ignore the proxy in automatic detection, if the connection with it failed. Should be available in the next release, and these errors should not be observed even with the OS System Preference set to automatically detect proxy.

@Chuxel Would it be possible to get this tested before release, by maybe giving a privately built extension to one of the customers here? Since I'm not able to repro this exact situation locally, I want to make sure this fix actually works and doesn't break other things.

[lostintangent]

@jonathonpday Are you still hitting this issue, or did one of our updates unblock you? If you could update to the latest Live Share extension, and let us know how it goes, that would be greatly appreciated! In the meantime, I’m going to close this as a duplicate of #447, so we can consolidate the discussion. Thanks!