Failed to backup: HTTP Code: SignatureDoesNotMatch
-
Hi everyone,
I have changed my object storage - I am now using a minio instance hosted on my NAS at home (on docker). This night I received an email stating that the backup failed:
Error uploading snapshot/app_45400376-f92a-4f3c-b40c-71834791808d/siSsQsn8EaqA62J+VTSX2mZFM+AKuVFRlV8fEbBfEOk/P5nj0C9iSgFP+nCjPYREvXqCqTVgImpVvoLmHJTNIoE/5vuTuQMRwXeMhQt3cse5P7jJ7XWUQpUSsuQqhtM1DA4/O4Z4LQo3RclPtEsVuW3ple6kXRhZfiw7NdfmFeH-uos. Message: The request signature we calculated does not match the signature you provided. Check your key and signing method. HTTP Code: SignatureDoesNotMatch
However, when I check the backups page on cloudron, it looks like a full backup was performed. Unfortunately I cannot get any related info from the backup logs.
Any hint on how to resolve this?
Thanks a lot in advance.
-
@stantropics Maybe it was just a temporary network error. Usually SignatureDoesNotMatch means that access/secret key was incorrect. It is possible that this message actually came from your previous object storage and not from minio. What I mean is: maybe a backup was in progress and you changed to minio, in which case it will fail when doing operations in the "middle" of the backup with minio.
What you can do to double check is: click on clean backups in the Backups view. This will remove all the backups that were associated with the previous object storage and only the ones that are valid in minio will remain.
-
@stantropics So, if I understand correct, you get this error from email but the UI itself shows it got backed up. If that's the case, I think it means that Cloudron maybe retried the backup and then retry worked out. I will have to look into the server task logs to dig in further. If you continue to get this error, can you write to us at support@cloudron.io and I can investigate further?
