Also, my S3 Access Key is showing up in the log. Why?!
Hi,
Please can you provide a link to your log file for the problematic backup? (You can download it from the “Existing Backups” tab of your UpdraftPlus settings page).
It’ll be too long to paste into the forum here, but you can download it to your computer, and share it with Dropbox, or paste it in pastebin.com, or any similar service, and post the link here.
Also – what region is the bucket you’re trying to access in?
Best wishes,
David
Hey David, I’m having the same issue with S3 as netpagz. We’re using MainWP with Updraft.
Here’s there log part where S3 fails:
34050.566 (9) No database backup (wp) - not part of this run
34050.567 (9) Saving backup history
34050.568 (9) backup_2015-11-09-2144_GGHC_98f0ffb4b646-plugins.zip: plugins: This file has not yet been successfully uploaded: will queue
34050.569 (9) backup_2015-11-09-2144_GGHC_98f0ffb4b646-themes.zip: themes: This file has not yet been successfully uploaded: will queue
34050.569 (9) backup_2015-11-09-2144_GGHC_98f0ffb4b646-uploads.zip: uploads: This file has not yet been successfully uploaded: will queue
34050.570 (9) backup_2015-11-09-2144_GGHC_98f0ffb4b646-others.zip: others: This file has not yet been successfully uploaded: will queue
34050.572 (9) Requesting upload of the files that have not yet been successfully uploaded (4)
34050.573 (9) Cloud backup selection (1/1): s3 (last)
34050.829 (9) Beginning dispatch of backup to remote (s3)
34053.047 (9) S3 Error: Failed to initialise: Invalid signature type: s3 (line: 444, file: /home/xxxxxx/public_html/wp-content/plugins/updraftplus/oc/aws/Aws/Common/Client/ClientBuilder.php)
34053.159 (9) [S3] XXXXXXXXXXXXAWSKEY Error: Failed to initialise
34054.242 (9) Error message: S3 Error: Failed to initialise: Invalid signature type: s3 (line: 444, file: /home/xxxxxxx/public_html/wp-content/plugins/updraftplus/oc/aws/Aws/Common/Client/ClientBuilder.php)
34054.244 (9) An error condition has occurred for the first time during this job
34054.246 (9) Retain: beginning examination of existing backup sets; user setting: retain_files=15, retain_db=15
34054.247 (9) Number of backup sets in history: 4
34054.248 (9) Examining backup set with datestamp: 1447105461 (Nov 09 2015 21:44:21)
We’re deploying to default US east coast region. It works on some sites and not on others. Can’t see any specific pattern. Plus, this specific site where I got this log is tiny, 50mb if that.
I’m not 100% sure, but from a quick look at S3 files, it looks like you might be using v2 of the AWS SDK and there is version 3 available. I might be wrong though, I saw in one of the files v2 mentioned.
Viktor: as you the same Viktor who’s posted in our customer support system at updraftplus.com? WordPress.org rules don’t allow queries for commercial purchases to be dealt with on their website – https://codex.wordpress.org/Forum_Welcome#Commercial_Products – so please post always here instead: https://updraftplus.com/paid-support-requests/
Best wishes,
David
Apologies – you’re not the same Viktor, I think!
Add this to your wp-config.php, near the top, and try a fresh backup:
define(‘UPDRAFTPLUS_S3_OLDLIB’, true);
David
Thanks David. Not the same Viktor. I haven’t purchased Pro version yet, I’m testing free version first to work out kinks like this. I will test and let you know how it goes.
Looks that worked David. I’ll keep an eye on it to see if the error shows up. I’m curious, did this switch to an older library or newer? Thanks.
Hi Viktor,
Not older or newer, really – it uses a different S3 library, rather than the official Amazon one.
Concerning the official Amazon one and its version, the 3.x series requires PHP 5.5+, whereas that’s only a minority of WP users currently: https://wordpress.org/about/stats . Amazon actively maintain the 2.8 series still.
David
Thanks David, makes sense.
hi everybody / David,
i have just installed the updraftplus plugin and ran into the same error (Error message: S3 Error: Failed to initialise: Invalid signature type: s3).
adding define(‘UPDRAFTPLUS_S3_OLDLIB’, true); in my wp-config.php fixed the issue.
i still want to use this plugin however on a lot more sites, and i’m afraid that one day this ‘fix’ will no longer work.
is is not possible that the plugin checks which library is needed, and then based on that uses the right library that will work?
