I have four virtual virtual servers which I backup daily to an Amazon S3 bucket for a few years now (one file per server). About a week ago the backup started to fail for one of the virtual servers. The error message I get:
Error message: Uploading archive to Amazon’s S3 service … upload failed! Empty response to HTTP request. Headers were :
(I can’t find anything else in any of the other log files.)
The file is about 200MB and the backup process gets cancelled after approx. 40 minutes.
The other virtual servers of the backup are backed up just fine. I made a manual backup out of the scheduled backup (download in browser) and that went just fine.
I’ve been having this issue as well - on a server that’s not changed (other than updates) and has been running and backing up fine for months now. Suddenly about half the virtual servers are failing. I’ve tried setting up a new VPS with a new virtualmin instance and importing all the servers into that but still the same result.
As with crus above, I can still download all the backups in my browser no problem.
Running Virtualmin 6.06-2 on Ubuntu 18.04.2. Backups are to an Ireland bucket.
I ‘solved’ my issue by migrating to a US based region (Oregon, to be precise), backups have been working fine since then. Not quite the fix I wanted, but it is working and that’s the most important thing.
Different regions seem to have different setups (I’ve never been able to use London, for example), I guess something has changed at Amazon’s end to make virtualmin fail like this.
Thanks for letting me know how you were able to solve the issue. I tried it (moving everything from Ireland to Oregon) but I receive the same error for one specific domain. I will try to use a ftp server instead, perhaps it has nothing to do with s3 which I doubt.
J’ai laissé virtualmin choisir l’emplacment de stockage (usa au lieu de l’europe) et çà fonctionne un peu mieux, mais encore des problèmes auss d entête html…
I let virtualmin choose the storage location (usa instead of europe) and it works a little better, but still some html header problems too…
