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

Connect button not working to initiate a connection #10621

Closed
cyberduck opened this issue Feb 17, 2019 · 7 comments
Closed

Connect button not working to initiate a connection #10621

cyberduck opened this issue Feb 17, 2019 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 17, 2019

9a2dd02 created the issue

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 17, 2019

@dkocher commented

Where is your credentials file located?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 17, 2019

9a2dd02 commented

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?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 22, 2019

@dkocher commented

#10625 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 22, 2019

84201fe commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 25, 2019

@ylangisc commented

In 9b8e24e.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 26, 2019

@dkocher commented

#10624 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 1, 2019

@dkocher commented

#10636 closed as duplicate.

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

No branches or pull requests

2 participants