-
-
Notifications
You must be signed in to change notification settings - Fork 290
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 via SFTP #13442
Comments
I too am experiencing this issue. The log (on my side) does not add anything useful, I am getting „Too many authentication failures“ right now. Don't have any info from the server side. Additional context Workaround |
I am also seeing this on Cyberduck version 8.3.3: getting the 'Too many authentication failures' with existing saved configs and with newly created configs (all using password auth). I've just downgraded to version 8.3.2, and password auth seems to be working for that version |
I also started to have connection issues with version 8.3.3. Downgrading to version 8.3.2 makes everything work again. I've noticed, however, that I can solve the problem in 8.3.3 by deleting the keys from my |
@mathio Thanks for the logfile which does not give too much insight why the auth process fails. Any chance to post a logfile generated with version 7.10.2? |
@wtw @Rizzle93 @geroembser Can you please provide a debug log of a failing connection attempt with version 8.3.3? |
@ylangisc Debug log for As @mathio mentioned there are failing authentication attempts with different keypairs. After these failing authentication attempts some background task returns null, which causes an exception. Authentication method |
Thanks @wtw for the log. I can see that password auth would also be tried if all other options do not work but it looks like your server has set |
Sure, it seems that the order of auth methods is the same, but not only two of my keys are used, but all four of them. There is no error after two attempts. It is the same bookmark/server and I can switch from 8.3.2 (works) to 8.3.3 (too many attempts) and back at will. After all keys failed, password auth is tried and succeeds. |
I have the same Problem "Too many authentication failures. Please contact your web hosting service provider for assistance." with version 8.4.2 on MacOS 11.6 (20G165). However, I need a key for the authentication and not a password. The correct key is selected in the connection settings and no password is in the password input field. After a downgrade to 8.3.2 it works as expected. Thanks to @wtw for posting the last working version numbers. |
Just another "me too" - using a private key & no password on macOS 12.5.1. I can ssh on the command line fine & I can access using FileZilla fine, but CyberDuck 8.4.3 fails with "Too many authentication failures." It works if I use version 8.3.2 without changing anything else (thanks @wtw!) (Edit: Clarify version.) |
Prioritise password authentication if one is set.
The latest snapshot version contains a fix for authentication with password. |
Where can I find the latest snapshot please? The link on the website does not work ( |
This issue seems to be fixed in version 8.4.4 (just upgraded and connects successfully): https://cyberduck.io/download/. |
I also can confirm that the bug is fixed with version 8.4.4. |
I downloaded the 8.4.4 version. I kept it in
Full log: cyberduck-8-4-4.log When I connect with Cyberduck 7.10.2 it works.
Full log: cyberduck-7-10-2.log |
Might be a different error and/or root cause. Luckily, my issue got solved, so I can't provide more help or input here, sorry. |
We are encountering the same issue with 8.5.10 (39764). Cyberduck refuses to connect to our newest web hosting server. Works perfectly well with the older servers. Server is running Ubuntu 22.04 with ProFTPD. Downgrading Cyberduck didn't help. Went all the way to 7.10. |
@Muutu This issue is closed. Refer to proftpd/proftpd#1595. |
Describe the bug
Connecting via SFTP with password authentication fails. Cyberduck tries to authenticate via public key.
This is happening for Cyberduck version 8+. The issue is not present in Cyberduck 7.10.2.
To Reproduce
Expected behavior
Connection should not fail.
I was told by my hosting provider the client is trying to connect using public key however it is configured to use password instead. Cyberduck should authenticate using password.
Screenshots
Desktop:
Log Files
Note: The domain was replaced with
example.com
in all logs.Related Cyberduck log:
Full log here: cyberduck.log
Related log from hosting provider:
Additional context
I can connect via
sftp
command line without any issues, therefore I can rule out general network issues.Workaround
Downgrading all the way down to Cyberduck version 7.10.2 works fine.
The text was updated successfully, but these errors were encountered: