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

Jump to bottom

Error "Failure to read attributes of [bucket name]" when attempting download bucket #8388

Closed
cyberduck opened this issue Dec 2, 2014 · 4 comments
Closed

Error "Failure to read attributes of [bucket name]" when attempting download bucket #8388

cyberduck opened this issue Dec 2, 2014 · 4 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
4.6.1

Comments

@cyberduck
Copy link
Collaborator

1ebf7a2 created the issue

Error:
"The specified key does not exist. Please contact your web hosting service provider for assistance."

I can login via Cyberduck with no issues. I can also view all of my buckets via Cyberduck. I have confirmed my credentials work fine via AWS CLI but only when I attempt to grab data via Cyberduck is there an issue. It was working fine last week but now it fails consistently. You can see in the response there is a HTTP 404 being returned.

Was there an update/change?

Here is the transcript when I attempt the following:

  1. Highlight bucket
  2. Right-click and 'Get info'
  3. View permissions
GET /?versioning HTTP/1.1
Date: Tue, 02 Dec 2014 13:36:59 GMT
Authorization: AWS AKIAJU2ZQV4GWX3WG43Q:rd/ZNJJ2KF0Tv6XK6F0EKl5hMcw=
Host: mpulse-beacon-logs.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.6 (Mac OS X/10.8.5) (x86_64)
Accept-Encoding: gzip,deflate
HTTP/1.1 200 OK
x-amz-id-2: bGgo1dmCJIud3RyavYrhVnWqeCfKwetAgPCRdxuZM7ACqVpKTAobUTAvtGXR+oEkXX34Ix8uBqI=
x-amz-request-id: 93A95BF919920CFB
Date: Tue, 02 Dec 2014 13:37:01 GMT
Transfer-Encoding: chunked
Server: AmazonS3
<br />

GET /PQX4J-SQS6B-2PSQZ-VKD9S-B4NS9%2F2014-11-12%2F?acl HTTP/1.1
Date: Tue, 02 Dec 2014 13:37:00 GMT
Authorization: AWS AKIAJU2ZQV4GWX3WG43Q:KyGfoJ5WWEAy5TjNCYhevEPBNxo=
Host: mpulse-beacon-logs.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.6 (Mac OS X/10.8.5) (x86_64)
Accept-Encoding: gzip,deflate
HTTP/1.1 404 Not Found
x-amz-request-id: 5B807E707EB1124E
x-amz-id-2: ITNeqw+ffbkZNPcOH37rqamNM5XB/xyyyCy15jvBMlznnYM4lpwx1m2m9/Xzzuf+YIgr2Sn0aNY=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Tue, 02 Dec 2014 13:36:59 GMT
Server: AmazonS3

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In e1ae914.

@cyberduck
Copy link
Collaborator Author

1ebf7a2 commented

Replying to [comment:5 dkocher]:

In e1ae914.



How do I take advantage of this fix? Do I need to re-download the app?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

1ebf7a2 commented

Please see screenshot attached in earlier comment. No Update is available in my preferences area.


Version 4.6 (15809)

@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.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.6.1
Development

No branches or pull requests
2 participants
@dkocher @cyberduck