Object Storage: Getting SignatureDoesNotMatch when attempting to download from the Linode panel
I just set up a cron job on a database server to pull regular backups and upload them to a Linode Object Storage bucket with s3cmd.
However, when I attempt to download any of the backup files directly from within the Linode cloud manager panel, I get the following error:
<Error>
<Code>SignatureDoesNotMatch</Code>
<RequestId>tx0000000000000060e13c6-00602b366b-1e63d43-
default</RequestId>
<HostId>1e63d43-default-default</HostId>
</Error>
I've checked over my config for s3cmd, and I'm not seeing anything that would point to the issue. So far as I know, I've disabled GPG signing by commenting out the relevant lines, but I'm probably missing something.
Any help is greatly appreciated.
2 Replies
rgerke
Linode Staff
I looked into this, and it appears that this error could be triggered by special characters in the filename. This limitation is current to our Cloud Manager, and it's something we're looking to resolve.
If you use s3cmd or Cyberduck to download, you should not run into this issue and be able to access the files in your bucket.
Let me know if this helps!
That was it! It was special characters. I had a script that was appending the standard '%T' timestamp to the end of the filename, so it was something like "MYSQL_PROD_BACKUP_02_16_21_15:54:01.sql.gz"
Changing it to just '%H%M' (so just numerical 24-hour time) renders files I can download from the dashboard. It must have been the colons in the timestamp causing the error.
I can confirm that I was able to get what I needed just using s3cmd, but it's nice to have the convenience of the dashboard too.
Thanks a lot!