DreamObjects issue

Hi,

To help us work out the cause of your problem, can you please send us a copy of the complete back log?
You can find this log in the ‘wp-content/updraft’ directory of your site via FTP.
You can send the log file as an attachment or copy the contents into an online tool (such as https://pastebin.com/ )

Regards,
Bryle

Thanks!

Since I do not wish to publicly disclose the domains (the problem is related to SSL authentication with DreamObjects), I prefer not to put the log here. I can email it to you if you provide an address. However, the problem, according to Dreamhost is not mine – but general with regard to the connection between Dreamhost and Updraft. Maybe best is to discuss it with them?

Yours,

Hagai

What I see at the log though is:

DreamObjects: Error: Failed to access bucket xxx.xxx. UpdraftPlus_S3::putBucket(xxx.xxx, private, us-east-1): [51] SSL: no alternative certificate subject name matches target host name ‘xxx.xxx.objects-us-east-1.dream.io’ (line: 483, file: xxx/wp-content/plugins/updraftplus/includes/S3.php)
0018.359 (0) An error condition has occurred for the first time during this job

Does your bucket name have periods in it?

Yes, all my buckets have periods in them – the names represent the domain they are connected to. However, these names have not changed in the last years and worked just fine. The problem started on Nov 16 without any change in parameters on my side.

Thanks,

Hagai

Since none of the code in UpdraftPlus has changed in that time (there hasn’t been an update since before then), then the change is presumably that DreamObjects have changed how they are generating their SSL certificates, so that their SSL certificates no longer will match that style of bucket. They might not have done it deliberately.

This conversation kind of stopped abruptly, but I think it did hit on the answer. I was having the exact same problem, and my bucket names did have periods in them. I simply created new buckets without periods in them to store my UpdraftPlus backups, and everything immediately started working. I don’t fully understand what caused the problem, but this simple solution solved it for me.

Apologies for not updating here (we continued the discussion directly with Dreamhost support). Indeed, the solution was to define buckets without periods in them. I guess that Dreamhost changed the Dreamobjects technology, and now a period makes it seems that the domain is different than the one used for the SSL certificate.