Hello,
We are experiencing a critical issue with the Remote - SSH extension (ms-vscode-remote.remote-ssh) in our Qoder environment, which prevents any remote development workflow.
Environment Details:
-
Qoder Version: 0.2.8
-
VSCode Engine Version: 1.100.0
-
OS: Windows 11 (Windows_NT x64 10.0.22000)
-
Remote Server: Ubuntu 22.04.5 LTS, OpenSSH_8.9p1
Problem Description:
The Remote - SSH extension fails to connect to our server. All authentication methods (PublicKey, Password) are attempted and fail, resulting in the error: Error: All configured authentication methods failed.
Key Facts & Diagnostics:
-
Standard SSH Client Works: Connecting from the Windows terminal (cmd, PowerShell) using the system’s OpenSSH client (ssh root@<server_ip>) works perfectly via public key authentication (passwordless).
-
Server Configuration is Correct: The server’s sshd_config permits both PubkeyAuthentication and PasswordAuthentication. The user’s public keys (id_rsa.pub, id_ed25519.pub) are correctly listed in /root/.ssh/authorized_keys.
-
Qoder Logs Analysis: The Qoder Remote - SSH output log shows the following sequence:
-
It correctly identifies the local identity files (.ssh/id_rsa, .ssh/id_ed25519).
-
It attempts publickey authentication using these keys, but it fails.
-
It then falls back to password authentication, which also fails (even with the correct password).
-
A recurring error in the logs is Error: Failed to connect to agent.
-
Troubleshooting Steps Taken (All Failed):
-
Forcing Password Auth: We modified the ~/.ssh/config file to explicitly set PreferredAuthentications password and PubkeyAuthentication no. Qoder appeared to ignore this configuration.
-
Forcing Public Key Auth: We modified the ~/.ssh/config file to explicitly provide the IdentityFile path. Qoder also ignored this.
-
Direct Command: We used the “Connect to Host…” command with a direct string ssh root@<server_ip> -i “C:\Users\<my_user>\.ssh\id_ed25519”. This also failed with the same error.
-
Remote.SSH.path Setting: We confirmed this setting is empty. Pointing it to the system’s ssh.exe did not resolve the issue.
Conclusion:
The issue is isolated to the Qoder application itself. It seems unable to correctly utilize the system’s SSH agent, keys, or configuration, unlike the standard system SSH client.
Request:
Could you please provide a specific configuration or workaround to make the Remote - SSH extension function correctly within Qoder? Is there a known issue or a required setting we are missing?
Thank you for your assistance.
Текст готов к публикации.
