While using key based authentication for SFTP backups, my client fails with the message:
2021-10-13 14:51:19.170 ERROR STORAGE_CREATE Failed to load the SFTP storage at sftp://duplicacy-user@server/duplicacy: ssh: handshake failed: ssh: disconnect, reason 2: Too many authentication failures Failed to load the SFTP storage at sftp://duplicacy-user@server/duplicacy: ssh: handshake failed: ssh: disconnect, reason 2: Too many authentication failures
My shell is configured with multiple keys for various different uses, and my ssh config file specifies which key for use for the endpoints I normally use. Ex: github, work servers, personal servers
Please describe what you expect to happen (but doesn’t):
I expect duplicacy to honor the key I configured while setting up the storage profile.
Please describe what actually happens (the wrong behaviour):
Duplicacy fails to connect, because it appears to be iterating through all of the keys in my ssh-agent configuration instead of the key specified at setup time.
This bug has been frustrating me for quite some time now, and if a solution can not be offered I will have to request a refund for all of my licenses. It would be a real shame to have to go through that hassle, given the fact that the SFTP browser in the web UI clearly works properly.