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

Interoperability with Linode Object Storage #12723

Closed
toddler-boy opened this issue Dec 29, 2021 · 2 comments · Fixed by #12725
Closed

Interoperability with Linode Object Storage #12723

toddler-boy opened this issue Dec 29, 2021 · 2 comments · Fixed by #12725
Assignees
Labels
bug s3 AWS S3 Protocol Implementation
Milestone

Comments

@toddler-boy
Copy link

Previously connecting to Linode Object Storage (s3 compatible) using v8.1.0 using Access Key ID / Secret Access Key combination to the endpoint us-east-1.linodeobjects.com. After upgrading to 8.2.0 I consistently get the below error though nothing has changed by way of configuration.

Login failed. Forbidden. Service Error Message. Please contact your web hosting service provider for assistance.

This issue persists regardless of the creation of new access key pairs and seems to be fixed by reverting to an older version.

I can still access these buckets by way of s3cmd or the interface

@dkocher dkocher added the s3 AWS S3 Protocol Implementation label Dec 29, 2021
@dkocher dkocher self-assigned this Dec 29, 2021
@dkocher
Copy link
Contributor

dkocher commented Dec 29, 2021

We can reproduce the problem which is caused by a 403 reply querying the region.

2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - GET /?location= HTTP/1.1
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - Date: Wed, 29 Dec 2021 13:07:12 GMT
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - Host: eu-central-1.linodeobjects.com
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - x-amz-date: 20211229T130712Z
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - Authorization: ********
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - Connection: Keep-Alive
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - User-Agent: Cyberduck/8.2.1.36687 (Mac OS X/12.1) (aarch64)
2021-12-29 14:07:12,235 [Thread-180] INFO  ch.cyberduck.transcript.request - Accept-Encoding: gzip,deflate
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - HTTP/1.1 403 Forbidden
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - Date: Wed, 29 Dec 2021 13:07:12 GMT
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - Content-Type: application/xml
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - Connection: keep-alive
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - x-amz-request-id: tx000000000000000491ef3-0061cc5d80-28f8ca8-default
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - Accept-Ranges: bytes
2021-12-29 14:07:12,297 [Thread-180] INFO  ch.cyberduck.transcript.response - Content-length: 200

Regression from 7f69ba1.

@dkocher dkocher added this to the 8.2.1 milestone Dec 29, 2021
@dkocher dkocher added the bug label Dec 29, 2021
dkocher added a commit that referenced this issue Dec 29, 2021
@dkocher dkocher linked a pull request Dec 29, 2021 that will close this issue
dkocher added a commit that referenced this issue Dec 30, 2021
Interoperability with Linode Object Storage
@dkocher
Copy link
Contributor

dkocher commented Jan 11, 2022

New service specific profiles in af748fa.

@dkocher dkocher changed the title v8.2.0 breaks Access Key Pair Interoperability with Linode Object Storage Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug s3 AWS S3 Protocol Implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants