inbuxa certs retries the certificate order only on the install's own domain (st.Domain, internal/apply/certs.go, Renew). The server adds its hostname to a domain's certificate only when the hostname is inside that domain's zone (server crates/common/src/network/acme/order.rs, build_domains). So with --mail-host on another domain, certs re-orders a certificate that will never include it, waits three minutes, and fails.
Fix: order on the domain that covers --mail-host. If none does, say so and name what to do: add the name to a domain's certificate, as the console's Order a certificate does, or let certs do that through the API key.
Test: an e2e case with the mail host on a second domain.
Split out of #81.
`inbuxa certs` retries the certificate order only on the install's own domain (`st.Domain`, `internal/apply/certs.go`, `Renew`). The server adds its hostname to a domain's certificate only when the hostname is inside that domain's zone (server `crates/common/src/network/acme/order.rs`, `build_domains`). So with `--mail-host` on another domain, `certs` re-orders a certificate that will never include it, waits three minutes, and fails.
**Fix:** order on the domain that covers `--mail-host`. If none does, say so and name what to do: add the name to a domain's certificate, as the console's Order a certificate does, or let `certs` do that through the API key.
**Test:** an e2e case with the mail host on a second domain.
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 16:07:04 +00:00
Fixed in #87 (4e761b2). certs orders on the domain that covers the mail host, adding a certificate-only domain when the server has none, and keeps names entered in the console on retries. If the server's hostname is still the old name, it says where to change it. Tested in the lab with e2e/cases/rename.sh (#88).
Fixed in #87 (4e761b2). `certs` orders on the domain that covers the mail host, adding a certificate-only domain when the server has none, and keeps names entered in the console on retries. If the server's hostname is still the old name, it says where to change it. Tested in the lab with `e2e/cases/rename.sh` (#88).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split out of #81.
inbuxa certsretries the certificate order only on the install's own domain (st.Domain,internal/apply/certs.go,Renew). The server adds its hostname to a domain's certificate only when the hostname is inside that domain's zone (servercrates/common/src/network/acme/order.rs,build_domains). So with--mail-hoston another domain,certsre-orders a certificate that will never include it, waits three minutes, and fails.Fix: order on the domain that covers
--mail-host. If none does, say so and name what to do: add the name to a domain's certificate, as the console's Order a certificate does, or letcertsdo that through the API key.Test: an e2e case with the mail host on a second domain.
Fixed in #87 (
4e761b2).certsorders on the domain that covers the mail host, adding a certificate-only domain when the server has none, and keeps names entered in the console on retries. If the server's hostname is still the old name, it says where to change it. Tested in the lab withe2e/cases/rename.sh(#88).