UpdraftPlus S3 Generic – authorization header is malformed

Can you leave the region blank?

I have checked the OVH documentation and it does look like this is allowed.

The region is determined by where the S3 space is located on OVH.
I don’t know where you’re seeing that in the documentation?

I have tested with an alternate backup plugin and the S3 details just work

If the storage is in the uk, why is “uk” not being used as the region?

Can you make sure you’re using the correct S3 endpoint for your bucket’s region ?

UpdraftPlus doesn’t have an option to set the region as the region should always be the same as the endpoint making the setting redundant.

the endpoint is as follows:
https://s3.uk.io.cloud.ovh.net/ so the region should be uk

if I change to Toronto its s3.ca-east-tor.io.cloud.ovh.net and the region for this should be ca-east-tor

But with each it seems to be sending us-east-1 with the UpdraftPlus_S3::putObject() request?

What region did you specify when you bought the storage: https://www.ovhcloud.com/en-gb/public-cloud/prices/#439

“A product provided at the “region” level runs on a specific region chosen by the customer when placing the order”: https://www.ovhcloud.com/en-gb/about-us/global-infrastructure/expansion-regions-az/

You will have need to selected London and set the bucket region as London as well.

It might be worth contacting OVH as well as I suspect this is something to do with your OVH account.

Hi

In both cases, I had to select the Region when adding the storage bucket, that dictates the endpoint of the created space.

Here’s the full details of the UK S3, the endpoint url is not editable

and the details for CA-EAST-TOR

• This reply was modified 4 weeks, 1 day ago by rmpnet. Reason: spelling

Hi,

First of all can you try changing the bucket name to something total unique that you have never used before

According to AWS, there are three scenarios that cause the error you are getting

1. When you are creating a bucket with a name that this already being used as a bucket name in your AWS account or in any other AWS account (Please note that S3 bucket names are globally unique).
2. When you are doing an operation on your S3 bucket and you have set the Region variable (either when configuring the SDK or while using environment variables etc) to a region other than the one in which the bucket is actually present.
3. You have recently deleted a S3 bucket in a particular region (say us-east-1) and you are trying to create a bucket (with the same name as the the bucket that was deleted) in another region right after deleting the bucket.

For point 3, give it up to two days and retry.

if a bucket which is present in a certain region say (us-east-1) is deleted, you can always create a bucket with the same name in another region. There is no such restriction in S3 that states you cannot do this. However, you will be able to do this only after you allow some time after deleting the bucket. This is because S3 buckets follow the Eventual Consistency model in the case of DELETE operation.

It means that after you delete a bucket, it takes a few hours, generally up-to 24 to 48 hours for the DELETE operation to be replicated across all our data centres. Once this change has propagated you can go ahead and create the bucket again in the desired region.