-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handshake Failed: no matching key exchange algorithm #243
Comments
I want to add that this only impacts specific servers, the error is only impacting Bluehost.com servers for me but my other servers are working as expected. |
Could you add "sshfs.configs": [
{
"name": "mysite.com",
"putty": "mysite.com",
"debug": true
}
] It's probably related to #239, as I recently added an auto-fix for it that disables some algorithms, probably the only ones that both VS Code and your server support, but coincidentally are the broken algorithms. You could risk adding |
Sure thing (looks like remote only wants Diffie Hellman if I'm reading this right... but that crashes VS Code's extension manager if I force enable it): [INFO] Command received to connect mysite [ERROR] Handshake failed: no matching key exchange algorithm [DEBUG] Reading ssh://mysite/.vscode/settings.json |
That's indeed what's going on here. Although it's quite unusual for a server to be configured to only support that one algorithm. There are basically 3 ways to solve this:
|
Unfortunately, it's a client's server (shared hosting, I believe) and I don't think that they have access to changing the algorithms. I have two weeks until the next maintenance where I require more than the currently working tools. I'll sort out what to do in the meantime. Thanks for the assist in sorting it out, I tried looking through the logs initially but my sleep deprived brain didn't think to add a debug flag in first :D |
Hi, my error is the following:
|
@antonio-petricca please make a new issue for more info. Also enable debug logging and/or check your server's SSH logs, as it might tell us more about the cipher issue. |
Similar to #236 and #238, I'm receiving the above error since mid-January or so. I've tried to add the fix listed in 236 with no luck. This was working fine prior and I can connect via Putty with no problems.
Here is my log (scrubbed):
[INFO] Created output channel for vscode-sshfs
[INFO] Loading configurations...
[DEBUG] Added configuration mysite.com from 2
[INFO] Found 1 configurations
[INFO] Extension activated, version 1.19.3, mode 1
[INFO] [createConnection(mysite.com,config)] Creating a new connection for 'mysite.com'
[INFO] Calculating actual config
[INFO] Fetching PuTTY sessions from registry
[DEBUG] Found 3 sessions:
[DEBUG] - {"name":"mysite.com","hostname":"mysite.com","protocol":"ssh","portnumber":22,"username":"username","usernamefromenvironment":0,"tryagent":1,"publickeyfile":<>,"proxyhost":"proxy","proxyport":80,"proxylocalhost":0,"proxymethod":0}
[DEBUG] Reading PuTTY configuration lead to the following configuration:
{
"name": "mysite.com",
"putty": "mysite.com",
"_location": 2,
"_locations": [
2
],
"_calculated": {
"name": "mysite.com",
"putty": "mysite.com",
"_location": 2,
"_locations": [
2
]
},
"username": "username",
"host": "mysite.com",
"agent": "pageant",
"port": 22
}
[DEBUG] Final configuration:
{
"name": "mysite.com",
"putty": "mysite.com",
"_location": 2,
"_locations": [
2
],
"_calculated": {
"name": "mysite.com",
"putty": "mysite.com",
"_location": 2,
"_locations": [
2
]
},
"username": "username",
"host": "mysite.com",
"agent": "pageant",
"port": 22
}
[INFO] [createSocket(mysite.com)] Creating socket
[DEBUG] [createSocket(mysite.com)] Connecting to mysite.com:22
[INFO] [createSSH(mysite.com)] Flag "DF-GE" not specified, disabling DiffieHellman kex groupex algorithms
[DEBUG] [createSSH(mysite.com)] Resulting algorithms.kex: [email protected],curve25519-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha1
[ERROR] [createSSH(mysite.com)] Handshake failed: no matching key exchange algorithm
Reported from createSSH(mysite.com)
[ERROR] Error while connecting to SSH FS mysite.com:
Handshake failed: no matching key exchange algorithm
[ERROR] Handshake failed: no matching key exchange algorithm
JSON: {"level":"handshake"}
The text was updated successfully, but these errors were encountered: