Result:
403 Forbidden: <?xml version=“1.0” encoding=“UTF-8”?>

<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>------------------------------</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256& #xA ;20190312T150703Z& #xA ;20190312/us-east-1/s3/aws4_request& #xA ;5dd733afa5194d5dc4634116a621ad66e790c5fa5fa1d206a98c1797105dd991</StringToSign><SignatureProvided

Suspicion:
Our Wasabi account seems to be in us-east-1, but the bucket rover.images is in us-west-1. I think this is causing the problem. But I’m not sure, and I do not know what to do about it.

Any recommendations would be appreciated.

Thank you
Steve Mullen

Are you using the latest release ?

My wasabi config looks like this - what does yours look like ( rclone config show Wasabi )

[wasabi]
type = s3
env_auth = false
access_key_id = XXX
secret_access_key = XXX
region = 
endpoint = s3.wasabisys.com
location_constraint = 
acl = 
server_side_encryption = 
storage_class = 
env_auth = true
access_key_id = ********************************
secret_access_key = *****************************************************
region = 
endpoint = s3.wasabisys.com
acl = public-read
If I set region to us-west-1, I get ‘Bad Request’ during the copy.  If I set it to us-east-1, I get ‘The request signature we calculated does not match the signature you provided’.
Thank you
              
I’ve also just added the empty params you provided:
server_side_encryption = 
storage_class = 
No difference, unfortunately.
env_auth = false
access_key_id = ****************************
secret_access_key = *************************************************
region = 
endpoint = s3.wasabisys.com
acl = public-read
server_side_encryption = 
storage_class =
The request signature we calculated does not match the signature you provided. Check your key and signing method.
I would like to point out that reading works:

rclone ls Wasabi:rover.images/vail
It seems to be only writing that is the problem.
              
I created a us-west-1 bucket and I can see the same problem.
When I try to use it I see a re-direct which gave me the idea of changing the endpoint.
If you use --s3-endpoint s3.us-west-1.wasabisys.com with your config above, does it work?