rclone gives Authorization header malformed, unexpected scope: #700

New Issue

Closed

opened 2024-02-02 20:05:41 +00:00 by alexej · 5 comments

alexej commented

2024-02-02 20:05:41 +00:00

Other clients like mino mc work great. But my rclone just gives me:

garage_api::generic_server: Response: error 400 Bad Request, Authorization header malformed, unexpected scope: 20240202/us-east-1/s3/aws4_request

rclone.conf:
[garage]
type = s3
provider = Other
env_auth = true
endpoint = mylocaldomain.com
force_path_style = true
acl = private
bucket_acl = private

I am using the garage docker image in version v0.9.1

Other clients like mino mc work great. But my rclone just gives me: garage_api::generic_server: Response: error 400 Bad Request, Authorization header malformed, unexpected scope: 20240202/us-east-1/s3/aws4_request rclone.conf: [garage] type = s3 provider = Other env_auth = true endpoint = mylocaldomain.com force_path_style = true acl = private bucket_acl = private I am using the garage docker image in version v0.9.1

Poppypop commented

2024-02-04 11:29:40 +00:00

Hello,

To workarround this , you have to specify your region and signature_v2 = true

Example on rclone.conf

[garage]
type = s3
provider = Other
env_auth = false
access_key_id = xxxxxxxxxxxxxxxxx
secret_access_key = xxxxxxxxxxxxxxxx
endpoint = s3.mydomaine.fr
acl = private
bucket_acl = private
force_path_style = true
region = eu-west1
signature_v2 = True

Hello, To workarround this , you have to specify your region and signature_v2 = true Example on rclone.conf ``` [garage] type = s3 provider = Other env_auth = false access_key_id = xxxxxxxxxxxxxxxxx secret_access_key = xxxxxxxxxxxxxxxx endpoint = s3.mydomaine.fr acl = private bucket_acl = private force_path_style = true region = eu-west1 signature_v2 = True ```

Poppypop commented

2024-02-04 11:29:59 +00:00

Documentation to be updated.

jpds commented

2024-02-07 16:20:38 +00:00

Contributor

It's already there: https://garagehq.deuxfleurs.fr/documentation/connect/cli/#rclone

lx commented

2024-02-07 16:24:51 +00:00

Owner

To workarround this , you have to specify your region and signature_v2 = true

I think the correct fix is not to add signature_v2 = true but to set the correct value for the region parameter. I have never needed to set signature_v2 = true myself. Anyway, the docs gives a correct config so I'm closing this.

> To workarround this , you have to specify your region and signature_v2 = true I think the correct fix is not to add `signature_v2 = true` but to set the correct value for the `region` parameter. I have never needed to set `signature_v2 = true` myself. Anyway, the docs gives a correct config so I'm closing this.

lx closed this issue

2024-02-07 16:24:51 +00:00

recolictmp commented

2024-02-23 21:46:27 +00:00

I had exactly same problem while setting up MSP360 backup software.

I tried to use signature v2 in MSP360, didn't work. (Unsupported authorization method)

And my solution is: modify garage.toml, set s3_region = "us-east-1" (match the error message), and problem get solved.

I had exactly same problem while setting up MSP360 backup software. I tried to use signature v2 in MSP360, didn't work. (Unsupported authorization method) And my solution is: modify `garage.toml`, set `s3_region = "us-east-1"` (match the error message), and problem get solved.