Solus
SolusVM 2.0 Technical Questions
Installation

Fail to install SolusVM 2: failed to get aws auth token: InvalidSignatureException: Signature not yet current

Updated June 24, 2024 06:07

Bato Tsydenov

Have more questions? Submit a request

Applicable to:

SolusVM 2

Symptoms

Installation of SolusVM 2 is interrupted with the error:

CONFIG_TEXT: failed to install by config 'config.yml':
'failed to get aws auth token: InvalidSignatureException:
Signature not yet current:
20190728T220350Z is still later than 20190728T111912Z (20190728T110412Z + 15 min.)
status code: 400, request id: e0fd08fd-e353-4448-82ba-64a0f682ce6c'

Reason

Server time doesn't match the real-time.

Solution

Set the correct time on the server.

Articles in this section

Unable to add new CR running Ubuntu 22: unmet dependencies: debianutils : Breaks: ifupdown (< 0.8.36+nmu1)
How to create SolusVM 2 database backup?
Fail to install SolusVM 2: failed to get aws auth token: InvalidSignatureException: Signature not yet current
Failed to add Compute Resource in SolusVM 2: failed to check DNS resolution for "time.google.com"
How to downgrade SolusVM 2 to previous version
How to remove SolusVM 2 on Compute Resource?
SolusVM 2 installation failed: context deadline exceeded
Update prepare task in Queued status: failed to self-update: /usr/local/solus/bin/installer no such file or directory
Getting the error while redeploying SolusIO stack: failed to create service solus_postgresql: Error response from daemon: network solus_app-network not found
How to access SolusVM 2 database?

Comments

0 comments

Please sign in to leave a comment.