Amazon S3 backup fails when region is not US Standard

When trying to backup to an Amazon S3 bucket that is created in regions other than US Standard (we have tried Oregon and Sydney) through the virtualmin backup module, we get the following error (bucket name replaced with xxxx's):

File does not exist: Can't connect to (certificate verify failed)

LWP::Protocol::https::Socket: SSL connect attempt failed with unknown errorerror:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed at /usr/share/perl5/LWP/Protocol/ line 51. at S3/ line 26

If we create an identical bucket in the US standard region, the backup works correctly.



Does your bucket name perhaps have dots in it? That is going to cause problems due to the way Amazon redirects requests for non-US buckets. For example, if your bucket is named you may get directed to the API endpoint by the S3 server. However, if Amazon only has an SSL cert for * , this hostname will not match the cert and you'll get an error like the one you saw.

The only work-around is to have a bucket without dots in the name. Does that work for you?

Hi Jamie,

Ah ok.... yes it does have dots in it. Changing the bucket name to not include dots should be ok - I will test and confirm that it works.

Hi Jamie,

As a follow up, taking out the dots in the bucket name has resolved the issue.

Thanks for the quick response.

Automatically closed -- issue fixed for 2 weeks with no activity.

This is still a bug in 4.18gpl no validation to prevent the use of a bucket with dots in - this just fails. I believe this either needs to be validated against or the at S3/ file updated to handle buckets with dots in

The 5.0 Virtualmin release will fix this.

Removing the dots from bucket names resolved the error on my machine

Operating system Ubuntu Linux 16.04.2 Webmin version 1.831 Virtualmin version 5.07

Does the dot issue still exist in Webmin 1.900? I'm not having trouble doing backup to S3 but am having issues restoring from S3 at DigitalOcean and have a dot in my object like...


I have tried both the Virtualmin GUI method as well as the Virtualmin command line like this...

virtualmin restore-domain --all-features --all-virtualmin --source s3://ACCESSKEY:PRIVATEKEY@bucket-name/object.1/

@colech - what's the exact error message that you are getting?

I just did some testing with the latest versions of Virtualmin and Webmin and a bucket named in the Singapore S3 region, and was able to backup to it just fine.

Unfortunately, I still have this issue. I cannot backup or list content and this is the error.

HTTP/1.0 500 Perl execution failed Server: MiniServ/1.942 Date: Sun, 7 Jun 2020 14:23:31 GMT Content-type: text/html; Charset=iso-8859-1 Connection: close Error - Perl execution failed File does not exist: Can't connect to (certificate verify failed) LWP::Protocol::https::Socket: SSL connect attempt failed with unknown error error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed at /usr/share/perl5/LWP/Protocol/ line 41. at S3/ line 26.

S3 account key UGITFIYTFIYTFTYFI Bucket name Storage location eu-central-1

This is what I can check on DNS side: Server: Address:

Non-authoritative answer: canonical name = Name: Address:

Make sure you have the aws CLI command installed on your system, it provides a more reliable client for the S3 API.

Hi, thanks, installing the AWS cli solved the problem.

JetBackup 5 is supporting a lot of new admin panels... don't think they have done Virtualmin yet but if they do it's a pretty affordable and very robust backup solution. I'd keep checking in on it and I bet they will support it eventually as that's where they are heading.