Couldn't start a terminal for xxx: All configured authentication methods failed

[elayoutable]

Hi there,

The extension is very great! Thank you very much! It worked perfect some weeks ago.

But now I´ve got the message:
Couldn't start a terminal for xxx: All configured authentication methods failed.

The ssh key is the same. I´ve tried the login with puuty (same sshkey) and no problems. I didn´t change anything.

Have you got a tipp for me? I´ve tried the older version 1.25 but with the same result.
Thank you!

[SchoofsKelvin]

Did you recently update your server or the OpenSSH server running on it? If so, you could check the build I mentioned in #309.

Otherwise provide me with your debug logs, so please follow these steps:

• Add DEBUG_SSH2 to the sshfs.flags array in VS Code's User Settings (settings.json)
  e.g. "sshfs.flags": ["DEBUG_SSH2"]
  • See this issue for more information about adding flags
• If you already have a connection open, close it completely (or even reload the window)
• Go to Output > SSH FS and copy the log from there after replicating your bug
• While it should censor passwords/passphrases, I recommend checking it for (other) sensitive data first.
  (especially since DEBUG_SSH2 activates some internal logging, which is less likely to be censored)

[elayoutable]

Unfortunately I´m to stupid ... :(

I´ve downloaded the Build extension #122 (vscode-sshfs-master.vsix.zip), but I can´t install it in Visual Studio Code (as a zip or unzipped).

I´ve added "DEBUG_SSH2" to the "sshfs.flags", but where can I find the log (Output > SSH FS)?

[SchoofsKelvin]

You can use the Extensions: Install from VSIX... command to install the .vsix file (after unzipping) from the build.

The output is in the Output pane, in the same place as the Terminal pane. You can use the View: Toggle Output command and then selecting SSH FS in the dropdown.

[SchoofsKelvin]

I've published a new version of the extension (v1.26.1) which includes this fix, so it's not necessary anymore to manually install the custom build to test it. If you still encounter this issue, comment on (and reopen) this issue.