HEART security.certificate-expiring H-11003
Certificate expiring. A security certificate expires soon.
| Code | HEART security.certificate-expiring; inside a message "code": "security.certificate-expiring" |
|---|---|
| H-number | H-11003: area 11, code 003 |
| Area | security: Logins, certificates, tampering |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every connected product |
Likely causes
- A certificate is near its end date.
- Automatic renewal was never set up.
- Automatic renewal is failing, such as a renewal server that cannot be reached.
How to fix or prevent it
- Renew the certificate.
- Set up automatic renewal, or fix it if it is failing.
- Check the product's clock, so the dates are read right.
What the HEART does by itself
It raises a warning well before the end date, so there is time to act. It resolves when a new certificate is in place.
When to call service
If the certificate is built into the product and you cannot renew it yourself.
Related codes
security.certificate-expiredH-11004: Certificate expiredconnectivity.clock-unsyncedH-03004: Clock not synchronised
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)