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
Comments
We can reproduce the problem which is caused by a
Regression from 7f69ba1. |
dkocher
added a commit
that referenced
this issue
Dec 29, 2021
dkocher
added a commit
that referenced
this issue
Dec 29, 2021
…Catch `SignatureDoesNotMatch` error code.
This was referenced Dec 29, 2021
dkocher
added a commit
that referenced
this issue
Dec 30, 2021
Interoperability with Linode Object Storage
New service specific profiles in af748fa. |
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
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
The text was updated successfully, but these errors were encountered: