Skip to content
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

Cannot authenticate server or no matching compression #77

Open
maxammann opened this issue May 26, 2020 · 3 comments
Open

Cannot authenticate server or no matching compression #77

maxammann opened this issue May 26, 2020 · 3 comments

Comments

@maxammann
Copy link

I'm running the latest version of the docker container. I also downloaded the static build version 2.4.0 from Github and tried to connect from two different platforms without success:

When connecting from arch-linux:

Cannot authenticate server
Reconnecting... (Cannot authenticate server)

When connecting from Debian GNU/Linux 9.12 (stretch):

Error connecting: kex error : no match for method compression algo client->server: server [[email protected],zlib], client [none]
Reconnecting... (Error connecting: kex error : no match for method compression algo client->server: server [[email protected],zlib], client [none])

The server only has an RSA key available.

It seems like the server is very strict about the compression and encryption algorithm. Is there a way to configure this without rebuilding the server?

@phil-blain
Copy link

Regarding compression, @nviennot indicated in another issue a few years ago that the tmate ssh server forces the use of compression. If the client does not support compression, the connection will fail. This is the case for example with the builtin version of OpenSSH on Windows:

PS C:\Users\me> ssh ***********************@nyc1.tmate.io
Unable to negotiate with 134.209.128.51 port 22: no matching compression method found. Their offer: [email protected],zlib
PS C:\Users\me> ssh -V
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

@ejohb
Copy link

ejohb commented May 30, 2022

I'm having the same problem using a PyCharm SSH-based interpreter. Is there any workaround?

@liqwang
Copy link

liqwang commented Dec 30, 2023

Regarding compression, @nviennot indicated in another issue a few years ago that the tmate ssh server forces the use of compression. If the client does not support compression, the connection will fail. This is the case for example with the builtin version of OpenSSH on Windows:

PS C:\Users\me> ssh ***********************@nyc1.tmate.io
Unable to negotiate with 134.209.128.51 port 22: no matching compression method found. Their offer: [email protected],zlib
PS C:\Users\me> ssh -V
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

I have the same problem with the builtin OpenSSH on Windows 10, and I have solved it by downloading a newer version of OpenSSH
https://github.com/PowerShell/Win32-OpenSSH/releases/download/v9.5.0.0p1-Beta/OpenSSH-Win64.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants