Cryptic S3 error: HTTP/1.1 400 Invalid URI: isHexDigit

Submitted by glimmung on Wed, 11/09/2016 - 06:39 Pro Licensee

Hi,

I've just added backups to AWS to a Virtualmin Pro instance, and am getting the (to me) cryptic message: -

HTTP/1.1 400 Invalid URI: isHexDigit

The target URI was simply cut and pasted from a working instance and the bucket name changed, and it is: -

my-bucket/virtualmin/weekly/%Y-%m-%d.%H%M

...so I don't think that it is this URI that is referred to.

I'm a bit stumped as to ho to troubleshoot this, as backups normally "just work" - any clues?

TIA,

--

PhilK

Status: 
Active

Comments

Submitted by andreychek on Wed, 11/09/2016 - 09:40

Howdy -- yeah that is an odd sounding error!

If you look in the backup settings for that particular backup, can you verify that these two options are enabled:

Do strftime-style time substitutions on file or directory name
Create destination directory

I'm curious if one of those not being enabled could be triggering an unusual issue.

Submitted by JamieCameron on Wed, 11/09/2016 - 22:51

Also, what language is your system configured to use? If it's not english, that date format might generate month names with accented characters in them.

Submitted by christefano on Sat, 03/03/2018 - 17:40 Pro Licensee

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 those two options ("Do strftime-style time substitutions on file or directory name" and "Create destination directory") resolved the issue for me.

Submitted by JamieCameron on Sun, 03/04/2018 - 18:42

I guess the "Create destination directory" option was the critical one. Unless you were using %d codes in your backup path previously, but they weren't converted to days or times?