Certificates: order one with the names you choose, and order again #170

Merged

jcoffey-dev merged 3 commits from feature/order-certificate into main 2026-11-07 01:17:38 +00:00

Conversation 0 Commits 3 Files Changed 14

+1530 -169

3 Commits

Author	SHA1	Message	Date
jcoffey-dev	05de723f5c	Certificates: title the order guide's tab	2026-11-06 18:07:56 -07:00
jcoffey-dev	114ad2cc34	Certificates: don't send a description with a new Let's Encrypt account ... The server writes an ACME provider's description itself and refuses one from a client ("Cannot modify server set property"), so the guides could never add a Let's Encrypt account: "Certificates, automatically" only worked on servers that already had one. Both guides now leave it out.	2026-11-06 18:07:56 -07:00
jcoffey-dev	41b9f48a89	Certificates: order one with the names you choose, and order again ... "Order a certificate" on the Certificates page takes the names you want, finds the domain they belong to (or adds one just for certificates, with no DKIM keys and nothing published), checks the names the way the existing guide does, and sets them as that domain's certificate hostnames. The server orders per domain, so that's how a certificate with chosen names is ordered. Once it's issued the guide offers to make it the default certificate; connections asking for its names get it without that. Above the list, every automatic certificate shows the domain that renews it, the next renewal, and why the last order failed. Order again tells the queued renewal to run now; it only creates one when none is queued, since a second would keep renewing for good (inbuxa-server#290). The existing guide's loading, polling and name lookups move to shared.ts so both guides use them. (#167)	2026-11-06 17:54:33 -07:00