-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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: can't connect to OpenSSH 9 / Ubuntu 22 #6804
Comments
My first ssh connect is ok, but got this error when duplicate it. Then I close the whole tabby and restart it, all is ok now~ |
This should be top priority, as it renders Tabby completely unusable for new os systems (latest centos, ubuntu). |
the issue is still there... :( i'm running debian sid, that is, the ssh agent is also from ssh9.0p1 right now, and it cannot connect 127.0.0.1:22.. doing ssh localhost connects fine without asking for a thing... |
What are the connection conditions? what is the error message in the SSH server logs at the time of SSH connection in |
@mc36 are you on v1.0.182? |
On build 182, I am able to connect to both Centos 9 and Ubuntu 22. Great work! |
Had to rollback to 181, could not connect anymore. ecdsa-sha2-nistp256 Ubuntu 20.04.4 LTS |
|
so i try to use the agent to authenticate with my key... (they came from keepassxc, if that matters, but should not) |
X-post.
|
I installed release alpha 183 yesterday (tabby-1.0.183-macos-x86_64.pkg) and I am running into this issue.
There's also a log on devtools stating I will just run |
Still having this problem under Ubuntu 22.04 with Tabby 1.0.186 - is this related to issues in the ssh2 package? Edit: FYI for people wanting a quick(ish) resolution. Just make a new ed25519 SSH key pair, update your endpoints and user accounts |
Tabby currently lacks support for rsa-sha2-256/512 private key auth (through node-ssh2).
OpenSSH 8 has deprecated the old ssh-rsa private key auth algorithm in 9.0 since rsa-sha2-256 offers better security with the same key, however Tabby as an SSH client doesn't support it yet.
The error shown in Tabby is All configured authentication methods failed.
As a workaround, you can reenable ssh-rsa auth on the server by adding PubkeyAcceptedAlgorithms +ssh-rsa to your /etc/ssh/sshd_config and reloading the SSH service.
The text was updated successfully, but these errors were encountered: