tabby: SSH Key Not Working

I am on version 1.0.75 on Ubuntu, and whenever I try to connect to my server with my SSH private key, I get the following error: Connecting to 45.77.239.27 Loading private key from /home/emil/.ssh/id_rsa SHA256 fingerprint: 246c4c289b674e79ca40586c44faba861e2c3dd9524308b6d1aad0edd25b1187 All configured authentication methods failed

My SSH key is configured in the remote server, why is this coming up? The SSH key is not encrypted.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 27 (2 by maintainers)

Most upvoted comments

The situation can be corrected by exporting the key to Putty Key Generator. Open Putty Key Generator, File - Load Private Key. Then we do Conversions - Export OpenSSH key. Accordingly, then in the connection settings, select our new exported key. This option helped me. Best regards.

gitbuk0 on Dec 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment. Thank you for your contributions.

stale[bot] on Jul 26, 2019

Sorry but same problem here. Private key generated from PuTTyGen. I tried every export format (ssh.com, new OpenSSH, legacy OpenSSH) but none of these keys are working. Note that everything’s working well with PuTTy.

Clem- on May 27, 2019

I can confirm that this buy still exists, and still frustrates me. I’m using Google Cloud for a VM instance and I love Terminus because of how it looks. However, if the program doesn’t function (which it doesn’t, developer!) It’s functionally useless to me. Can it be really that hard for someone who has already created an application which seems as polished as this, already with some types of private keys supported, to simply add another?

mattsavin on Jul 7, 2020

I am running into the same problem here. I have an RSA key pair that i can perfectly use with my terminal (running ssh -i /path/to/key/ user@remote.host) to connect to my remote machine, but it can’t seem to work with Tabby. I am using Tabby 1.0.197 with Ubuntu 20.04 and the error message is:

 SSH  Connecting to remote.host
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  hash_something
 SSH  Loading private key: file:///path/to/key/

 SSH  Connecting to remote.host
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  hash_something
 SSH  Loading private key: file:///path/to/key/
 X  Error signing data with key: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR

Update: Indeed when using ed25519 keys, the process seems to work fine, as mentioned before from @luddystefenson. Maybe the problem is only with RSA keys?

Update 2: when i use ssh-keygen to generate RSA keys it works just fine. The difference between these 2 keys are that the first (that does not work) is of the format:

-----BEGIN RSA PRIVATE KEY-----
dg35hy
...
...

and the second (the one that works) is:

-----BEGIN OPENSSH PRIVATE KEY-----
fdsefgswhh
...
...
-----END OPENSSH PRIVATE KEY-----

GeorgeTasop on Jul 17, 2023

This is absolutely dumb founding. BUT! The SSH connection worked for me once I generated my keys on my server side (Kali VM) and moved them to my client with Tabby. I have NO idea why.

I specifically used a ed25519 key just incase that info may be helpful.

luddystefenson on Jul 2, 2022