New Linode Object Storage Endpoint Connection Failures

[WoodardDigital]

2 things to start off;

• I verified the access keys and URLs were correct using s3cmd, then I attempted to mirror that configuration in Cyberduck,
• Not sure if a bug report is really the best for this, but if nothing else this should get it on y'all's radar.

Describe the bug
When attempting to connect to the new Linode Object Storage IAD the connection fails when using bookmarks. Error output is as follows.

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

To Reproduce
Use bookmarks to add the new US IAD cluster to cyberduck. The below syntax was used.

Protocol: Amazon S3
Server: us-iad-1.linodeobjects.com
Access Key ID: <your access key>
Secret Access Key: <your secret access key>

Expected behavior
Successful connection

System Information:

• OS: macOS
• Version: Ventura 13.4.1

Log Files - These are the lines generated when i attempt to connect via the bookmark.,

2023-07-13 05:34:03.079612-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] GET /?location= HTTP/1.1
2023-07-13 05:34:03.079657-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Date: Thu, 13 Jul 2023 11:34:02 GMT
2023-07-13 05:34:03.079679-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2023-07-13 05:34:03.079696-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Host: us-iad-1.linodeobjects.com
2023-07-13 05:34:03.079711-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] x-amz-date: 20230713T113402Z
2023-07-13 05:34:03.079737-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Authorization: ********
2023-07-13 05:34:03.079750-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Connection: Keep-Alive
2023-07-13 05:34:03.079763-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] User-Agent: Cyberduck/8.6.0.39818 (Mac OS X/13.4.1) (aarch64)
2023-07-13 05:34:03.079775-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Accept-Encoding: gzip,deflate
2023-07-13 05:34:03.223691-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] HTTP/1.1 403 Forbidden
2023-07-13 05:34:03.223878-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Date: Thu, 13 Jul 2023 11:34:03 GMT
2023-07-13 05:34:03.223916-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Content-Type: application/xml
2023-07-13 05:34:03.223974-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Connection: keep-alive
2023-07-13 05:34:03.224012-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] x-amz-request-id: tx00000b7295be39bfcc353-0064afe12b-103e841-default
2023-07-13 05:34:03.224040-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Accept-Ranges: bytes
2023-07-13 05:34:03.224087-0600 0x89c95f   Info        0x0                  42661  0    Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:transcript] Content-length: 200

[AliveDevil]

The error you are seeing is due to us not knowing which region your bucket belongs to, thus Cyberduck requests the S3-location, which Linode refuses (either you don't have enough permissions, or Linode doesn't support that API).

Can you check whether this file (click on Download raw file, and install) allows you to connect successfully?

[WoodardDigital]

That works perfect!
All I had to do was fill in was the access information

[WoodardDigital]

To add to this, I created 53 and 54. I believe they should suffice for the 2 other new DCs