Remote SSH fails to connect to remote server after VS Code update 1.37.0 #1137

Friksel · 2019-08-10T13:57:33Z

After VSCode update 1.37.0 the Remote/Remote SSH extension(s) cannot connect to the remote server anymore as was working before. As seen on two different machines both using windows host with vs code to connect to a VM running Ubuntu 18.04.

I have the latest upgrades of the extensions installed and did an extra check for updates, but it couldn't find any)

When swithing back to the 1.36.x version of VS Code everything works fine again with the same setup. And when switching to 1.37.0 after, again the problem is back again: can't make the connection working.

In the output it says twice: bash) was unexpected at this time..

I also tried uninstalling the vscode-server on the remote via vs code 'Remote-SSH: Uninstall VS Code Server from host', but that didn't seem to work as it exited with code 1.

So than I tried 'uninstalling' the vs code server by removing the vscode-server folder on the remote, but that didn't help connecting (and installing) from vs code later either.
There's no installation on the remote after this (no 'wget' and all that in the output and no re-creation of the vscode-server folder on the remote).

This is the full output I'm getting:

[13:36:36.030] remote-ssh@0.45.4
[13:36:36.030] win32 x64
[13:36:36.031] SSH Resolver called for "ssh-remote+7b22686f73744e616d65223a227562756e7475564d2d425f285562756e747531382e303429227d", attempt 1
[13:36:36.032] SSH Resolver called for host: uVM_(Ubuntu)
[13:36:36.032] Setting up SSH remote "uVM_(Ubuntu)"
[13:36:36.063] Using commit id "036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8" and quality "stable" for server
[13:36:36.069] Testing ssh with ssh -V
[13:36:36.392] ssh exited with code: 0
[13:36:36.392] Got stderr from ssh: OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
[13:36:36.392] Running script with connection command: ssh -o ClearAllForwardings=true ubuntuVM-B_(Ubuntu18.04) bash
[13:36:36.394] Install and start server if needed
[13:36:37.210] > bash) was unexpected at this time.
> 
[13:36:37.210] Got some output, clearing connection timeout
[13:36:37.641] "install" terminal command done
[13:36:37.641] Install terminal quit with output: bash) was unexpected at this time.
[13:36:37.641] Received install output: bash) was unexpected at this time.
[13:36:37.642] Failed to parse remote port from server output: bash) was unexpected at this time.
[13:36:37.642] 
[13:36:37.643] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[13:36:37.643] ------

versions

VSCode Version: 1.37.0
Local OS Version: Win 10 home up to date
Remote OS Version: Ubuntu 18.04
Remote Extension/Connection Type: SSH
Remote SSH Extension version: v0.45.4
Remote Development version: 0.16.0

Steps to Reproduce:

Open Vs Code and connect to existing remote

Does this issue occur when you try this locally?: ahum?!
Does this issue occur when you try this locally and all extensions are disabled?: ahum?!

The text was updated successfully, but these errors were encountered:

meteorlxy · 2019-08-12T02:16:20Z

Same issue here.

Everything worked well before this update.

Currently I have to downgrade to VS Code 1.36.1.

---- update

Fixed by removing the parens () in my hostname aliases, according to this comment by @roblourens

luanft · 2019-08-13T02:46:28Z

Same issue here.

Everything worked well before this update.

Currently I have to downgrade to VS Code 1.36.1.

I just tried it first time in VScode version 1.37.

captainfffsama · 2019-08-13T07:22:41Z

I have same problem here..and I have to downgrade to 1.36.1...
just use command ssh -o ClearAllForwardings=true ubuntuIP in vscode teminal,I can connect to my server,but Remote SSH seems to use the ssh -o ClearAllForwardings=true ubuntuIP bash...
obviously, there is no bash in windows and teminal tell me bash) was unexpected at this time

Ibrahim-Badwi · 2019-08-13T07:31:39Z

after updating to 1.37.0 the Remote-SSH extension stopped >

roblourens · 2019-08-16T00:40:43Z

This is probably due to the () in your ssh host name. I will have to quote them. Can you try without the parens?

Friksel · 2019-08-17T03:27:02Z

This is probably due to the () in your ssh host name. I will have to quote them. Can you try without the parens?

I removed the (), and also the underscore, but that didn't fix it.
The same name didn't have a problem in the previous version of VS Code (1.36.1).

roblourens · 2019-08-17T16:48:03Z

Can you share the output after that? You might see a different error now.

Friksel · 2019-08-17T17:57:42Z

Here it is:

[17:52:32.522] remote-ssh@0.45.5
[17:52:32.522] win32 x64
[17:52:32.523] SSH Resolver called for "ssh-remote+7b22686f73744e616d65223a2275564d423138227d", attempt 1
[17:52:32.523] SSH Resolver called for host: uVMB18
[17:52:32.523] Setting up SSH remote "uVMB18"
[17:52:32.527] Using commit id "036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8" and quality "stable" for server
[17:52:32.530] Testing ssh with ssh -V
[17:52:32.593] ssh exited with code: 0
[17:52:32.593] Got stderr from ssh: OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
[17:52:32.593] Running script with connection command: ssh -o ClearAllForwardings=true uVMB18 bash
[17:52:32.595] Install and start server if needed
[17:52:32.842] > 
[17:52:32.842] Got some output, clearing connection timeout
[17:52:33.349] > Running remote connection script
> Acquiring lock on /home/MYUSERNAME/.vscode-server/bin/036a6b
> 1d3ac84e5ca96a17a44e63a87971f8fcc8/vscode-remote-lock.0
> 36a6b1d3ac84e5ca96a17a44e63a87971f8fcc8
> Found existing installation at /home/MYUSERNAME/.vscode-serv
> er/bin/036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8...
> 
[17:52:33.398] > 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)
> *
> 
> 
[17:52:33.422] > Checking server status on port 39727 with wget
> 33e7478d-4718-4a63-b887-72899bb6b529==39727==43515==ubu
> ntu==
> 
[17:52:33.423] Received install output: 33e7478d-4718-4a63-b887-72899bb6b529==39727==43515==ubu
[17:52:33.423] Failed to parse remote port from server output: 33e7478d-4718-4a63-b887-72899bb6b529==39727==43515==ubu
[17:52:33.424] 
[17:52:33.424] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[17:52:33.425] ------




[17:52:33.761] "install" terminal command done
[17:52:33.761] Install terminal quit with output:

bondenn · 2019-08-17T18:33:49Z

I had the same issue, it was fixed by removing the ()'s from the hostname in the ssh configuration

roblourens · 2019-08-18T15:54:00Z

This shows the line wrapping at 56 characters, @Tyriar?

[17:52:33.422] > Checking server status on port 39727 with wget
> 33e7478d-4718-4a63-b887-72899bb6b529==39727==43515==ubu
> ntu==
>

Dayjo · 2019-08-19T10:26:10Z

I am also getting this issue, but I have no odd characters in my hostname. I'm trying to uninstall and re-install the Remote - SSH extension but I also get an 'unknown error' occur when I try.

I have removed the directories on the remote host and it started to re-install but then continued to error.

I closed everything, managed to uninstall all the remote ssh packages from vscode (insiders). I found that there were processes running on the remote host, so I killed all vscode related processes. Re-installed the plugin, reconnected and it seems to be working ok now.

rafipiccolo · 2019-08-19T13:19:16Z

Are you on windows >= 1903 ?
I think i tried everything. Still doesn't work

rafipiccolo · 2019-08-19T14:30:15Z

see #1152
in vscode settings :
search conpty
and uncheck it
Now it works. although i don't know what it means.

Dayjo · 2019-08-19T15:33:15Z

@rafipiccolo I'm on Mac OSX 10.14.6. Uninstalling and re-installing seemed to fix it for me, however, it failed several times.

Tyriar · 2019-08-19T23:42:15Z

This shows the line wrapping at 56 characters

I think this could happen if your window is particularly tiny and terminal is restored (there might be a race whether it happens or not).

dreamflasher · 2019-08-23T17:59:03Z

Same error here, on two different machines:

[17:56:48.106] Testing ssh with ssh -V
[17:56:48.106] ssh exited with code: 0
[17:56:48.106] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[17:56:48.109] Running script with connection command: ssh -o ClearAllForwardings=true df_ND40sv2 bash
[17:56:48.110] Install and start server if needed

Unchecking conpty did not help. Connecting to another remote vm works.

fseesink · 2019-08-28T21:53:06Z

I had this working previously, but am in the same boat. My challenge is it's been a bit so don't know if this is due to a change in VSCode, some update to OpenSSH, or what.

I originally followed the setup steps, creating SSH keys, putting them on the remote servers, and modifying my SSH config with the necessary info as the servers I connect to have SSH on a non-standard port. And it all worked great. But when this started happening, I eventually went online looking for help, and found this.

In my case, from two different machines (both macOS 10.14.6 with VSCode 1.37.1), when I now try to use the Remote-SSH extension to talk to remote RHEL7 systems, I'm prompted for a password (even though I have SSH keys setup), and no matter what I do, it fails.

[21:44:10.936] remote-ssh@0.45.6
[21:44:10.936] darwin x64
[21:44:10.937] SSH Resolver called for "ssh-remote+mysite", attempt 1
[21:44:10.937] SSH Resolver called for host: mysite
[21:44:10.937] Setting up SSH remote "mysite"
[21:44:10.939] Using commit id "f06011ac164ae4dc8e753a3fe7f9549844d15e35" and quality "stable" for server
[21:44:10.940] Testing ssh with ssh -V
[21:44:10.951] ssh exited with code: 0
[21:44:10.951] Got stderr from ssh: OpenSSH_7.9p1, LibreSSL 2.7.3
[21:44:10.951] Running script with connection command: ssh -o ClearAllForwardings=true -o ConnectTimeout=15 mysite bash
[21:44:10.952] Install and start server if needed
[21:44:11.064] > frank@mysite.full.fqdn's password:
[21:44:11.064] Got some output, clearing connection timeout
[21:44:15.869] "install" wrote data to terminal: "*********************"
[21:44:15.872] >
[21:44:17.452] > Permission denied, please try again.
[21:44:17.453] > frank@mysite.full.fqdn's password:
[21:44:18.366] "install" wrote data to terminal: ""
[21:44:18.369] >
[21:44:20.892] > Permission denied, please try again.
[21:44:20.893] > frank@mysite.full.fqdn's password:
[21:44:22.069] "install" terminal command canceled
[21:44:22.069] Install terminal quit with output:
[21:44:22.069] Received install output:
[21:44:22.070] Failed to parse remote port from server output:
[21:44:22.070]
[21:44:22.070] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[21:44:22.070] ------

Now from Terminal, everything still works fine. If I do ssh username@host where host is configured in the SSH config file and has things like the port set, I go right in. But from VSCode, not so much.

If anyone has any insight, I'm all ears.

scq000 · 2019-08-29T03:05:45Z

I have the same problem:

03:04:19.751] "install" terminal command done
[03:04:19.751] Install terminal quit with output: scq000@myhost's password:
[03:04:19.752] Received install output: scq000@myhost's password:
[03:04:19.752] Failed to parse remote port from server output: shic@myhost's password:
[03:04:19.752]
[03:04:19.753] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}

roblourens · 2019-08-30T03:16:13Z

This issue started with the extension not handling () in names correctly which is now fixed. Then the terminal wrapping issue which might be addressed by disabling remote.SSH.showLoginTerminal if it is set, @Friksel.

Then it is not obvious that other people are seeing the same issue. @fseesink please open a new issue. If you test it from another terminal make sure that you are trying to connect exactly the same as how vscode is. e.g. vscode is using mysite but you show using username@host.

@scq000 Not sure what's going on. Please open a new issue with the full log.

Friksel · 2019-08-30T17:09:28Z

Hey @roblourens , next to the issue I reported still not being fixed, there are obviously more people like me here having problems with this extension after upgrading to 1.37 and/or in combination with the latest version of the extension.

I helped you with this issue and gave answers to your questions and put valuable time of my daytime job in testing this over and over again (for hours really). And now, without this issue being fixed you just close this issue without any reason.

Because you just feel like closing it??? Without even asking me/us if it's fixed??

This way of communication/handling doesn't come accross as very professional and reliable to me. And to be honoust after months of all kinds of connection problems with this extension I'm starting to lose faith in this extension very quickly now. I think it's hard to believe this extension will ever become stable. Sometimes it works and suddenly it stops working again on and off everytime again.

Which really is a pitty, because I need it for my job badly and I like the whole idea of it and would also like to thank you guys for making this great extension. If it works. I know it's in preview still, but it's taking a very long time to make this stable obviously and it's taking me way too much time to fix the problems everytime for months now to be able to use it. Today I had to spent another few hours to make the connection work again, which NEVER returned for whatever reason. It's pretty random and feels very unreliable and delicate.
Eventhough it was working somewhat fine previously. It seems totally random when this extension has a connection and very very delicate.

Sorry, I am going to look for another solution now to be able to do my job. I can't rely on this extension unfortunately and it's taking way to long to become stable. And if you guys just close this problematic issues and act like it's fixed, than I don't believe chances are this will become a problemless extension in the future very soon. I'm sorry, I'm gonna look further for other options now.

malonnnn · 2019-08-30T19:40:04Z

chiming in, I too have the same issue

[19:39:16.824] "install" terminal command done
[19:39:16.825] Install terminal quit with output: 61b90089-48a5-4602-a91b-6edee3724b40==39229====ubuntu==
[19:39:16.825] Received install output: 61b90089-48a5-4602-a91b-6edee3724b40==39229====ubuntu==
[19:39:16.825] Failed to parse remote port from server output: 61b90089-48a5-4602-a91b-6edee3724b40==39229====ubuntu==
[19:39:16.825] 
[19:39:16.826] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[19:39:16.826] ------

roblourens · 2019-08-30T21:11:54Z

@Friksel, I apologize, this shouldn't have been closed. I thought I was waiting to hear back from you for something but actually you had answered my questions to date. I am tracking dozens of confusing issues every day and make mistakes. The other people in this issue are seeing different symptoms and I prefer that people open new issues because I get confused by the noise (and @malonnnn please open a new issue)

I'm still not sure what your issue is but if you are interested in trying one more thing, this may be fixed in the nightly build of the ssh extension. Find "Remote - SSH (Nightly)" in the marketplace (and uninstall the stable version). If you have set remote.SSH.showLoginTerminal, then disabling that might help too.

Friksel · 2019-09-03T18:08:59Z

@Friksel, I apologize, this shouldn't have been closed. I thought I was waiting to hear back from you for something but actually you had answered my questions to date. I am tracking dozens of confusing issues every day and make mistakes.

Alright. Thanks for your apologies and clearing that up. Apologies and I understand. For me it also had to do with problems I faced with using the plugin for some months now and it takes too much time for me to keep trying to work around them. And that's a pitty, because I really like this extension and it creates an important workflow in my job that would otherwise be a pain to do. So if the extension connects everything is fine, but when it doesn't connect for hours it's very frustrating, because than I literally cannot do my job. Although I understand it's still in preview and I understand you guys work very hard on this.

So thanks for re-opening the issue.

I'm still not sure what your issue is but if you are interested in trying one more thing, this may be fixed in the nightly build of the ssh extension. Find "Remote - SSH (Nightly)" in the marketplace (and uninstall the stable version). If you have set remote.SSH.showLoginTerminal, then disabling that might help too.

I was about to try the nightly build, but first I removed the showLoginTerminal setting I indeed had set. Removing this setting fixed the problem instantly. When adding showLoginTerminal: true again the problem got back and I never got a connection with that setting set to true. Removing the setting again fixed the connectionproblem again. After leaving it out I had no problems anymore. Today I had no problems connecting after that. Hope it holds!! And glad this fixed the connection problems (at least for now).

What I don't understand is why removing a setting to just show or hide the terminal should affect the connection to be made. Especially because the error message I previously got was that there was unparsable output. I'm very interested; Could you please let me know why this just showing/hiding of the terminal affects the connection of the extension? And are there any plans on fixing this so we can leave the terminal open during connecting? (which would be welcome in the future for debugging-reasons perhaps)

BTW it's working in VS Code 1.37.1 now too.

Thanks for the quick reactions and great it's working now (at least for now, hope it holds!!). And let this extension be a very stable extension. Because it's just a briljant idea and great and important tool to have. I'd rather stay with this extension than needing to look for alternatives. So keep up the great work.

roblourens · 2019-09-03T19:01:32Z

Ok, that's really good to hear. We are running the ssh command in a terminal in the background, and by default the terminal is not actually rendered. But if that setting is set, then the terminal is rendered, and if your pane is set to be somewhat narrow, then lines will wrap. We are trying to parse the terminal's output and if there are newlines where we don't expect, it breaks the parsing code. Plus on windows, this seems to happen when the terminal is not actually displayed but gets some narrow default width in the background somehow...

In the nightly version, we also changed the way that we output and parse the lines we expect, so it should be much more resilient even when it is rendered.

Please let me know if you have any more issues, thanks for using it!

ifigotin · 2019-09-03T23:16:31Z

I'm also having this issue right after updating to 1.37.1.
Also seeing this one on
1.38.0-insider
Commit: 5ab84ce18fe7dee304325952f2849264dd4a48c1

ifigotin · 2019-09-03T23:19:21Z

The error I'm seeing is as follows:

[23:18:17.520] Install and start server if needed
[23:18:17.595] > Cannot execute command-line and remote command.
[23:18:17.595] Got some output, clearing connection timeout
[23:18:18.061] "install" terminal command done
[23:18:18.061] Install terminal quit with output: Cannot execute command-line and remote command.
[23:18:18.061] Received install output: Cannot execute command-line and remote command.
[23:18:18.061] Failed to parse remote port from server output: Cannot execute command-line and remote command.
[23:18:18.062] 
[23:18:18.062] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[23:18:18.062] ------

jorymorrison · 2019-09-16T20:00:01Z

Same Issue here on 1.38

[19:51:14.931] remote-ssh@0.45.6
[19:51:14.931] win32 x64
[19:51:14.932] SSH Resolver called for "ssh-remote+bastion", attempt 1
[19:51:14.932] SSH Resolver called for host: bastion
[19:51:14.932] Setting up SSH remote "bastion"
[19:51:14.968] Using commit id "b37e54c98e1a74ba89e03073e5a3761284e3ffb0" and quality "stable" for server
[19:51:14.991] Testing ssh with ssh -V
[19:51:14.993] Got error from ssh: spawn ssh ENOENT
[19:51:14.993] Testing ssh with C:\windows\System32\OpenSSH\ssh.exe -V
[19:51:15.093] ssh exited with code: 0
[19:51:15.093] Got stderr from ssh: OpenSSH_for_Windows_8.0p1, LibreSSL 2.6.5
[19:51:15.093] Using SSH config file "C:\Users\jtmorrison\vscode-config\config"
[19:51:15.094] Running script with connection command: "C:\windows\System32\OpenSSH\ssh.exe" -o ClearAllForwardings=true -F C:\Users\jtmorrison\vscode-config\config bastion bash
[19:51:15.101] Install and start server if needed
[19:51:15.502] "install" terminal command done
[19:51:15.502] Install terminal quit with output: 
[19:51:15.502] Received install output: 
[19:51:15.503] Failed to parse remote port from server output: 
[19:51:15.503] 
[19:51:15.503] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[19:51:15.504] ------

Curiously I am also seeing the error popup The terminal shell path "cmd.exe" does not exist just before or after the SSH connection attempt.

roblourens · 2019-09-17T17:21:33Z

Neither of you are seeing the same issue, please open your own issues.

mlangTse · 2019-09-26T11:33:40Z

Same Issue here on 1.38

[19:51:14.931] remote-ssh@0.45.6
[19:51:14.931] win32 x64
[19:51:14.932] SSH Resolver called for "ssh-remote+bastion", attempt 1
[19:51:14.932] SSH Resolver called for host: bastion
[19:51:14.932] Setting up SSH remote "bastion"
[19:51:14.968] Using commit id "b37e54c98e1a74ba89e03073e5a3761284e3ffb0" and quality "stable" for server
[19:51:14.991] Testing ssh with ssh -V
[19:51:14.993] Got error from ssh: spawn ssh ENOENT
[19:51:14.993] Testing ssh with C:\windows\System32\OpenSSH\ssh.exe -V
[19:51:15.093] ssh exited with code: 0
[19:51:15.093] Got stderr from ssh: OpenSSH_for_Windows_8.0p1, LibreSSL 2.6.5
[19:51:15.093] Using SSH config file "C:\Users\jtmorrison\vscode-config\config"
[19:51:15.094] Running script with connection command: "C:\windows\System32\OpenSSH\ssh.exe" -o ClearAllForwardings=true -F C:\Users\jtmorrison\vscode-config\config bastion bash
[19:51:15.101] Install and start server if needed
[19:51:15.502] "install" terminal command done
[19:51:15.502] Install terminal quit with output: 
[19:51:15.502] Received install output: 
[19:51:15.503] Failed to parse remote port from server output: 
[19:51:15.503] 
[19:51:15.503] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[19:51:15.504] ------

Curiously I am also seeing the error popup The terminal shell path "cmd.exe" does not exist just before or after the SSH connection attempt.

im getting the same issue, how to solve it?

Blair2004 · 2019-10-04T10:16:42Z

Same issue, this is quie annoying already. Sometime when i connect to the root it works, but when i try to connect to already opened folders it doesn't

[10:11:15.252] remote-ssh@0.46.1
[10:11:15.252] win32 x64
[10:11:15.253] SSH Resolver called for "ssh-remote+7b22686f73744e616d65223a224d794e65786f504f53227d", attempt 1
[10:11:15.253] SSH Resolver called for host: MyNexoPOS
[10:11:15.253] Setting up SSH remote "MyNexoPOS"
[10:11:15.309] Using commit id "b37e54c98e1a74ba89e03073e5a3761284e3ffb0" and quality "stable" for server
[10:11:15.315] Testing ssh with ssh -V
[10:11:15.464] ssh exited with code: 0
[10:11:15.464] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[10:11:15.465] Running script with connection command: ssh -D 49518 MyNexoPOS bash
[10:11:15.467] Install and start server if needed
[10:11:15.735] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> �]0;C:\WINDOWS\SYSTEM32\cmd.exe�
[10:11:15.735] Got some output, clearing connection timeout
[10:11:15.813] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
[10:11:16.232] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
[10:11:19.869] > Running remote connection script
> 
[10:11:19.884] > Acquiring lock on /home/nexoposclub/.vscode-server/bin/b37e54c98e1a74ba89e03073e5a3761284e3ffb0/vscode-remote-lock.b37e54c98e1a74ba89e03073e5a3761284e3ffb0
[10:11:19.895] > Found existing installation at /home/nexoposclub/.vscode-server/bin/b37e54c98e1a74ba89e03073e5a3761284e3ffb0...
> 
[10:11:19.959] > Found running server...
> 
> 
[10:11:19.967] > *
> * 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:11:20.001] > Checking server status on port 33430 with wget
> 
[10:11:20.010] > 937a21ac-65bf-4b5b-8fb9-3eab5b1312ff: start
> sshAuthSock====
> 
[10:11:20.167] > agentPort==33430==   
> webViewServerPort====
> osReleaseId==centos==
> arch==x86_64==       
> webUiAccessToken==== �
[10:11:20.168] > 
> 937a21ac-65bf-4b5b-8fb9-3eab5b1312ff: end
[10:11:20.168] > 
> 
[10:11:20.169] Received install output: 
sshAuthSock====
agentPort==33430==   
webViewServerPort====
osReleaseId==centos==
arch==x86_64==       
webUiAccessToken==== �

[10:11:20.171] Failed to parse remote port from server output: 
sshAuthSock====
agentPort==33430==   
webViewServerPort====
osReleaseId==centos==
arch==x86_64==       
webUiAccessToken==== �

[10:11:20.172] 
[10:11:20.173] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[10:11:20.174] ------

roblourens · 2019-10-04T17:56:53Z

Please open a new issue.

oreilm49 · 2019-10-11T14:57:02Z

see #1152
in vscode settings :
search conpty
and uncheck it
Now it works. although i don't know what it means.

This also worked for me

heyzling · 2019-10-15T20:50:18Z

I had problem connecting to target host via bastion with following ssh config
Host host HostName host User my-user ProxyCommand ssh -q -x -W %h:%p my-user@bastion

Output and error was like jorymorrison had

Same Issue here on 1.38

[19:51:14.931] remote-ssh@0.45.6
[19:51:14.931] win32 x64
[19:51:14.932] SSH Resolver called for "ssh-remote+bastion", attempt 1
[19:51:14.932] SSH Resolver called for host: bastion
[19:51:14.932] Setting up SSH remote "bastion"
[19:51:14.968] Using commit id "b37e54c98e1a74ba89e03073e5a3761284e3ffb0" and quality "stable" for server
[19:51:14.991] Testing ssh with ssh -V
[19:51:14.993] Got error from ssh: spawn ssh ENOENT
[19:51:14.993] Testing ssh with C:\windows\System32\OpenSSH\ssh.exe -V
[19:51:15.093] ssh exited with code: 0
[19:51:15.093] Got stderr from ssh: OpenSSH_for_Windows_8.0p1, LibreSSL 2.6.5
[19:51:15.093] Using SSH config file "C:\Users\jtmorrison\vscode-config\config"
[19:51:15.094] Running script with connection command: "C:\windows\System32\OpenSSH\ssh.exe" -o ClearAllForwardings=true -F C:\Users\jtmorrison\vscode-config\config bastion bash
[19:51:15.101] Install and start server if needed
[19:51:15.502] "install" terminal command done
[19:51:15.502] Install terminal quit with output: 
[19:51:15.502] Received install output: 
[19:51:15.503] Failed to parse remote port from server output: 
[19:51:15.503] 
[19:51:15.503] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"UnparsableOutput"},"measures":{"resolveAttempts":1,"retries":1}}
[19:51:15.504] ------

Curiously I am also seeing the error popup The terminal shell path "cmd.exe" does not exist just before or after the SSH connection attempt.

Found out something wrong with default Windows 10 ssh client. Solved it setting Remote SSH: Path to ssh client from git-for-windows binaries. Path - %git-for-windows-path%/usr/bin/ssh

rafipiccolo mentioned this issue Aug 14, 2019

not connecting since windows update #1164

Closed

JtMotoX mentioned this issue Aug 15, 2019

Please support macOS SSH host #24

Closed

roblourens added the info-needed Issue requires more information from poster label Aug 16, 2019

roblourens self-assigned this Aug 16, 2019

jmdacruz mentioned this issue Aug 22, 2019

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

Closed

costas90 mentioned this issue Aug 28, 2019

Firewall settings prevent connecting to WSL #1304

Closed

roblourens closed this as completed Aug 30, 2019

erasmus7 mentioned this issue Aug 30, 2019

Can't connect to host while with command line ssh I can #1327

Closed

roblourens reopened this Aug 30, 2019

roblourens closed this as completed Sep 3, 2019

vscodebot bot locked and limited conversation to collaborators Oct 18, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remote SSH fails to connect to remote server after VS Code update 1.37.0 #1137

Remote SSH fails to connect to remote server after VS Code update 1.37.0 #1137

Friksel commented Aug 10, 2019 •

edited

Loading

meteorlxy commented Aug 12, 2019 •

edited

Loading

luanft commented Aug 13, 2019

captainfffsama commented Aug 13, 2019

Ibrahim-Badwi commented Aug 13, 2019

roblourens commented Aug 16, 2019

Friksel commented Aug 17, 2019

roblourens commented Aug 17, 2019

Friksel commented Aug 17, 2019 •

edited

Loading

bondenn commented Aug 17, 2019

roblourens commented Aug 18, 2019

Dayjo commented Aug 19, 2019 •

edited

Loading

rafipiccolo commented Aug 19, 2019

rafipiccolo commented Aug 19, 2019

Dayjo commented Aug 19, 2019 •

edited

Loading

Tyriar commented Aug 19, 2019

dreamflasher commented Aug 23, 2019 •

edited

Loading

fseesink commented Aug 28, 2019

scq000 commented Aug 29, 2019

roblourens commented Aug 30, 2019

Friksel commented Aug 30, 2019

malonnnn commented Aug 30, 2019

roblourens commented Aug 30, 2019

Friksel commented Sep 3, 2019 •

edited

Loading

roblourens commented Sep 3, 2019 •

edited

Loading

ifigotin commented Sep 3, 2019 •

edited

Loading

ifigotin commented Sep 3, 2019

jorymorrison commented Sep 16, 2019 •

edited

Loading

roblourens commented Sep 17, 2019

mlangTse commented Sep 26, 2019

Blair2004 commented Oct 4, 2019

roblourens commented Oct 4, 2019

oreilm49 commented Oct 11, 2019

heyzling commented Oct 15, 2019 •

edited

Loading

Remote SSH fails to connect to remote server after VS Code update 1.37.0 #1137

Remote SSH fails to connect to remote server after VS Code update 1.37.0 #1137

Comments

Friksel commented Aug 10, 2019 • edited Loading

meteorlxy commented Aug 12, 2019 • edited Loading

luanft commented Aug 13, 2019

captainfffsama commented Aug 13, 2019

Ibrahim-Badwi commented Aug 13, 2019

roblourens commented Aug 16, 2019

Friksel commented Aug 17, 2019

roblourens commented Aug 17, 2019

Friksel commented Aug 17, 2019 • edited Loading

bondenn commented Aug 17, 2019

roblourens commented Aug 18, 2019

Dayjo commented Aug 19, 2019 • edited Loading

rafipiccolo commented Aug 19, 2019

rafipiccolo commented Aug 19, 2019

Dayjo commented Aug 19, 2019 • edited Loading

Tyriar commented Aug 19, 2019

dreamflasher commented Aug 23, 2019 • edited Loading

fseesink commented Aug 28, 2019

scq000 commented Aug 29, 2019

roblourens commented Aug 30, 2019

Friksel commented Aug 30, 2019

malonnnn commented Aug 30, 2019

roblourens commented Aug 30, 2019

Friksel commented Sep 3, 2019 • edited Loading

roblourens commented Sep 3, 2019 • edited Loading

ifigotin commented Sep 3, 2019 • edited Loading

ifigotin commented Sep 3, 2019

jorymorrison commented Sep 16, 2019 • edited Loading

roblourens commented Sep 17, 2019

mlangTse commented Sep 26, 2019

Blair2004 commented Oct 4, 2019

roblourens commented Oct 4, 2019

oreilm49 commented Oct 11, 2019

heyzling commented Oct 15, 2019 • edited Loading

Friksel commented Aug 10, 2019 •

edited

Loading

meteorlxy commented Aug 12, 2019 •

edited

Loading

Friksel commented Aug 17, 2019 •

edited

Loading

Dayjo commented Aug 19, 2019 •

edited

Loading

Dayjo commented Aug 19, 2019 •

edited

Loading

dreamflasher commented Aug 23, 2019 •

edited

Loading

Friksel commented Sep 3, 2019 •

edited

Loading

roblourens commented Sep 3, 2019 •

edited

Loading

ifigotin commented Sep 3, 2019 •

edited

Loading

jorymorrison commented Sep 16, 2019 •

edited

Loading

heyzling commented Oct 15, 2019 •

edited

Loading