These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Amazon S3 back up failure on the new forum.
Hi everyone. I'm using the latest version of webmin/virtualmin with all updates installed. I have this running on centos 7.
I have signed up for Amazon S3 and have created a bucket and configured this in virtualmin. I can't view the bucket in the Amazon S3 bucket bit of virtualmin.
I have just tried to run a backup, but right at the end where it tries to upload the backup, it fails as follows:
Uploading archive to Amazon's S3 service .. .. upload failed! Invalid HTTP response : HTTP/1.1 400 Bad Request
What can I do to sort this or work out what is failing?
Many thanks in advance. Craig
I've been playing around with this again this evening.
If I try to backup to a bucket in Europe (London or Frankfurt) it fails as above.
However, backing up to a bucket in US works fine.
Just wanted to chime in and say I had the same error. I'd created an IAM account at Amazon AWS that only had the relevant S3FullAccess permissions, and Virtualmin was unable to transfer backups to S3.
Selecting the "Do strftime-style time substitutions on file or directory name" and "Create destination directory" options on Virtualmin's backup configuration page resolved the issue for me.
I am having the same problem as Craig in eu-west-2 (London). christefano's work-around does not resolve the issue for me.
Got the same problem. We're using S3 in Ireland, which works, but Virtualmin still can't backup to the London S3 servers it seems.
All the log says is this: Uploading archive to Amazon's S3 service .. .. upload failed! Invalid HTTP response : HTTP/1.1 400 Bad Request
Hi Same error here to Paris region ... tried to install the aws client ... Did you solve your problem ? Pierre.
Any updates anyone? I've just signed up for S3 and have hit exactly the same problem. Backing up to the US works, London doesn't.
Ours works now. I'm not sure when it happened, but I just double-checked, and we are indeed running on the London S3 now.
Thanks havfrue. I'll keep my fingers crossed that ours just needs time to settle in too! I appreciate knowing there is hope :)
After the latest update, this problem is back. Now we're getting the error on S3/London again, but only London - Cali is fine for example. Uploading archive to Amazon's S3 service .. .. upload failed! Invalid HTTP response : HTTP/1.1 400 Bad Request
I think it's because these servers do not support version 2 signatures:
Another post suggested that I install the AWS command line interface as a package - this didn't help either. Temporarily I have created a bucket in Ireland which works fine.
Well it works now again. I think the only thing that happened was a Perl update.