Settings › Certificates › Ordered automatically lists a domain as *.example.com, example.com · not issued yet when the domain's DNS is managed automatically but its Let's Encrypt account checks names over TLS-ALPN-01 (or HTTP-01). The certificate exists and renews normally; only the panel is wrong. Seen on console rc.23 against server rc.39, on every domain with automatic DNS and a TLS-ALPN account.
Cause
The server picks the names from the account's challenge (build_domains in common/src/network/acme/order.rs): DNS-01 or DNS-PERSIST-01 orders the domain and a wildcard; anything else orders mta-sts, ua-auto-config, autoconfig and autodiscover (plus the server's name and mail exchangers inside the domain).
CertificateOrdersPanel.tsx decides the method from dnsAutomatic instead (d.dnsAutomatic ? 'dns' : 'tls'), so it computes the wildcard pair, finds no certificate covering it, and says "not issued yet".
The order guide (OrderCertificatePage.tsx) uses the same guess for "what this domain orders today", so it can say an order replaces wildcard names the domain never had.
Effects
The panel looks like most automatic certificates were never issued, which sends people chasing a problem that isn't there.
The renewal date it shows still comes from the queued task, so it's right; the names and the "not issued yet" line aren't.
Fix
Take the method from the domain's own ACME account (acmeProviderId → its challengeType), and fall back to the DNS setting only when the account can't be found. The guides that set a domain up keep using the DNS setting to choose how to check names; that part is a choice, not a reading.
Settings › Certificates › **Ordered automatically** lists a domain as `*.example.com, example.com · not issued yet` when the domain's DNS is managed automatically but its Let's Encrypt account checks names over TLS-ALPN-01 (or HTTP-01). The certificate exists and renews normally; only the panel is wrong. Seen on console rc.23 against server rc.39, on every domain with automatic DNS and a TLS-ALPN account.
## Cause
- The server picks the names from the account's challenge (`build_domains` in `common/src/network/acme/order.rs`): DNS-01 or DNS-PERSIST-01 orders the domain and a wildcard; anything else orders mta-sts, ua-auto-config, autoconfig and autodiscover (plus the server's name and mail exchangers inside the domain).
- `CertificateOrdersPanel.tsx` decides the method from `dnsAutomatic` instead (`d.dnsAutomatic ? 'dns' : 'tls'`), so it computes the wildcard pair, finds no certificate covering it, and says "not issued yet".
- The order guide (`OrderCertificatePage.tsx`) uses the same guess for "what this domain orders today", so it can say an order replaces wildcard names the domain never had.
## Effects
- The panel looks like most automatic certificates were never issued, which sends people chasing a problem that isn't there.
- The renewal date it shows still comes from the queued task, so it's right; the names and the "not issued yet" line aren't.
## Fix
Take the method from the domain's own ACME account (`acmeProviderId` → its `challengeType`), and fall back to the DNS setting only when the account can't be found. The guides that set a domain up keep using the DNS setting to *choose* how to check names; that part is a choice, not a reading.
jcoffey-dev
added this to the 27.1 milestone 2026-11-22 03:24:28 +00:00
Fixed by #262 (a4de0c68) on main: the Ordered automatically panel and the order guide now read the method from the domain's own ACME account, and use the DNS setting only when that account can't be found. Ships in the next console release candidate (after 27.1-rc.23).
Fixed by #262 (a4de0c68) on main: the Ordered automatically panel and the order guide now read the method from the domain's own ACME account, and use the DNS setting only when that account can't be found. Ships in the next console release candidate (after 27.1-rc.23).
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.
Settings › Certificates › Ordered automatically lists a domain as
*.example.com, example.com · not issued yetwhen the domain's DNS is managed automatically but its Let's Encrypt account checks names over TLS-ALPN-01 (or HTTP-01). The certificate exists and renews normally; only the panel is wrong. Seen on console rc.23 against server rc.39, on every domain with automatic DNS and a TLS-ALPN account.Cause
build_domainsincommon/src/network/acme/order.rs): DNS-01 or DNS-PERSIST-01 orders the domain and a wildcard; anything else orders mta-sts, ua-auto-config, autoconfig and autodiscover (plus the server's name and mail exchangers inside the domain).CertificateOrdersPanel.tsxdecides the method fromdnsAutomaticinstead (d.dnsAutomatic ? 'dns' : 'tls'), so it computes the wildcard pair, finds no certificate covering it, and says "not issued yet".OrderCertificatePage.tsx) uses the same guess for "what this domain orders today", so it can say an order replaces wildcard names the domain never had.Effects
Fix
Take the method from the domain's own ACME account (
acmeProviderId→ itschallengeType), and fall back to the DNS setting only when the account can't be found. The guides that set a domain up keep using the DNS setting to choose how to check names; that part is a choice, not a reading.Fixed by #262 (
a4de0c68) on main: the Ordered automatically panel and the order guide now read the method from the domain's own ACME account, and use the DNS setting only when that account can't be found. Ships in the next console release candidate (after 27.1-rc.23).