A certificate request is failing
Weik.io 2026.2Requests for a gateway hostname's certificate keep failing at the certificate authority, and the detail gives the authority's error and the next attempt.
| Kind | Severity | Who sees it |
|---|---|---|
certificate- |
Warning, and an error while a site has no valid certificate for the name | Everyone who can read the gateway’s environment |
What it means#
The platform keeps failing to get a certificate for a gateway hostname from its certificate authority. While an earlier certificate is still valid, callers notice nothing yet.
What raises it#
A certificate request for the hostname has failed and is placed again later. The detail gives the authority’s error and when the next attempt is. For a site’s gateway, it’s an error while the site has no valid certificate for the name, and a warning while it still serves an earlier one.
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 certificatesSee the gateway’s hostnames and where their certificates come from:
$ weikio describe gateway <gateway>How to fix it#
The error says what the cause is. A name that points at the hub is proved on port 443, so its DNS record has to point at the hub and port 443 has to be open to the authority. A name proved through DNS needs a DNS connection that works, which weikio certificates dns test <name> checks. Once the cause is fixed, ask again at once:
$ weikio certificates renew <hostname>