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

Error "The request signature we calculated does not match the signature you provided" when opening a large folder #10395

Closed
cyberduck opened this issue Jul 10, 2018 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 10, 2018

8719699 created the issue

When opening the largest folder (about 2000 files) my company uses, I get this error report: "Listing directory -directories-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."

This is fairly odd, because every other folder in that S3 account functions as normal. The error happens both on my desktop (Windows 8.1, about 5 year old hardware, 16 GB of RAM) and my laptop (Windows 10, decade old hardware, not a fast machine), but does not happen on my boss's 5 year old but pretty souped up Mac.

The only thing I can find different between this folder and other folders is the number of objects in it, and other computers can open the folder, so I assume it's not an issue of any corruption or error on the server side. Cyberduck won't let me copy the further details to put it in here, but I'll take a screenshot.

I'm currently not able to change our most heavily used folder from my office, any help would be appreciated. Thank you!


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 5, 2018

@dkocher commented

Ticket retargeted after milestone closed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 6, 2018

@dkocher commented

#10373 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 10, 2018

@ylangisc commented

I've tried many different ways to replicate this issue but didn't succeed. There is definitively something wrong and I'd like to fix this issue. Can you please enable debug logging (restart Cyberduck), try to navigate in the large folder and post the log file after you see the error message?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 11, 2018

@dkocher commented

Possibly related to #9914.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 12, 2018

8719699 commented

This error stopped happening with the last large update (last weeks/month). I really appreciate the followup! Let me know if you need anything else from me.

Loading

@cyberduck cyberduck closed this Nov 22, 2018
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants