Error while connecting to SSH FS turing: All configured authentication methods failed

[Michael-B-Ibikunle]

Recently the connection for turing&hopper on vscode stopped working with the ssh fs extension. It used to work fine but now everytime I try to open a terminal, the error "Error while connecting to SSH FS turing: All configured authentication methods failed" popped up. The same error occurs for hopper as well. Need help thank you

[turbo2025]

yes same with me , the version is 1.26.1 , using in arch linux

[turbo2025]

my config is
"sshfs.configs": [
{
"name": "dev",
"host": "192.168.10.193",
"port": 10086,
"username": "turbo",
"privateKeyPath": "/home/turbo/.ssh/id_ecdsa",
"passphrase": true,
"group": "home"
}
]

[turbo2025]

just only work in username and password , didn't work with key

[Prototype-Laboratory]

same problem, when try to login with private key.

[Michael-B-Ibikunle]

error still comes through when i tried with different ssh exstension

[svenoone]

I confirm the same problem. I have a private key that I would like to use. The authentication fails - I spent what felt like forever with it and thought something was wrong with my configuration.

In my case it is an ssh-rsa 4096 SHA256 key.

I have not tried whether other keys work. If this is necessary I will be happy to do so to help with the problem.

[kinchahoy]

Running into the same problem. Can we revert to an older version?

[kinchahoy]

FYI - I resolved this by reverting to v1.25.0. @SchoofsKelvin Any idea if this is an easy fix? Very much appriciate your work on this extension!

[SchoofsKelvin]

Which key formats/ciphers are you using for this? Perhaps it's a new key format that the underlying ssh2 library (or at least the older version the published extension uses) doesn't support. If you can generate and attach a new key in the same format, that'd be handy.

This issue would be easier to solve with 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)