Method 2: Enabling Legacy Options in OpenSSH

If this isn’t an option and you recognize the dangers of using a compromised algorithm, then there’s a client-side way to bypass this error message. If it’s your own server, then take a moment to update them.

You’ll want to update all the ssh packages at the server end of the equation, so make sure the system administrator is aware of what’s going on. OpenSSH implements a dizzying array of different protocols, but it disables a number of these because they’re now known to be compromised and therefore unsafe. Should you still be having issues, then it means that the server and client weren’t ever able to come to terms with the right protocol to use. Barring that, you might want to try restarting ssh by running service ssh restart and giving it a few moments. This will refresh the cache that the ssh application uses to connect to the remote server. If you still receive it, then try regenerating keys with ssh-keygen -A from the command prompt. While we were running ssh in a virtual machine that allowed the connection to a bogus server address that was set to the documentation-approved, but you’ll want to substitute a real networking address instead. Sometimes this error message is just because there is some remote-side service that isn’t currently running, which might have been corrected in the meantime. Method 1: Recontacting the Server and Regenerating Keysīefore you do anything else, make sure that you can reproduce the error. You should be able to use the same process to correct it if you’re running ssh on Windows or something exotic, but you might find that the switch options are slightly different.

The following methods to fix the error have been tested on everything that ssh works on, but you’ll most likely find this problem on Unix and Linux systems. This process can be really frustrating, but the error is so common that you’ll often find Unix types talking about how they’re experiencing it and giving the same advice to get out of the woods. You won’t be able to connect to the remote server whenever you experience the error. When you’re trying to use ssh to get in touch with a remote server, you might receive an error that reads no matching key exchange method found before giving you a suggestion as to which encryption algorithm you’ll want to be using.

Windows terminal ssh no kex alg