Remote SSH fails to connect to remote server on 1.38.0-insider

[jmdacruz]

This looks similar to #1137, but still different enough. From what I can see on the logs, there seems to be a port number missing on the install output (it shows 5809a992-6d03-4482-84e8-1839a468bde5==33493====ubuntu==, but from other examples I think it should show something like 5809a992-6d03-4482-84e8-1839a468bde5==33493==XXXXX==ubuntu==, with XXXXX being a different port number)

• VSCode Version: 1.38.0-insider
• Local OS Version: macos 10.14.6 (Darwin x64 18.7.0)
• Remote OS Version: Ubuntu 16.04.6 LTS
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Launch a remote that was previously working
2. Connection cannot be established (See output below)
3. Delete the .vscode-server-insiders folder on the remote target and retry
4. Issue still persists

Does this issue occur when you try this locally?: No, only with remote
Does this issue occur when you try this locally and all extensions are disabled?: No

[18:57:26.487] remote-ssh@0.45.5
[18:57:26.487] darwin x64
[18:57:26.488] SSH Resolver called for "ssh-remote+7b22686f73744e616d65223a22446576656c6f706d656e74227d", attempt 1
[18:57:26.488] SSH Resolver called for host: Development
[18:57:26.488] Setting up SSH remote "Development"
[18:57:26.495] Using commit id "366e1b275cf01e2d50e96083dede553de608b078" and quality "insider" for server
[18:57:26.499] Testing ssh with ssh -V
[18:57:26.520] ssh exited with code: 0
[18:57:26.520] Got stderr from ssh: OpenSSH_7.9p1, LibreSSL 2.7.3
[18:57:26.520] Running script with connection command: ssh -o ClearAllForwardings=true -o ConnectTimeout=15 Development bash
[18:57:26.520] Install and start server if needed
[18:57:27.346] > Running remote connection script
[18:57:27.347] Got some output, clearing connection timeout
[18:57:27.349] > Acquiring lock on /home/appsadm/.vscode-server-insiders/bin/366e1b275cf01e2d50e96083dede553de608b078/vscode-remote-lock.366e1b275cf01e2d50e96083dede553de608b078
[18:57:27.355] > Found existing installation at /home/appsadm/.vscode-server-insiders/bin/366e1b275cf01e2d50e96083dede553de608b078...
[18:57:27.396] > Found running server...
>  
> *
> * Reminder: You may only use this software with Visual Studio family products,
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
>  
[18:57:27.403] > Checking server status on port 33493 with wget
[18:57:27.409] > 5809a992-6d03-4482-84e8-1839a468bde5==33493====ubuntu==
[18:57:27.409] Received install output: 5809a992-6d03-4482-84e8-1839a468bde5==33493====ubuntu==
[18:57:27.409] Failed to parse remote port from server output: 5809a992-6d03-4482-84e8-1839a468bde5==33493====ubuntu==
[18:57:27.410] 
[18:57:27.410] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[18:57:27.410] ------




[18:57:27.881] "install" terminal command done
[18:57:27.881] Install terminal quit with output: 

[jmoses-ds]

I'm seeing this exact same thing that occurred immediately after I updated to the 1.38 insiders version.

Version: 1.38.0-insider
Commit: 366e1b275cf01e2d50e96083dede553de608b078
Date: 2019-08-22T10:49:36.487Z
Electron: 4.2.9
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.5.0

[jmoses-ds]

Using the nightly SSH extension did not resolve the issue, although the output to

[19:19:31.952] > Checking server status on port 40661 with wget
[19:19:31.984] > 2ab4e582-d605-4e5f-9ca9-98014cd0b55e: start
> agentPort==40661==
> webViewServerPort====
> osReleaseId==ubuntu==
> webUiAccessToken====
> 2ab4e582-d605-4e5f-9ca9-98014cd0b55e: end
[19:19:31.984] Received install output: 
agentPort==40661==
webViewServerPort====
osReleaseId==ubuntu==
webUiAccessToken====

[19:19:31.985] Failed to parse remote port from server output: 
agentPort==40661==
webViewServerPort====
osReleaseId==ubuntu==
webUiAccessToken====

[19:19:31.985] 
[19:19:31.985] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[19:19:31.986] ------

[oviava]

Exact same issue

[jmoses-ds]

Going back to 1.37 official makes everything work again.

[russhughes]

Same issue here. I'll try 1.37 official.

[cmeans]

Downloaded 1.37 and am having the exact same issue. What steps did you follow that worked?

[darkvertex]

I'm on 1.38.0-insider and having the same exact issue. 🤔

I had used the remote ssh extension with success in the past.

[cmeans]

There was an update today that made it barf.

[ritzz32]

I am getting the same thing on 1.38. Switching over to stable on 1.37.1 has fixed the issue for me.

[Lunyyx]

Same problem here, i think this is an error by the devs...

[roblourens]

The latest extension update should fix it, sorry! #1232