Backups no longer sent to Wasabi (S3 Compatible) bucket

[Benjamin LittonParticipant]

Hi,

I have had daily backups of my site taken and sent to a Wasabi bucket via the “S3-Compatible (Generic)” remote storage option for over a year. Everything worked great until recently, and now UpdraftPlus fails to send the backups to Wasabi. When I test my S3 settings, the JS alert I get is:

S3 settings test result: Failure: We successfully accessed the bucket, but the attempt to create a file in it failed. Please check your access credentials. (UpdraftPlus_S3::putObject(): [6] Could not resolve host: [s3-location].[s3-end-point])

Recently I had a colleague help me troubleshoot from the Wasabi side, and he confirmed that he can access and write to the same bucket with the exact same settings via the Cloudberry backup application.

I read another forum where someone claimed that they have this remote storage issue ever since updating their site to WordPress 5.3, and this issue did start happening for me around the time I updated my site to WP 5.3. In any case, if you could please help me troubleshoot from your end, I would greatly appreciate it.

Please let me know what information you would like me to provide, and thank you in advance for your help.

Ben

[Bryle CroduaModerator]

Hi,

Could you send us a copy of your server’s PHP Error log?
You can find this log through your web hosting control panel (typically cPanel). If you are unsure where to find the PHP Error log, you can ask your hosts to provide it.

Regards,
Bryle

[Benjamin LittonParticipant]

This reply has been marked as private.

[Bryle CroduaModerator]

Hi,

Thanks for sending the PHP error log. However, we could not find much information in it that will provide us clue as to what causes the issue.

Are you able to send us a copy of the backup log too please?

Regards,
Bryle

[Benjamin LittonParticipant]

This reply has been marked as private.

[udadminKeymaster]

This is related to Amazon having deprecated “path-style” bucket access. Our code switched over to using “host-style” bucket access. Does your S3 provider provide host-style access? If they do, then you just need to set up the missing DNS record (the one mentioned in your error message).

We are also looking to revert the change for non-Amazon providers in the next release.

[Author]

Posts