Live-share: [VS Code] Sharing workspace: Could not connect to the server. Check that you are connected to the internet.

[yoann54]

Error:

Sharing workspace: Could not connect to the server. Check that you are connected to the internet.

Steps to Reproduce:

1.
2.

||Version Data|
|-:|:-|
|extensionName|VSLS|
|extensionVersion|0.3.869|
|protocolVersion|2.2|
|applicationName|VSCode|
|applicationVersion|1.28.2|
|platformName|Linux|
|platformVersion|4.18.16-96.current|

[Moniarchy]

Hi there,
Are you behind a corporate proxy? If so, see here: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#proxies

If this doesn't solve your problem, please let me know. Also, please attach your logs to this issue or email them to [email protected]. You can get your logs by running the "Live Share: Export Logs" command in VS Code.

[cwebster2]

I also have this issue with the current up-to-date versions of code-insiders for Linux (Linux 4.18.10 Debian Sid) and the up-to-date version of the live share extension.

I am not behind a proxy. My IPV4 network is behind NAT but this machine also has globally routable IPV6 addressing.

The relevant bit of the logs appears to be:

[2018-11-06 03:31:50.436 Client.Rpc.Auth V] < auth.login()
[2018-11-06 03:31:50.725 Client.Rpc V] > telemetry.genericOperation:
[2018-11-06 03:31:50.734 Client.Rpc.Auth E] > auth.login() error: Error: The SSL connection could not be established, see inner exception.
at new ResponseError (/home/casey/.vscode-insiders/extensions/ms-vsliveshare.vsliveshare-0.3.897/node_modules/vscode-jsonrpc/lib/messages.js:46:28)
at handleResponse (/home/casey/.vscode-insiders/extensions/ms-vsliveshare.vsliveshare-0.3.897/node_modules/vscode-jsonrpc/lib/main.js:430:48)
at processMessageQueue (/home/casey/.vscode-insiders/extensions/ms-vsliveshare.vsliveshare-0.3.897/node_modules/vscode-jsonrpc/lib/main.js:258:17)
at Immediate._onImmediate (/home/casey/.vscode-insiders/extensions/ms-vsliveshare.vsliveshare-0.3.897/node_modules/vscode-jsonrpc/lib/main.js:242:13)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
at processImmediate [as _immediateCallback] (timers.js:722:5)
[2018-11-06 03:31:50.735 Command:Object I] SessionContext: State update from "SigningIn" to "SignedOut".
[2018-11-06 03:31:50.735 Command:Object I] Decorator: Authentication Completed Failed (12602ms abs=12594ms pre=-20215ms post=32809)
[2018-11-06 03:31:50.735 Command:Object I] Decorator: SessionStateTransitions Completed Failed (12602ms abs=0ms pre=0ms post=0)
[2018-11-06 03:31:50.735 Command:Object I] Decorator: Progress Completed Failed (12604ms abs=2ms pre=2ms post=0)
[2018-11-06 03:31:50.735 Command:Object I] Decorator: Validation Completed Failed (12604ms abs=0ms pre=0ms post=0)
[2018-11-06 03:31:50.735 Command:Object I] Decorator: TelemetryStatus Completed Failed (12605ms abs=1ms pre=1ms post=0)
ms)

and the inner exception here is:

[2018-11-06 03:31:50.707 Agent V] < #1 {Name=telemetry.genericOperation Arguments={EventName=complete-httprequest Result=Failure}}
[2018-11-06 03:31:50.721 Agent.Rpc.Auth E] HTTP exception in auth.login request handler: System.Net.Http.HttpRequestException: The SSL connection could not be
established, see inner exception. ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> System.TypeInit
ializationException: The type initializer for 'SslMethods' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Ssl' threw an
exception. ---> System.TypeInitializationException: The type initializer for 'SslInitializer' threw an exception. ---> Interop+Crypto+OpenSslCryptographicExce
ption: error:0E076071:configuration file routines:MODULE_RUN:unknown module name
at Interop.SslInitializer..cctor()
--- End of inner exception stack trace ---
at Interop.Ssl..cctor()
--- End of inner exception stack trace ---
at Interop.Ssl.SslV2_3Method()
at Interop.Ssl.SslMethods..cctor()
--- End of inner exception stack trace ---

I'm emailing my logs to the email vsls-feedback address.

[cwebster2]

After further troubleshooting, this appears to be a bug in the dotnet runtime. See this issue in the dotnet/corefx repo: https://github.com/dotnet/corefx/issues/33179 which describes incompatibilities between dotnet and newer ssl libraries (introduced in debian 10 / testing).

Editing the file /etc/ssl/openssl.cnf and commenting out the line suggested in that issue, then restarting vs code allows vsls to operate. This is undesirable as it bypasses security choices made by the OS, but it is a workaround.

Ultimately, this isn't your bug, its dotnets, but this is certainly an example of its impact and perhaps having a microsoft extension impacted will convince the dotnet team to fix their stuff. Please do pass this along to them.

[srivatsn]

@cwebster2 thanks for finding the corefx issue!

[srivatsn]

@Priya91 we should probably detect this situation and output some meaningful error until .NET Core supports openssl 1.1 (which seems to be 3.0)

[nickray]

Perhaps add this to https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux#tips-by-distribution?

[Priya91]

@Chuxel Can we please the data about requiring openssl 1.0 for liveshare to work in our docs..

[Chuxel]

@Priya91 Yep. Added links to the .NET Core issue and workaround comment in that section.

[Priya91]

Fix: Upgrade to .NET Core 3.0

[Priya91]

This is now fixed.