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

Listing directory failed with error request signature we calculated does not match the signature you provided #9747

Closed
cyberduck opened this issue Nov 2, 2016 · 7 comments
Labels
bug high priority s3 AWS S3 Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

e757f6c created the issue

While using Cyberduck on two of my macs, I occasionally receive the message at the bottom. It is sporadic with which folders it won't open. My team and I successfully use Cyberduck on multiple devices to access those same directories, so it appears to be the configuration of Cyberduck on these two devices, though for the life of me I cannot find out what is difference on this one. I uninstall and reinstall, and have the same problem. Although the error says it has something to do with my "web hosting provider," I have no indication that is the case, since others on my team do not have this issue.

My job is primarily dependent on my ability to access these files. Any assistance you can offer would be greatly appreciated.

The error is:

Listing director (directory name) failed.
The request signature we calculated does not match the signature you provided. Check your key and signing method. Please contact your web hosting service provider for assistance.

Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Screen Shot 2016-11-02 at 10.46.25 AM.png

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Possibly related to #9793.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This might be caused by using AWS2 signature for authentication instead of the default AWS4. Please try to remove your configuration file from ~/Library/Preferences/ch.sudo.cyberduck.plist and relaunch Cyberduck.

@cyberduck
Copy link
Collaborator Author

e757f6c commented

Unfortunately, this is not a fix. The problem recurred again within hours.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (⌘-L).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please reopen this issue if you can still reproduce with the current 5.3 snapshot build.

@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.
Labels
bug high priority s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

1 participant