HEART security.certificate-expired H-11004
Certificate expired. A security certificate has expired.
| Code | HEART security.certificate-expired; inside a message "code": "security.certificate-expired" |
|---|---|
| H-number | H-11004: area 11, code 004 |
| Area | security: Logins, certificates, tampering |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Every connected product |
Likely causes
- A certificate was not renewed in time.
- Automatic renewal failed.
- The product's clock is wrong, so a valid certificate looks expired.
How to fix or prevent it
- Check the clock first.
- Renew the certificate, and install it.
- Set up automatic renewal, so it does not happen again.
What the HEART does by itself
It raises an error alert. Secure connections that rely on the certificate fail, as they must: a HEART does not turn off the check. It resolves when a valid certificate is in place.
When to call service
If you cannot renew it yourself.
Related codes
security.certificate-expiringH-11003: Certificate expiringconnectivity.clock-unsyncedH-03004: Clock not synchronisedconnectivity.dependency-unreachableH-03003: A service it relies on cannot be reached
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)