vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Remote Explorer: SSH targets not appearing

Open MariamNakhle opened this issue 5 months ago • 7 comments

After using Remote Explorer for over a year without any issue, suddenly last week none of the ssh targets appear when I click on the Remote Explorer icon on the left side bar. The .ssh/config file still contains all the host names.

I tried uninstalling + reinstalling Remote Explorer and Remote-SSH extensions. I also uninstalled and reinstalled VScode.

Here are the versions I am using:

VScode version: 1.86.0 Remote - SSH version: v0.108.0 Remote Explorer version v0.4.1

MariamNakhle avatar Feb 05 '24 09:02 MariamNakhle

Same issue here. I rolled back to v0.107.1 and the SSH targets re-appeared for me.

jamesps-ebi avatar Feb 05 '24 10:02 jamesps-ebi

Thanks, this worked for me too.

MariamNakhle avatar Feb 05 '24 12:02 MariamNakhle

Same issue, about to rollback now 😝

Neeham avatar Feb 05 '24 15:02 Neeham

Same issue here. Rolling back to v0.107.1 fixed it for me.

Issue occurs with these versions: VS Code: 1.86.0 Remote - SSH: 0.108.0 Remote Explorer: 0.4.1 OS: Windows 10 Pro (22H2)

CrustyPistachio avatar Feb 05 '24 15:02 CrustyPistachio

Another issue to keep in mind, you may have to downgrade your VSCode to 1.85.2 if the server that you are SSHing to does not meet the minimum linux distribution requirement. I downgraded the extension, could see the targets but could no longer connect to it.

From the latest release notes:

Linux minimum requirements update In this milestone, we have updated the toolchains to build our desktop client. From this release onwards, VS Code desktop is only compatible with Linux distributions based on glibc 2.28 or later, and glibcxx 3.4.25 or later, such as Debian 10, RHEL 8, or Ubuntu 20.04.

If you are unable to upgrade your Linux distribution, the recommended alternative is to use our web client. If you would like to use the desktop version, then you can download the VS Code release 1.85. Depending on your platform, make sure to disable updates to stay on that version. A good recommendation is to set up the installation with Portable Mode.

Neeham avatar Feb 05 '24 16:02 Neeham

I'm having the same issue and noticed in vscode's process explorer that it is doing DNS lookups for domains specified in my ssh config CanonicalDomains option.

To test if it is linked, I commented out CanonicalizeHostname and CanonicalDomains in my ssh config. This seems to work around the issue and the list of remotes appears again.

Unfortunately I need this setting for other reasons, so it's not really a solution for me.

tom-ami avatar Feb 05 '24 16:02 tom-ami

Same here, I got vs code from snap on ubuntu 22.04, no targets appear.

rudiservo avatar Feb 12 '24 12:02 rudiservo

Update to latest VS Code and this should be fixed. More details here https://github.com/microsoft/vscode/issues/203375

isidorn avatar Feb 22 '24 12:02 isidorn

Not fixed, I have vscode 1.87 and remote-ssh 0.109, still the same issue.

rudiservo avatar Mar 01 '24 13:03 rudiservo

Same issue, vscode 1.87 and remote-ssh 0.109.

SSH targets not appearing, and get error: Failed to connect to the remote extension host server (Error: A system error occurred: uv_os_get_passwd returned ENOENT (no such file or directory))

Downgrading to v0.107.1 solves it.

hsimonfroy avatar Mar 04 '24 08:03 hsimonfroy

Let me reopen just in case, and assign to @connor4312

isidorn avatar Mar 04 '24 09:03 isidorn

The CanonicalDomains config causes the issue for me

1a1a11a avatar Mar 24 '24 16:03 1a1a11a