A certificate is expiring
Weik.io 2026.2A certificate Weik.io obtained for a gateway hostname expires within 14 days and its renewals have failed, or an uploaded certificate expires within 30 days.
| Kind | Severity | Who sees it |
|---|---|---|
certificate- |
Warning, and an error close to the end | Everyone who can read the gateway’s environment |
Its row in the problem list has a figure such as 12 days left.
What it means#
The certificate of a gateway hostname expires soon. Once it expires, callers’ TLS checks fail and they can’t call the APIs on that hostname.
What raises it#
For a certificate Weik.io obtained, the problem shows 14 days before the end, when its automatic renewals have failed, and becomes an error 3 days before. For an uploaded certificate, it shows 30 days before the end and becomes an error 7 days before. The detail gives the end time and the renewal’s last error, or the command that uploads a renewed certificate.
What to check#
See where the certificate comes from, its proof and its last error:
$ weikio describe certificate <hostname>List the certificates with their days left:
$ weikio get certificatesHow to fix it#
For a certificate Weik.io obtains, fix what made the renewal fail, such as a DNS record that no longer points at the hub or a DNS connection whose token expired, then renew it:
$ weikio certificates renew <hostname>For an uploaded certificate, upload the renewed one:
$ weikio gateway set <gateway> --server-certificate <name>=<chain.pem>,<key.pem>