Rclone sync s3 BadSignature

Help and Support
1

Running on Centos 7 with latest Rclone beta
Endpoint: s3.sirv.com

Using the same command with the same config on Linux Mint 19.3 works absolutely fine

2020/02/05 09:04:13 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2020/02/05 09:04:13 DEBUG : Using v2 auth
2020/02/05 09:04:13 DEBUG : arrow-grey.png: Need to transfer - File not found at Destination
2020/02/05 09:04:13 ERROR : arrow-grey.png: Failed to copy: s3 upload: 403 Forbidden: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Forbidden
BadSignature

FBtUIprVwn73blIw

2020/02/05 09:04:13 ERROR : Attempt 1/1 failed with 1 errors and: s3 upload: 403 Forbidden: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Forbidden
BadSignature

FBtUIprVwn73blIw

2020/02/05 09:04:13 Failed to sync: s3 upload: 403 Forbidden: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Forbidden
BadSignature

FBtUIprVwn73blIw

3

you use are using siganture 2, which is not compatible withs sirv.
you need to use signature 4

"https://sirv.com/help/resources/api/#Connect_to_your_Sirv_bucket"
Sirv’s S3 REST API lets you securely upload and manage files with either AWS Signature Version v3 or Signature Version v4 authentication

4

Thanks for the reply asdffdsa

I actually managed to resolve this by adding the following line to rclone.conf:

v2_auth = true

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.