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.

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

Login Failed: Exhausted Available Authentication Methods #11394

Closed
cyberduck opened this issue Dec 8, 2020 · 8 comments
Closed

Login Failed: Exhausted Available Authentication Methods #11394

cyberduck opened this issue Dec 8, 2020 · 8 comments
Assignees
Labels
bug fixed sftp
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Dec 8, 2020

2316422 created the issue

Continually getting the error message: "Login failed. Exhausted available authentication methods. Please contact your web hosting service provider for assistance." I should have no issues getting onto the server of which I am trying to use, because I have gotten on through terminal numerous times since trying to get onto cyberduck.


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 9, 2020

@dkocher commented

Do you have a PreferredAuthentications setting in your OpenSSH ~/.ssh/config?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 12, 2020

bc3ab78 commented

Same issue with version 7.7.2 on Mac OS 10.14.6 accessing a Linux server using PIV authentication. I have PKCS11Provider set in the ssh config file. It works with command line sftp, FileZilla and Cyberduck through version 7.7.1 but fails with 7.7.2, so it's a new bug or feature. For now I went back to version 7.7.1.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 12, 2020

@dkocher commented

Replying to [comment:2 cbdjjdmn1]:

Same issue with version 7.7.2 on Mac OS 10.14.6 accessing a Linux server using PIV authentication. I have PKCS11Provider set in the ssh config file. It works with command line sftp, FileZilla and Cyberduck through version 7.7.1 but fails with 7.7.2, so it's a new bug or feature. For now I went back to version 7.7.1.

Please share your configuration in ~/.ssh/config.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 12, 2020

bc3ab78 commented

Replying to [comment:3 dkocher]:

Please share your configuration in ~/.ssh/config.

This is a scrubbed version of the config entry for that host:

Host host1 host1.addr1.addr2.com

Hostname host1.addr1.addr2.com

ServerAliveInterval 30

ServerAliveCountMax 3

AddKeysToAgent yes

ForwardAgent yes

PKCS11Provider /usr/lib/ssh-keychain.dylib

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 13, 2020

@dkocher commented

We never supported the PKCS11Provider directive. But if the key is registered with SSH agent it should work using public key authentication. Possibly related to #10454.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 13, 2020

bc3ab78 commented

Replying to [comment:5 dkocher]:

We never supported the PKCS11Provider directive. But if the key is registered with SSH agent it should work using public key authentication. Possibly related to #10454.


The key is registered with this command: ssh-add -s /usr/lib/ssh-keychain.dylib

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 21, 2020

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 21, 2020

@dkocher commented

In b536847.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed sftp
Projects
None yet
Development

No branches or pull requests

2 participants