You are not logged in.
Pages: 1
I upgraded to 4.3.2 and tried connecting to Amazon S3 but I keep on getting secret/key invalid. I know the secret/key are correct as I am using them on my live website(Bigtree 4.2.24). I checked S3 and we are using the right region.
Any ideas why it wouldn't connect?
Thanks
Offline
Is there a specific environment you're using you're trying to secret / key in (local, live, dev, etc)? It's possible that the AWS library in your vendor folder is out of date and that's causing issues. You could try running "composer update" and see if that fixes it.
Offline
Hey Tim,
This is my local using MAMP. I did a composer update and it updated aws to 3.81.5
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
- Updating aws/aws-sdk-php (3.81.3 => 3.81.5): Downloading (100%)
Writing lock file
Generating autoload files
I also did a clean install of BigTree and same issue.
Any other ideas?
Thanks
Offline
That's really strange. I tested in my local BigTree 4.3 install with your secret / key (from the live site) and it connected without any issues.
I think we'll need to dump the actual error being returned (which is hopefully informative). Can you modify line 14 of /core/admin/modules/developer/cloud-storage/amazon/update.php to add:
print_r($cloud->Errors);
die();
And then tell me what the error message says?
Offline
Tim,
This is the error:
Array ( [0] => Error executing "ListBuckets" on "https://s3.amazonaws.com/"; AWS HTTP error: cURL error 60: SSL certificate problem: unable to get local issuer certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) )
Offline
Thanks! It looks like this is due to your local system using an old certificate authority bundle for cURL calls. It looks like there's an option for specifying one in the AWS SDK so I'm going to see if we can specify the one bundled with BigTree. I'll let you know when I have more info!
Offline
Thanks Tim!!!
Offline
I've pushed a commit that should now use BigTree's local CA Cert bundle when calling S3 / CloudFront:
https://github.com/bigtreecms/BigTree-C … 0c2dcb2d8e
Offline
For some reason, I had to rename the cache/bigtree-ca-cert.pem file to something different to get mine working again, no clue why it stopped working at some time. Otherwise, I was getting an error (after changing the amazon cloud update php file to spit it out)
Array ( [0] => Error executing "ListBuckets" on "https://s3.amazonaws.com/"; AWS HTTP error: cURL error 77: (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) )
Offline
I believe BigTree 4.4.13 released a fix for that issue. The root cause of it was that the URL where BigTree was downloading the certificate bundle from changed -- it was providing a 301 response but the cURL request wasn't following the redirect to the new URL. That led to all future cURL requests failing after the bundle was corrupted.
Offline
Pages: 1