mrrsm Posted November 27, 2013 Report Share Posted November 27, 2013 Package Info: Blest version 3.0.6 PHP 5.3.27 (cgi-fcgi) (built: Oct 25 2013 10:24:08) Copyright © 1997-2013 The PHP Group Zend Engine v2.3.0, Copyright © 1998-2013 Zend Technologies with the ionCube PHP Loader v4.4.4, Copyright © 2002-2013, by ionCube Ltd., and with Zend Guard Loader v3.3, Copyright © 1998-2010, by Zend Technologies OpenSSL 1.0.0-fips 29 Mar 2010 curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz URL: /admin/settings/system/backup/upload/ The error I was receiving was: error: SSL: certificate subject name '*.s3.amazonaws.com' does not match target host name [bLESTA INSTALL URL]' The easy fix was to use a bucket name without the period in it but it still should be able to use any valid bucket name which would include the period. A similar problem was reported in Drupal https://drupal.org/node/1673888 Link to comment Share on other sites More sharing options...
Paul Posted November 27, 2013 Report Share Posted November 27, 2013 Thanks for the report. Can anyone else confirm? Link to comment Share on other sites More sharing options...
Cody Posted November 27, 2013 Report Share Posted November 27, 2013 What was the name of your bucket? As per AmazonS3 bucket rules, a bucket can not start with, end with, or contain more than one period in a row. Link to comment Share on other sites More sharing options...
mrrsm Posted November 27, 2013 Author Report Share Posted November 27, 2013 What was the name of your bucket? As per AmazonS3 bucket rules, a bucket can not start with, end with, or contain more than one period in a row. The same url as my blesta instance is on which follows the rules as I use that format for some other sites buckets. subdomain.domain.com Link to comment Share on other sites More sharing options...
Cody Posted December 16, 2013 Report Share Posted December 16, 2013 This is a "Won't Fix" issue. SSL wildcard certs only work for a single subdomain of the cert'd domain. So *.s3.amazonaws.com works only for something.amazonaws.com, not something.something.s3.amazonaws.com. Since buckets are accessed via [bucketname].s3.amazonaws.com you can't have periods in your bucket name and connect to them via SSL. Instead, to do this you must use something like cloudfront, but Blesta does not yet allow you to specify the host for the AmazonS3 connection. Consider replacing periods with hyphens in your bucket name or open a feature request to add support for cloudfront. Link to comment Share on other sites More sharing options...
Recommended Posts