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

S3 read failure #3756

Closed
cyberduck opened this issue Sep 27, 2009 · 1 comment
Closed

S3 read failure #3756

cyberduck opened this issue Sep 27, 2009 · 1 comment
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

5974899 created the issue

I created a new S3 account and did a couple of test uploads and download with Cyberduck 3.2.1. It worked as expected.

Later, I uploaded a few folders and subfolders worth of data, maybe 1GB worth, to the account on Windows with CloudBerry Explorer. That worked and the listing on Cloudberry was as expected.

Then, I opened Cyberduck to upload data from the Mac. That's where the surprises begin. My bucket and it's contained directories are present. But when I try to open those directories, I get errors in the form of a Failures dialog:

Failures

The last action could not be completed due to the following errors:
S3 Error:
<s3 pathname displayed>
Request Error.. Not Found.

The transcript reads, in one particular case:

x-amz-request-id: 82...<rest of id removed for security>[\r][\n]
x-amz-id-2: eQV<rest of id removed for security>[\r][\n]
Content-Type: application/xml[\r][\n]
Transfer-Encoding: chunked[\r][\n]
Date: Sun, 27 Sep 2009 19:05:00 GMT[\r][\n]
Server: AmazonS3[\r][\n]
[\r][\n]

If I then use CloudBerry on Windows or S3Hub on the Mac, I'm able to view the bucket and its contents as expected. Restarting Cyberduck doesn't change anything.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Is this still an issue with the current release? We would need to dig in further then.

@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 s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants