-
-
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
[BUG] Error: Keys(CouldNotReadKey) #10115
Comments
What format is the key in? |
mostly PEM RSA... |
Me too, in 1.0.216. My private key is something like this:
Edit: This problem does not reproduce in 1.0.215. |
New nightly build is available now - give it a try! |
Nightly build not working. Use Key as "Vault" and "File" |
For both EC and PuTTY? PuTTY formatted keys won't be supported in the new backend for a while, but EC should still work. Could you please generate a new key in the exact same format and post it here for me to test against? |
Sorry, my mistake. OpenSSH keys work, but the PuTTY keys do not. |
For me it's not working as well. Was woring like 2 days ago. Running version 1.0.216 It's working again when installing version 1.0.215. |
It also stopped working for me when updating to recent version. |
There's a new nightly build with PPK key support available |
Tried the nightly build 1.0.217-nightly.0, same result, but different error message:
|
If I add the key as file from system again to profiles it is working, but a bit annoying for doing this over 20 entries. Had issues with the keys before, it should really not happen in any future build. |
@feligato PPKv2 support will be in the nightly as soon as this build completes https://github.com/Eugeny/tabby/actions/runs/12640523980
|
Describe the problem:
I'm getting this error since the latest version.
Failed to load private key vault://xxx: Error: Keys(CouldNotReadKey)
I have tried re-adding the key to the vault. Same error.
To Reproduce:
The text was updated successfully, but these errors were encountered: