Currently, on Windows 10 with current patches, when I try to open a connection with aws_access_key_id and aws_secret_access_key defined, nothing happens when I click on "Connect". Same functionality both on the latest 6.x as well as the latest 7.x beta. The same credentials work normally from the same Windows system using Cloudberry Explorer for S3, and the operation works also normally with the Mac version of Cyberduck (on a Mac, naturally :-), so it seems the Windows version of Cyberduck is affected by this problem.
The text was updated successfully, but these errors were encountered:
Cyberduck requires a credentials file? I don't have one configured on the Windows system I think. The credentials entered into the connection profile aren't standalone? What does it need from the credentials file since the connection profile is already provided the aws_access_key_id and aws_secret_access_key, and the region is set in the profile settings?
Stumbled upon a workaround for this glitch yesterday. Accidentally had it set to FTP instead of Amazon S3 that I was trying to connect to and hit Connect, and it eventually errors (or can just hang there). If while it's hanging there or once it errors out, I then change it from FTP to Amazon S3 it then connects! But again this is still an issue needing a fix.