Vscode-remote-release: Remote ssh extension won't work on latest insiders

[derekriemer]

Issue Type: Bug

1. try to connect to ssh using an agent.

Actual: Vscode shows that everything failed from an authentication failure, then, initiates the agent, but throws away the result. I'm using a custom agent from work that does fancy things with security keys.

VS Code version: Code - Insiders 1.45.0-insider (2225d77536d12fea2eda04930f431a5eb0930bba, 2020-04-09T09:22:11.706Z)
OS version: Windows_NT x64 10.0.18362
Fetching remote diagnostics for 'SSH' failed: Connecting with SSH timed out

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz (4 x 2904)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.84GB (7.75GB free)|
|Process Argv||
|Screen Reader|yes|
|VM|0%|

Fetching remote diagnostics for 'SSH' failed: Connecting with SSH timed out

Extensions (3)

Extension|Author (truncated)|Version
---|---|---
remote-ssh|ms-|0.51.0
remote-ssh-edit|ms-|0.51.0
debugger-for-chrome|msj|4.12.6

[derekriemer]

This could be the remote extension, but it just started happening after todays insiders update.

[tomaxsas]

same here on WIndows 10 latest

[brbecker]

It seems like something is blocking. As soon as the timeout occurs, the normal connection output from the server appears in the Terminal window, but the extension has already given up. Tried increasing the timeout with no impact.

[roblourens]

Can someone share the log from the Remote-SSH output channel?

[malonnnn]

https://pastebin.com/raw/K4RMRWVr

[brbecker]

[13:15:40.388] Log Level: 2
[13:15:40.420] [email protected]
[13:15:40.420] win32 x64
[13:15:40.423] SSH Resolver called for "ssh-remote+uinf9690t", attempt 1
[13:15:40.424] SSH Resolver called for host: uinf9690t
[13:15:40.425] Setting up SSH remote "uinf9690t"
[13:15:40.501] Using commit id "2225d77536d12fea2eda04930f431a5eb0930bba" and quality "insider" for server
[13:15:40.505] Install and start server if needed
[13:15:40.542] Checking ssh with "ssh -V"
[13:15:40.559] Got error from ssh: spawn ssh ENOENT
[13:15:40.559] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[13:15:40.566] Got error from ssh: spawn C:\WINDOWS\System32\OpenSSH\ssh.exe ENOENT
[13:15:40.567] Checking ssh with "C:\Program Files\Git\usr\bin\ssh.exe -V"
[13:15:40.887] > OpenSSH_8.2p1, OpenSSL 1.1.1d 10 Sep 2019
[13:15:40.894] Using SSH config file "C:\Users\bbecke01.ssh\config"
[13:15:40.894] Running script with connection command: "C:\Program Files\Git\usr\bin\ssh.exe" -T -D 62082 -F "C:\Users\bbecke01.ssh\config" uinf9690t bash
[13:15:40.903] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[13:15:57.903] Resolver error: Connecting with SSH timed out
[13:15:57.917] ------

[13:15:59.657] >
[13:15:59.658] Got some output, clearing connection timeout
[13:16:00.140] > Error connecting to agent: No such file or directory

2783c1cc1508: running

[13:16:00.175] > Acquiring lock on /home/bbecke01/.vscode-server-insiders/bin/2225d77536d12fea2eda04930f431a5
eb0930bba/vscode-remote-lock.bbecke01.2225d77536d12fea2eda04930f431a5eb0930bba
\ln /home/bbecke01/.vscode-server-insiders/bin/2225d77536d12fea2eda04930f431a5eb0930bba/vsco
de-remote-lock.bbecke01.2225d77536d12fea2eda04930f431a5eb0930bba.target /home/bbecke01/.vsco
de-server-insiders/bin/2225d77536d12fea2eda04930f431a5eb0930bba/vscode-remote-lock.bbecke01.
2225d77536d12fea2eda04930f431a5eb0930bba

[13:16:00.201] > Found existing installation at /home/bbecke01/.vscode-server-insiders/bin/2225d77536d12fea2e
da04930f431a5eb0930bba...

[13:16:00.242] > 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)
  *

Checking server status on port 37091 with wget
2783c1cc1508: start
sshAuthSock==/home/bbecke01/.ssh/ssh_auth_sock==
agentPort==37091==
osReleaseId==rhel==
arch==x86_64==
webUiAccessToken====
tmpDir==/run/user/48910==
platform==linux==
2783c1cc1508: end

[yanggehua]

I am also experiencing the same issue:

Here is the output from 1.45-insiders build. I have no idea why it has all the escape characters. The same remote connection on 1.44 has clean output.

[10:14:11.831] Log Level: 1
[10:14:11.835] [email protected]
[10:14:11.835] win32 x64
[10:14:11.836] SSH Resolver called for "ssh-remote+dell", attempt 1
[10:14:11.837] SSH Resolver called for host: dell
[10:14:11.837] Setting up SSH remote "dell"
[10:14:11.853] Using commit id "c12bd56a8886f31e353a45f5846f0a35a52f908e" and quality "insider" for server
[10:14:11.854] Install and start server if needed
[10:14:11.856] Checking ssh with "ssh -V"
[10:14:11.892] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[10:14:11.893] Using SSH config file "C:\Gehua\credentials\config"
[10:14:11.893] Running script with connection command: ssh -T -D 49988 -F "C:\Gehua\credentials\config" dell bash
[10:14:11.895] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[10:14:23.896] Resolver error: Connecting with SSH timed out
[10:14:23.898] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"Timeout","askedPw":"0","askedPassphrase":"0","asked2fa":"0","askedHostKey":"0","gotUnrecognizedPrompt":"0","remoteInConfigFile":"1"},"measures":{"resolveAttempts":1,"retries":1}}
[10:14:23.898] ------




[10:14:24.180] "install" terminal received data: "[?25l






















]0;C:\WINDOWS\System32\cmd.exe[?25h[?25l






















[?25h"
[10:14:24.181] Got some output, clearing connection timeout
[10:14:24.576] "install" terminal received data: "[?25l










[?25h"
[10:14:24.972] "install" terminal received data: "[?25l96266df2cd31: running
[?25h"
[10:14:25.018] "install" terminal received data: "[?25lAcquiring lock on /home/garyyang/.vscode-server-insiders/bin/c12bd56a8886f31e353a45f5846f0a35a52f908e/vsco
de-remote-lock.garyyang.c12bd56a8886f31e353a45f5846f0a35a52f908e
[?25h"
[10:14:25.027] "install" terminal received data: "[?25l\ln /home/garyyang/.vscode-server-insiders/bin/c12bd56a8886f31e353a45f5846f0a35a52f908e/vscode-remote-lock
.garyyang.c12bd56a8886f31e353a45f5846f0a35a52f908e.target /home/garyyang/.vscode-server-insiders/bin/c12bd
56a8886f31e353a45f5846f0a35a52f908e/vscode-remote-lock.garyyang.c12bd56a8886f31e353a45f5846f0a35a52f908e  
[?25h"
[10:14:25.036] "install" terminal received data: "[?25lFound existing installation at /home/garyyang/.vscode-server-insiders/bin/c12bd56a8886f31e353a45f5846f0a35
a52f908e...
[?25h"
[10:14:25.056] "install" terminal received data: "[?25lFound running server...
[?25h[?25l
*
* Reminder: You may only use this software with Visual Studio family products,[?25h[?25l
* as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)[?25h[?25l
*[?25h[?25l
[?25h"
[10:14:25.064] "install" terminal received data: "[?25l

[?25h"
[10:14:25.070] "install" terminal received data: "[?25lChecking server status on port 42911 with wget[?25h[?25l

[?25h"
[10:14:25.080] "install" terminal received data: "[?25l96266df2cd31: start[?25h[?25l
sshAuthSock====[?25h[?25l
agentPort==42911==[?25h[?25l
osReleaseId==ubuntu==[?25h[?25l
arch==x86_64==[?25h[?25l
webUiAccessToken====[?25h[?25l
tmpDir==/run/user/15734==[?25h[?25l
platform==linux==[?25h[?25l
96266df2cd31: end[?25h[?25l

[?25h"
[10:17:25.087] "install" terminal received data: " "

[yanggehua]

Corresponding output from 1.44 (working):

[10:14:24.440] Log Level: 2
[10:14:24.445] [email protected]
[10:14:24.445] win32 x64
[10:14:24.447] SSH Resolver called for "ssh-remote+dell", attempt 1
[10:14:24.447] SSH Resolver called for host: dell
[10:14:24.447] Setting up SSH remote "dell"
[10:14:24.480] Using commit id "2aae1f26c72891c399f860409176fe435a154b13" and quality "stable" for server
[10:14:24.481] Install and start server if needed
[10:14:24.485] Checking ssh with "ssh -V"
[10:14:24.519] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[10:14:24.521] Using SSH config file "c:\gehua\credentials\config"
[10:14:24.522] Running script with connection command: ssh -T -D 50002 -F "c:\gehua\credentials\config" dell bash
[10:14:24.525] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[10:14:24.588] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ]0;C:\WINDOWS\System32\cmd.exe
[10:14:24.588] Got some output, clearing connection timeout
[10:14:24.599] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
[10:14:25.082] > da6130e5a986: running
> 
[10:14:25.115] > Acquiring lock on /home/garyyang/.vscode-server/bin/2aae1f26c72891c399f860409176
> fe435a154b13/vscode-remote-lock.garyyang.2aae1f26c72891c399f860409176fe435a154b1
> 3
> 
[10:14:25.123] > \ln /home/garyyang/.vscode-server/bin/2aae1f26c72891c399f860409176fe435a154b13/v
> scode-remote-lock.garyyang.2aae1f26c72891c399f860409176fe435a154b13.target /home
> /garyyang/.vscode-server/bin/2aae1f26c72891c399f860409176fe435a154b13/vscode-rem
> ote-lock.garyyang.2aae1f26c72891c399f860409176fe435a154b13
> Found existing installation at /home/garyyang/.vscode-server/bin/2aae1f26c72891c
> 399f860409176fe435a154b13...
> 
[10:14:25.149] > SSH_CONNECTION=172.30.93.73 50004 172.29.80.132 22    
> LANG=en_US.UTF-8
> OLDPWD=/home/garyyang
> XDG_SESSION_ID=1278
> USER=garyyang
> PWD=/home/garyyang
> HOME=/home/garyyang
> SSH_CLIENT=172.30.93.73 50004 22
> MAIL=/var/mail/garyyang
> SHELL=/usr/bin/zsh
> SHLVL=1
> VSCODE_AGENT_FOLDER=/home/garyyang/.vscode-server     
> LOGNAME=garyyang
> DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/15734/bus
> XDG_RUNTIME_DIR=/run/user/15734
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/us
> r/local/games
> _=/usr/bin/printenv
> Starting server with command... /home/garyyang/.vscode-server/bin/2aae1f26c72891
> c399f860409176fe435a154b13/server.sh --host=127.0.0.1 --enable-remote-auto-shutd
> own  --port=0 &> "/home/garyyang/.vscode-server/.2aae1f26c72891c399f860409176fe4
> 35a154b13.log" < /dev/null
> Waiting for server log...
[10:14:25.160] > 
> 
[10:14:25.667] >  
> *
> * Reminder: You may only use this software with Visual Studio family products,  
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057) 
> *
> 
> 
[10:14:25.765] > da6130e5a986: start
> sshAuthSock====
> agentPort==41277==
> osReleaseId==ubuntu==
> arch==x86_64==
> webUiAccessToken====
> tmpDir==/run/user/15734==
> platform==linux==
[10:14:25.770] > 
> da6130e5a986: end
> 
[10:14:25.771] Received install output: 
sshAuthSock====
agentPort==41277==
osReleaseId==ubuntu==
arch==x86_64==
webUiAccessToken====
tmpDir==/run/user/15734==
platform==linux==

[10:14:25.772] Remote server is listening on port 41277
[10:14:25.772] Parsed server configuration: {"agentPort":41277,"osReleaseId":"ubuntu","arch":"x86_64","webUiAccessToken":"","sshAuthSock":"","tmpDir":"/run/user/15734","platform":"linux"}
[10:14:25.774] Starting forwarding server. localPort 50009 -> socksPort 50002 -> remotePort 41277
[10:14:25.776] Forwarding server listening on 50009
[10:14:25.776] Waiting for ssh tunnel to be ready
[10:14:25.777] [Forwarding server 50009] Got connection 0
[10:14:25.778] Tunneled remote port 41277 to local port 50009
[10:14:25.779] Resolved "ssh-remote+dell" to "127.0.0.1:50009"
[10:14:25.789] ------




[10:14:25.818] [Forwarding server 50009] Got connection 1
[10:14:25.819] [Forwarding server 50009] Got connection 2
[10:14:26.428] [Forwarding server 50009] Got connection 3
[10:14:26.429] [Forwarding server 50009] Got connection 4
[10:14:30.311] [Forwarding server 50009] Got connection 5
[10:14:30.312] [Forwarding server 50009] Got connection 6

[roblourens]

Fixed in https://github.com/microsoft/vscode/commit/44c5185373d5f209cd6c0b5d29a216fb801da34e

I will try to get an Insiders release out today but I'm having other unrelated build issues.

[roblourens]

In the meantime, you can use vscode Stable

[roblourens]

Ok, I released an Insiders build that should fix this. Sorry!