`xvc storage new r2`
iesahin opened this issue · comments
There is a bug with s3cmd
on R2. s3tools/s3cmd#1273
We can try a workaround with "--no-check-md5" option.
That option didn't work. xvc is able to put the files with the same credentials.
The actual error I'm getting for s3cmd is
ERROR: S3 error: 403 (SignatureDoesNotMatch): The request signature we calculated does not match the signature you provided. Check your secret access key and signing method.
I'm still getting the same error.
I changed signature_v2 = False
and got another error saying "ERROR: S3 error: 401 (Unauthorized): SigV2 authorization is not supported. Please use SigV4 instead."
I found the solution. My host_bucket
configuration in s3cmd
config was incorrect. Fixed it.