-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
SSH connection fires the error "Authentication failed" with version 1.0.222. Works with 1.0.221 #10347
Comments
I can confirm. Fresh installation, no plugins. Tabby detects |
Same here , had to rollback , selected all Ciphers , key exchange , HMAC & host key. |
Same error, I see this in server logs "sshd[2141525]: userauth_pubkey: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]". So I can fix it on server side, but it was working fine with previous version. |
Same issue here. |
The same problem and a similar error: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms |
Same issue, rolled back |
Same for me on 1.0.222, looks like 1.0.222 always presents the deprecated ssh-rsa (sha1) hash to the server for authentication, no matter what ciphers you check/uncheck in settings. I supsect commit d1c1b48 to be the culprit Rollback to 1.0.221 fixed it. 1.0.221 uses sha256 hash for authentication. |
Same issue here. |
Same issue. |
Same for me on 1.0.222. Rollback to 1.0.221 fixed it. |
Same issue here, after upgrading to 1.0.222 |
Same issue here, after upgrading to 1.0.222 |
I had the same issue and was going crazy trying to figure out what was wrong. |
Same issue. |
Same issue. |
1 similar comment
Same issue. |
Any workaround other than downgrade? It's a massive pita I just upgraded tabby on like 8 machines 😆 |
You can change your RSA key to an ECDSA key and it will work... ;-) |
Please try the latest nightly build, it should be fixed there. |
I might sound dumb but, where can we get the nightly build? |
Just tried nightly, still the same
on win11 x64 |
Same here!
|
I've updated the build, could you give it another try? |
Works on Ubuntu 24.04. Thank you so much @Eugeny! |
I tried the nightly build and it do not change the bug is still there. Tested on Linux Linux Mint 21.3 (based on Ubuntu 22.04) and there is the same error in 1.0.223+nightly, 1.0.222, 1.0.221, and even 1.0.215, this means that is not related to the I tested the 1.0.223+nightly also on Windows 10.... exactly the same problem. I can still connect to SSH through the terminal
|
Nightly build 5deb725 fixed the issue for me, Windows 11 24H2. |
I used this link https://nightly.link/Eugeny/tabby/workflows/build/master/Linux%20DEB%20%28amd64%29.zip... does it correspond to the nightly build 5deb725 ? |
@Eugeny I found the bug!! The problem is not the password but the username! Tabby uses a wrong username to log in SSH: in I found a quick and dirty workaround and finally I can use it locally but I do not have idea how to fix in a proper way!!
and it works. |
https://github.com/Eugeny/tabby/actions/runs/13758597414
|
Same here:
Anyone has found any solutions? |
Version: 1.0.222
Platform: Linux x64 6.8.0-55-generic
Plugins: quick-cmds
Frontend: xterm-webgl
SSH connection : port 22, with username and authentication with private key file.
The connection is established with v1.0.221
The connection fails with v1.0.222
The text was updated successfully, but these errors were encountered: