ERROR: Cannot transfer backup to S3! (403)

I must test for it. I will come back if i have done it.

Hello, on my test it works without problems. Please look that the setting for Multipart Uploads is deactivated.

Thanks. When looking for the Multipart setting (I still haven’t found it yet). I have noticed that for all sites on one server the “Bucket selection” has the message: “No bucket found!”. I have verified the keys and they are correct.

On my other server, the bucket is there, and the message has changed slightly; “ERROR: Cannot transfer backup to S3! (400)”

Oh, and where’s the multipart setting?

The multipart setting is in the tab with the S3 Settings.
With PHP Version did you use. Because BackWPup has two S3 Clinest one for PHP 5.2 and one for PHP 5.3 and above.

Server 1, located in the UK (can’t see the bucket);
+ 5.3.2-1ubuntu4.23.
+ no multipart settings on the tab (see: https://uploadpie.com/6zYeH)
Jobs give the error: “ERROR: Cannot transfer backup to S3! (403)”

Server 2, located in the Netherlands (can see the bucket)
+ 5.2.17
+ no multipart settings on the tab (see: https://uploadpie.com/6G7wc)
Jobs give the error: “ERROR: Cannot transfer backup to S3! (400)”

On Server 1 i think the the PHP Version will not correctly detected.
Please look in the General tab is there standing somwhat about v1 on the S3 destination.

I think best is upgrad the PHP Versions. I will look again in the old S3 api if i can find anithing there.

The old works too in my tests. Did you have set special rights?

Yes, on the first server it’s set to “Backup to an S3 Service v1”.

Not sure about special rights – it’s possible; is there an easy way I can check?

Unfortunately upgrading the PHP version is not currently an option.

Ups, i see that the newer AWS-sdk needs PHP 5.3.3 and you server has Version 5.3.2. That means thet the PHP Version is corectly detected, but to old for the new SDK and that is why the old SDK will use.

I will try to test it again wit the old php 5.2.17

Sorry but this test has nothing changed too. It works.

It looks like that ther is somthing wrong with the autentication.

Please check that you use the google interoperable Keys for authentication.

I’ve just double-checked the keys and tried again; still the same “No bucket found!” error.

I’ve changed the backup to my Amazon s3 account; and get exactly the same error.

Very strange.

I ther a firewall or proxy that must used for the connection?

No – not that I’m aware of. The backup on all the sites just stopped working on the 16th March – all with the same error.

Sorry, but i don’t have more ideas for the moment.

OK, many thanks. I will chase it up with my hosting company from this end.