-
Notifications
You must be signed in to change notification settings - Fork 231
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
Unable to connect to server using openssh private key #50
Comments
I can confirm that this is happening to me too. Selected my key under ~/.ssh/id_rsa
|
Thanks for reporting, will look into it |
I've had the same problems today with some of the servers I manage. I tested on one of my servers by changing to a different key from another server that worked and the problem resolved - the difference between the two keys being the length of the key. Perhaps a clue into the source of the problem? |
Related issue dbeaver/dbeaver#5845, consider using/supporting SSHJ. |
Temporary solution:
This works with version 1.0.4 |
Can confirm this is still an issue to date. Existing OpenSSH private keys can be converted to RSA format using the following terminal command where id_rsa is the OpenSSH private key:
Recommend you back-up id_rsa before running the command as the file will be overwritten when converted. Remember to OpenSSH seems to be the new standard private key format. Any comment on when/if Snowflake will add support? Thank you for this program. |
Using Snowflakes for connecting to AWS EC2 unable to connect through .pem files for the new EC2 instances ( through Putty/WINSCP i can login to EC2 with same key). But can connect to Older EC2s with Snowflake with their .PEM files. |
facing the same issue while I am trying to access the new aws instance, i 'm geting an error - Unable to connect to server. Please look into this. |
Holy molly, same issue still persists. |
I cannot connect using my private key:
It's related to this post:
https://stackoverflow.com/questions/53134212/invalid-privatekey-when-using-jsch
The text was updated successfully, but these errors were encountered: