I’m seeing the same thing. I had mine up and running running for about a week before failing tonight and last night with this error.
From my log
[08-Mar-2014 04:16:38] Compressing files as TarGz. Please be patient, this may take a moment.
[08-Mar-2014 04:19:46] Backup archive created.
[08-Mar-2014 04:19:46] Archive size is 1.10 GB.
[08-Mar-2014 04:19:46] 14517 Files with 1.65 GB in Archive.
[08-Mar-2014 04:19:46] 1. Trying to send backup file to S3 Service …
[08-Mar-2014 04:19:46] ERROR: S3 Service API: Invalid signature type: s3
[08-Mar-2014 04:19:46] 2. Trying to send backup file to S3 Service …
[08-Mar-2014 04:19:46] ERROR: S3 Service API: Invalid signature type: s3
[08-Mar-2014 04:19:46] 3. Trying to send backup file to S3 Service …
[08-Mar-2014 04:19:46] ERROR: S3 Service API: Invalid signature type: s3
[08-Mar-2014 04:19:46] ERROR: Step aborted: too many attempts!
Can you try to reset the API keys?
I did and no luck, created new keys and gave Admin rights, even though the old ones still work
I did experienced a problem with the credentials, which maybe the source of this problem. Since the ‘API secret’ field is marked as a password field, several browsers (definitely Safari) will correct the inserted values back to any username/password combinations that you’ve saved for that website. Which makes it impossible to configure S3.
no, no Safari used to configure, Chrome is the browser by choice used to configure, also no Mac used, it was done in a Windows 8.1 computer.
Server is a CentOS 6 64 bits with the latest and greatest patches and updates, funny thing is that it was working, it worked for two days, then stopped doing it, and during those days nothing changed in the server, no updates, no configuration changes, nothing… so I’m thinking this could be more of an Amazon change and that the plugin is not compatible with the new Amazon API or something
Hmmm, i can’t find a problem in moment.
I still have this issue. I deleted the old key and put a new S3 key in, but it still has the same problem.
In the S3 settings section of the job details, under S3 Bucket, it says
Bucket selection Invalid signature type: s3
Did you have a test envojerment where i can test for it?
For whoever having the Invalid signature type:s3 error. My problem was have eAccelerator for PHP turned on. As soon as I deactived it, all worked. Its not a great solution to just turn it off, but at least its a temp one until it is fixed
That fixed it for me too. I recompiled PHP and Apache (WHM EasyApache) without eAccelerator and the backup works now. Lovely!
