S3 backup compatibility with Linode object storage
Trying to use Linode's S3 compatible storage object, but failing and getting an error. Has anyone use Linode object storage for WHM backups before?
The error I am getting is "Error: Validation for transport "Linode Object Storage" failed: Could not upload test file: SignatureDoesNotMatch:".
Using WHM 86.0.21 on CentOS 7.8.
Thank you.
-
I don't know a whole lot about Linode's S3 compatible object storage but this error usually means the access key or access ID is incorrect. 0 -
Created a new access/secret key pair and tried it. When I tried to save and validate, I got the following error. Error: Validation for transport "Linode Object Storage" failed: Could not list files in destination: Can't use an undefined value as an ARRAY reference at /usr/local/cpanel/Cpanel/Transport/Files/AmazonS3.pm line 315. Does that help point in any direction? 0 -
I just checked the contents of the bucket and found the following file was created:
With this, I believe the access/secret key pair is working fine. If I try to validate again, I now get the "Error: Validation for transport "Linode Object Storage" failed: Could not upload test file: SignatureDoesNotMatch:" message.validate.tmp-27520-1591280987.txt 84 bytes a few seconds ago 0 -
I believe you're right, I think this might be best investigated by one of our analysts. Can you please open a ticket using the instructions in the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks! 0 -
I am having problems with this as well. Was there ever a resolution with the original problem? I am getting the following error message: Validation for transport "Linode Object Storage" failed: Could not upload test file: Timeout 0 -
I moved on to another form of backup. The S3 compatible would have been nice, but wasn't a show stopper for us. Sorry I am not any help. 0 -
@brianc - you're always welcome to open a ticket to have our team check out your machine! 0 -
In a recent ticket where the "SignatureDoesNotMatch" error was seen, the issue was found to be with the 'host' being used for the Linode S3 destination. The host was set to 'test.us-east-1.linodeobjects.com' where 'test' matched the bucket name. Since the bucket name is specified elsewhere in the configuration, simply setting the host to 'us-east-1.linodeobjects.com' allowed the destination to validate and successfully upload a test file. 0
Please sign in to leave a comment.
Comments
8 comments