Skip to content
Weik.ioDocs
2026.2
Try Weik.io

A certificate request is failing

Weik.io 2026.2

Requests for a gateway hostname's certificate keep failing at the certificate authority. The detail shows the authority's error and when the next attempt is.

On this page
Kind Severity Who sees it
certificate-request-failing 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#

Weik.io 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 failed. The detail shows the authority’s error and when Weik.io sends the request again. For a gateway at a site, the problem is a warning while the site still serves an earlier certificate, but an error while the site has no valid certificate for the name.

What to check#

See the certificate’s last error. The output also shows where the certificate comes from and how it’s proved:

Terminal
$ weikio describe certificate <hostname>

List the certificates with their days left:

Terminal
$ weikio get certificates

See the gateway’s hostnames and where their certificates come from:

Terminal
$ weikio describe gateway <gateway>

How to fix it#

The cause is in the authority’s error. What to check depends on how the name is proved:

  • A name that points at the hub is proved on port 443, so check that its DNS record points at the hub and that port 443 is open to the authority.
  • A name proved through DNS needs a working DNS connection. Test the connection with weikio certificates dns test <name>.

When you’ve fixed the cause, request the certificate again:

Terminal
$ weikio certificates renew <hostname>

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo