Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error: All configured authentication methods failed #5023

Closed
zuedev opened this issue Dec 1, 2021 · 37 comments
Closed

Error: All configured authentication methods failed #5023

zuedev opened this issue Dec 1, 2021 · 37 comments
Labels
Plugin: SSH T: Bug

Comments

@zuedev
Copy link

zuedev commented Dec 1, 2021

Version: 1.0.164
Platform: Windows x64 10.0.22000
Plugins: none
Frontend: xterm

Clean install of Windows 11 Pro + Tabby, using an RSA 4096 SSH key with both the new and old OpenSSH formats. Using the built-in SSH works fine, but here's what I get from Tabby:

image

image

I have also tried with version 1.0.165-nightly.0 to no avail. If you need me to do anything else to try and help figure out the issue, just ask! I'd really like to use Tabby as my main driver. 😅
@Eugeny
Copy link
Owner

Eugeny commented Dec 1, 2021

Could you try explicitly setting the auth method to "private key" in the connection profile?

@zuedev
Copy link
Author

zuedev commented Dec 1, 2021

Could you try explicitly setting the auth method to "private key" in the connection profile?

That's what I did for those screenshots, but have also tried everything else and only explicit password works.

@TyrantLucifer
Copy link

I met the same problem again. When I tried to connect my server use specified private key not default private key(it in ~/.ssh), it would show this error in screen.This tool is so cool that I want to use it in my whole work. Anyone can help me solve this problem?

@Eugeny
Copy link
Owner

Eugeny commented Dec 2, 2021

Could you please generate and post another key pair with the exact same settings and format you're using so that I test it on my side with the exact same settings?

@zuedev
Copy link
Author

zuedev commented Dec 2, 2021 •
edited
Loading

Could you please generate and post another key pair with the exact same settings and format you're using so that I test it on my side with the exact same settings?

Here's a test key in the old OpenSSH format.

I just checked it against a new Ubuntu 20.04.3 LTS VM and it's giving me the same errors.

-----BEGIN RSA PRIVATE KEY-----
MIIJJwIBAAKCAgEAzD9YjdcjYZdYeLFJCjMOveogXsiBacEv6eEr7CYntLbugYqH
ZIlVIPoZsaMB+Q3dNcGbqmaW3JdOiK6QvAWFjqrALVpEluaqhCunC44CpS2scy/C
Yj1uVdwasAseHOskamC2xcP4pBQ9/DZoGM2NBrXZR+WiLJ2uLxXzzPWCUKHWKnK/
wQ+Leh5UqCqseFfI8HSRvg9Zz08ycjl+vCGHqZr+6J/rtyqTcEm3Ska34vkkbxIX
Juo68QPesh1hTuu5YMcX9oxvca5IwdOQJi3kZ/nsixdumJn1rRkMp/a2sESisQVA
NTyKFB6P3QEZCBMbGgAtHph0GBvQr/DDlhlx0qd98cvD1zVhepyl58qEjHWrFNQi
6kx03tQs3gn9IoeWpQR8euJmFxGTYh34iiGTliU+NFDYVgGy9ZqZLSU/0rviwpWN
YxLULJpC1YLF9jPsE3fHjxbp/PIQvp0ZXQ14wI1GTR+4oXNUvakGMujVCbqXrwjk
o9QsXUDfCLvPKygNmrLNPo8Mq9WUKTzFFVezZ3mTGiULPwZ18xEsc+HYd0VNO68L
HQAk7IlCYDln2uBjwMVuXsizdEbUiQ3HUlTZZaW5p4yl+UmtZ5NjNxHwKs0ZZWbT
3NktArvovWZlFC4UrkbThEUuWXhr9uO3AfHPjySX338AoF+Mpyz9hp8OVLMCAwEA
AQKCAgAxhLYihWNVmMzhThIoP+K2FppMgI4npqfIK0hr04BS5vsCOyTCMi2Kdjhe
gefLixnzm4HzGTZAOwrWRoReoXQU977p//WbJEd5DeBNA9wOUfl6X7zf9obWmCt8
POXLGxNUGyiU4ANbPHEewc4RHVywoMwSC1F7QatmTQszyN4UUHhNCE8HLo6hR9M8
hkQUVSwpaAmhq7UZdtkDKn9Ye0SZ0TM2EPekC9V9JtIiVuzkQYUczKUCUU2C+241
frwF1061cO+VXczzIc8P9wv+xaeXsdcwjbjJlKIkmmsgGceHCszq4BwGDCxp3lMA
wPBhrcgnUJ2fylRzN+MrlNLGhFq8ya6gEbIJw1QKiNPbIT1lVLvMPGPh/RBFMp2J
vpZN4ks522u0BPrcnGI+z9RTqlaeQlHP2kV7Nhs9jESmcz+UTuVtzfVm/SaKXITA
2XrSZX0R7DKrFCPwGYihlcuxQny54y5talGS5YstEaya4ZvFdHTxMbUULdqClluJ
sqvPMslfZ7RwfyukChGKwuLTVPyzhTktkTAfHmNQ0e0hm42yY2EZ1eDTWOWawnmE
MAyXR4f0ycIm1r/E3dQdLuoszgwq+dn3rJeyr6YaXJL43JVEZX22IVuFsSqKQL7L
6CXu2J5NSG6LckShoI1rK8/FSW3xxMq6r28qjI2nru9CgAv6MQKCAQEA9LtW1IoL
tKRqpXwmhvrAu0AW2RHh90oJlQ5tWCD2DohMStS0KSj2pnb6+bt9qKXdOEW8m3/2
rAIcriIptzi25gOfDd2cGrKPRAlB7Dp9zbqkhVjP6ghAVeEN6cbugHMQIhk99f2c
XkTAA6PJlPWGHxBmlE17IDnwqnf6/C9HdM9BsSqY68H3usnI1ib0JdCiSejzvlXO
xvyKdQ6TNFTr3cXEYjTGuLVfPSOk1xQmO5BEF6UoThGo2NxcFz2lanxOZXhbKtYV
6Y8FTMhNZTSS0WkCKScf4fqeLsijn+YhKS58Ije6AN7z+OqSPawmH0fbyVK0t+BE
OT41gsIDUAOpywKCAQEA1abRCBvy02lEaVMpsuT2kTvyO3KAsEJV+0KnWAk/M4QO
iUM/cChdemMhZHlQnU3uqNEOMOap8FtIhZJob6eSs1DsysXRqJhVgnMrkRJ07h7h
0dQ2206+wvB/eN0vgKorEB+QZk+dg45MGL/+7AnOdYvtyLSlNz8wjqJ5GRGoJDXK
C5xstINZYkkEkqyHs3TIeWWhR6JXUJgVBJ5UBu3mOarLsadyuIZrirnYcMyFxdG5
x4BYgjoa/vnJYC1LiEaM0XzOikNClyjv2uy8y2Q0KJMeYMm00W1WyYcTnx8NVj7D
jlpYlc1gSn8490NH0P7oj9W6+cCC4wlWN5T9n9nDuQKCAQB8FtlqHyzcRVnF2vN2
EYLT7yUmn4ih6Kp/J7eNrfjVWYrFjqBjFmAp+746DjUi5CcNN17wwauDf/am3K+m
NV2Xt1JYp3tVliBKcR859lZ/kBmHe4bAtbpZUSnK1ZFtE+qkP4RJTHSS3+00a0H1
A6Ej8x7wJ3E83+QFq5xZbmee9M/sUxsCv3ErBtGMtGerHOSM8U9VvRCBmN9jhyZg
rIaEBpkS6ouwcFaAG6ijXZYdMYM1MgsDurSQcPtI1XsgSTM/BA3F5JNrv5cCXbXQ
kR24jLQJxcrGvFqkghtlIjzCMs3CU9s+Qc4W8mmAV99kkP0CUatMaKxvEfnz+QfQ
9GqNAoIBABbNxlPaP9HG05F2WeYJQDQCNPmZYBjwC6NU2u2vlvpVpwOJlPTQqiGN
ARxrQmp3zfhgz+XySMMpyxTOqqz4MtVG1u9Rq+4VzFKvHkBOuwJLc4jk4LIJtpyx
9LkeypouD4iaBdyVtNc80ex2Wawx48JyHAAnH9dEvFcNCmXdl5e90gHpQUUHG/w8
lOte1OEXnuouKceukSk+AkhK6ecPb1pKW5FrsPf3CPV2np5zhfe2SeD8VvYXY5hB
avgD/aLe/NrDOnxRb4MY0HkKeaAv4s1N3pkwDkeoJvI9o5+BPfgtnMvN4tSiZhut
dpQVr02kV4g6pMlRfebjsTsfgO6V3KkCggEACV/WAhY8ciS3T3lSFKyUvvlZ4zrw
Or2ZD3YOT7KPVMiXEILalo8tIeLkgXgazpnAz9qsxJMRq+K69TL9P2hyJZuqSnKu
sPMakKB420J8/9PYZEVafswr+tbEvkF7uLhiqiDuqTCZ7bx4dygOr2KkxcLxztFu
1ViVNd9uQpkUMz0XSDKCZ9VBuC1OT80Vuvam5OyeHVO7L3/Jp7o4SAiSY/tTX4N+
jjVStWnGZzjC0yDSAVnSwo4n2309AwBMhXxOyGAqiZ+S2PakEAaH+fDNVlroEc3T
8mfFTn1Bw/RRDAlqGM8YWVBZU3LRw5KJEeXW6cOP2cUFzKmEPdPkhWnM8g==
-----END RSA PRIVATE KEY-----

Edit: Here's the public key for convenience:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDMP1iN1yNhl1h4sUkKMw696iBeyIFpwS/p4SvsJie0tu6BiodkiVUg+hmxowH5Dd01wZuqZpbcl06IrpC8BYWOqsAtWkSW5qqEK6cLjgKlLaxzL8JiPW5V3BqwCx4c6yRqYLbFw/ikFD38NmgYzY0GtdlH5aIsna4vFfPM9YJQodYqcr/BD4t6HlSoKqx4V8jwdJG+D1nPTzJyOX68IYepmv7on+u3KpNwSbdKRrfi+SRvEhcm6jrxA96yHWFO67lgxxf2jG9xrkjB05AmLeRn+eyLF26YmfWtGQyn9rawRKKxBUA1PIoUHo/dARkIExsaAC0emHQYG9Cv8MOWGXHSp33xy8PXNWF6nKXnyoSMdasU1CLqTHTe1CzeCf0ih5alBHx64mYXEZNiHfiKIZOWJT40UNhWAbL1mpktJT/Su+LClY1jEtQsmkLVgsX2M+wTd8ePFun88hC+nRldDXjAjUZNH7ihc1S9qQYy6NUJupevCOSj1CxdQN8Iu88rKA2ass0+jwyr1ZQpPMUVV7NneZMaJQs/BnXzESxz4dh3RU07rwsdACTsiUJgOWfa4GPAxW5eyLN0RtSJDcdSVNllpbmnjKX5Sa1nk2M3EfAqzRllZtPc2S0Cu+i9ZmUULhSuRtOERS5ZeGv247cB8c+PJJfffwCgX4ynLP2Gnw5Usw==

@Eugeny
Copy link
Owner

Eugeny commented Dec 8, 2021 •
edited
Loading

It works for me - could you please test a fresh nightly with this key against this blank VM I've just set up: 159.223.127.106?

@burtek
Copy link

burtek commented Dec 13, 2021 •
edited
Loading

I also get a smiliar issue with private keys. I have a freshly new passwordless priv key that works in Putty but Tabby wants a password for it.

The key is puttygen-generated ssh-rsa 2048 SHA256 passwordless key. Works great in putty (while used directly and via pageant) and works in Tabby via pageant. But Tabby doesn't seem to be able to use the key, although it has no issue with another key of same params (passwordless puttygen-generated ssh-rsa 2048 SHA256) used with another remote.

image

image

159.223.127.106

that works fine with me using key provided by @zuedev

EDIT:

The key works fine when imported in OpenSSH format but does not work in .ppk format - although there is no issue using .ppk format for the other key.

EDIT2:

Found the issue. I'm using a new PuttyGen now that saves private keys in new format, i.e. with header PuTTY-User-Key-File-3. Extracted my issues as #5145

@EldritchGarden
Copy link

I have an OpenSSH key that works connecting to Ubuntu, Mint, and MX Linux, but the same key doesn't work to connect to either of my Fedora installations.

image

Not sure if this is a coincidence, but it does seem strange that it fails on both of my Fedora machines, but works fine on Ubuntu/Debian and derivatives when using the same exact key

@coert
Copy link

coert commented Jan 4, 2022

Similar problem as @EldritchGarden , I have an OpenSSH key (with passphrase) that works just fine from Tabby ssh to Linux Mint, but fails on another server running Xero (Arch) Linux.

Crazy, but ssh from a zsh shell in Tabby to the Xero Linux server works just fine.

Is there a possibility to get ssh to be more verbose from the Tabby ssh connection? (similar to ssh -vvv from the terminal)

@stefanfritsch
Copy link

I have the same issue. Windows ssh-agent is not working, private key is not working, but connecting from a powershell window works just fine.

@BenjaminHuang
Copy link

Met the same issue

@stardiviner
Copy link

stardiviner commented Feb 4, 2022 •
edited
Loading

Screen Shot 2022-02-04 at 3 45 14 PM

I got similar problem.

Only specified password authentication is working. Agent or private key all has this problem.

@DacoDev
Copy link

DacoDev commented Apr 4, 2022 •
edited
Loading

Seeing the same on 1.0.174, using the 1Password SSH agent, I can SSH directly from a local terminal and it auths OK but using a profile I get the failure

@wgicio
Copy link

wgicio commented Apr 5, 2022

Same issue

Seeing the same on 1.0.174, using the 1Password SSH agent, I can SSH directly from a local terminal and it auths OK but using a profile I get the failure

@stardiviner
Copy link

After upgrading to latest version, the ssh key authorization problem seems fixed on my M1 macOS Monterey.

@mmdjiji
Copy link

mmdjiji commented Jun 29, 2022

Same with #6690

@Akbar30Bill
Copy link

I have the same issue using private key
image

@utgpay2
Copy link

utgpay2 commented Jul 14, 2022

all bro,ubuntu have the problem,use centos is ok

@Uj947nXmRqV2nRaWshKtHzTvckUUpD
Copy link

i have same problem after upgrading from centos 8 to 9

@Eugeny
Copy link
Owner

Eugeny commented Jul 18, 2022

Duplicate of #6804 - see that issue for more info.

@Eugeny Eugeny closed this as completed Jul 18, 2022
@lxeridium
Copy link

我也一样， 用mobaxterm 没有问题， 用tabby 就是上不去。

@Issues-translate-bot
Copy link
Collaborator

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

Me too, I have no problem with mobaxterm, but I can't get on with tabby.

@alibabasb
Copy link

Me too...

@Uj947nXmRqV2nRaWshKtHzTvckUUpD
Copy link

Me too...

update to latest version

@mmdjiji
Copy link

mmdjiji commented Aug 7, 2022

Solved, by upgrading to the latest version.

@Aterfax
Copy link

Aterfax commented Aug 29, 2022

I think something is unpatched with respect to these new builds when using the Pageant agent. If I supply the private key via the key method in the profile, I can login to endpoints.

If I tell it to use Pageant agent I cannot login with the same error as above with v182 and above.

@Aterfax Aterfax mentioned this issue Aug 29, 2022
Closed
@GoldBaby5511
Copy link

Me too

@Aterfax
Copy link

Aterfax commented Dec 1, 2022

Me too

Please see: #6804 (comment)

@pysonic
Copy link

pysonic commented Dec 1, 2022

i updated .. but still not working... what can i do

@Issues-translate-bot
Copy link
Collaborator

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

i updated .. but still not working... what can i do

@pysonic
Copy link

pysonic commented Dec 1, 2022 •
edited by unfurl-links bot
Loading

i solve this problem
https://aws.amazon.com/ko/premiumsupport/knowledge-center/ec2-linux-fix-permission-denied-errors/

Amazon Web Services, Inc.

@springeye
Copy link

How to solve it? I have encountered the same problem and upgrading to the latest version does not work!

@hanxu-zhao-L043767
Copy link

Me too.

@meowtech
Copy link

Same problem with latest version 1.0.200

@cgfcrc
Copy link

cgfcrc commented Jun 5, 2024

Same problem with version 1.0.207.

@FANGOD
Copy link

FANGOD commented Aug 5, 2024

Same problem with version 1.0.211！

@silencesoup
Copy link

I find one way to connect with tabby.
Connect with config yml, usually the path is in ~/.ssh/config.
If you don't know how to write the config, use vscode remote-ssh or something like this to connect the server, and it will automatically write into the config file.
And in tabby, do not use ssh to connect. Use the config yml to connect.
image

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Plugin: SSH T: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests