Details
-
Type:
Task
-
Status: Done
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Sprint:MEN Sprint 50, MEN Sprint 51
-
Story Points:2
-
Backlog:yes
Description
A common problem is that the Mender client is unable to connect to the server and logs:
... level=info msg="Mender state: authorize-wait -> bootstrapped" module=mender ... level=error msg="authorize failed: transient error: authorization request failed: failed to execute authorization request: Post https://<SERVER-URI>/api/devices/v1/authentication/auth_requests: x509: certificate has expired or is not yet valid" module=state
Typically this is caused by incorrect time setting on the device. See https://docs.mender.io/troubleshooting/mender-client#certificate-expired-or-not-yet-valid for full explanation.
Since this is such a common problem we should add more context around the error message.
Acceptance criteria
- There are more log entries directly following the "...certificate has expired or is not yet valid" message that gives more context
- Stretch goal:
"Current clock is {CURRENT-CLOCK}, but certificate is only valid from {CERT-VALID-START} to {CERT-VALID-END}."
See https://docs.mender.io/troubleshooting/mender-client#certificate-expired-or-not-yet-valid for more information.
- Minimum:
"Verify that the clock on the device is correct. See https://docs.mender.io/troubleshooting/mender-client#certificate-expired-or-not-yet-valid for more information."
- These messages are only printed after this given error