The Certificates guide and Order a certificate only knew DNS-01 and TLS-ALPN-01. On an installer setup that meant they never reused the installer's HTTP-01 Let's Encrypt account, and always added a TLS-ALPN-01 one, which can't validate while Caddy holds port 443. This is how forum t/279 ran into the server-set description bug.
Both guides now ask how Let's Encrypt reaches the server for names checked without DNS: port 80 (HTTP-01) or port 443 (TLS-ALPN-01) (DirectChoice, on the Account step).
The choice starts on port 80 when the server already has an HTTP-01 account (the installer makes one), so that account is reused. Otherwise it starts on port 443, as before.
The texts that said "port 443" now give the chosen port.
shared.ts: defaultDirect, challengeOf and providerFor replace CHALLENGE; addProvider takes the choice. There's a new shared.test.ts.
The server's listeners can't settle this: in a container install the HTTPS listener is on [::]:443 inside the container while Caddy holds the host's 443. So the existing account decides the default, and the admin can change it.
Local CI: typecheck, lint, i18n:check, tests (1085), the three shell tests, build and notice-check all pass. The release/2026 backport follows in a separate PR.
Fixes #206.
The Certificates guide and Order a certificate only knew DNS-01 and TLS-ALPN-01. On an installer setup that meant they never reused the installer's HTTP-01 Let's Encrypt account, and always added a TLS-ALPN-01 one, which can't validate while Caddy holds port 443. This is how forum t/279 ran into the server-set `description` bug.
- Both guides now ask how Let's Encrypt reaches the server for names checked without DNS: **port 80 (HTTP-01)** or **port 443 (TLS-ALPN-01)** (`DirectChoice`, on the Account step).
- The choice starts on port 80 when the server already has an HTTP-01 account (the installer makes one), so that account is reused. Otherwise it starts on port 443, as before.
- The texts that said "port 443" now give the chosen port.
- `shared.ts`: `defaultDirect`, `challengeOf` and `providerFor` replace `CHALLENGE`; `addProvider` takes the choice. There's a new `shared.test.ts`.
The server's listeners can't settle this: in a container install the HTTPS listener is on `[::]:443` inside the container while Caddy holds the host's 443. So the existing account decides the default, and the admin can change it.
Local CI: typecheck, lint, i18n:check, tests (1085), the three shell tests, build and notice-check all pass. The release/2026 backport follows in a separate PR.
The guides only knew DNS-01 and TLS-ALPN-01, so on an installer setup
they never reused its HTTP-01 Let's Encrypt account and always added a
TLS-ALPN-01 one, which can't validate while the installer's web server
holds port 443.
Both guides now ask how Let's Encrypt reaches the server for names
checked without DNS: port 80 (HTTP-01) or port 443 (TLS-ALPN-01). It
starts on port 80 when the server already has an HTTP-01 account, as an
installer setup does, so that account is reused; otherwise on port 443,
as before. The texts that said port 443 say the chosen port.
Fixes#206
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.
Fixes #206.
The Certificates guide and Order a certificate only knew DNS-01 and TLS-ALPN-01. On an installer setup that meant they never reused the installer's HTTP-01 Let's Encrypt account, and always added a TLS-ALPN-01 one, which can't validate while Caddy holds port 443. This is how forum t/279 ran into the server-set
descriptionbug.DirectChoice, on the Account step).shared.ts:defaultDirect,challengeOfandproviderForreplaceCHALLENGE;addProvidertakes the choice. There's a newshared.test.ts.The server's listeners can't settle this: in a container install the HTTPS listener is on
[::]:443inside the container while Caddy holds the host's 443. So the existing account decides the default, and the admin can change it.Local CI: typecheck, lint, i18n:check, tests (1085), the three shell tests, build and notice-check all pass. The release/2026 backport follows in a separate PR.