remote connection error: Unavailable (FileSystemError): ENOPRO: resource not found "

[wangzhankun]

Does this issue occur when all extensions are disabled?: Yes (only with ssh extension)

• VS Code Version: 1.94.2
• OS Version: macos 14.6.1 Apple m3
• remote OS: debian 12
• ssh authored by Kerberos

Steps to Reproduce:

1. connect to remote server
2. try to open remote folder, and then vscode report bug:

[670 ms] userEnvProbe: loginInteractiveShell (default)
[670 ms] userEnvProbe: not found in cache
[670 ms] userEnvProbe shell: /usr/bin/zsh
[684 ms] Error reading shell environment.
[684 ms] Error: Connection closed
        at Socket.<anonymous> (/Users/xxxxxxx/.vscode/extensions/ms-vscode-remote.remote-ssh-0.115.0/out/extension.js:2:293877)
        at Object.onceWrapper (node:events:634:26)
        at Socket.emit (node:events:531:35)
        at TCP.<anonymous> (node:net:339:12)

ERR ENOPRO: 未找到资源 "vscode-remote://ssh-remote%2B10.xx.xx.xxx/home/xxxxxx/documents/rodan" 的文件系统提供程序: CodeExpectedError: ENOPRO: 未找到资源 "vscode-remote://ssh-remote%2B10.xx.xx.xxx/home/xxxxx/documents/rodan" 的文件系统提供程序
    at Git.j (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3072:64896)
    at async Git.exists (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3072:66919)
    at async Promise.all (index 0)
    at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3108:7727
    at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1942:14511

more log.txt

[medikoo]

I have exact same issue. It started to happen recently, it's hard to work with any remote host.

It looks there's something wrong with downloaded vscode-server, as on first connection it works, but after VS Code downloads the vscode-server, then any further attempts to open remote connection just fail.

Currently I'm able to work only by constantly removing .vscode-server on server and only after that attempting to connect or opening folder on remote succeeds

[wangzhankun]

downgrade the vscode will solve the issue, for example version 1.83.1. The bug may have been introduced in a recent release