The Certificates guide only knows DNS-01 and TLS-ALPN-01 (CHALLENGE in src/features/certificates/shared.ts, and in CertificateSetupPage.tsx on release/2026). The installer sets Let's Encrypt up with HTTP-01, because Caddy holds port 443 and forwards /.well-known/acme-challenge/ on port 80 to the server (EnableACME in inbuxa-installer internal/jmap/setup.go).
So on an installer setup:
the guide never reuses the installer's account (providerFor matches on challenge type), and always creates a new one;
for a domain without automatic DNS it picks TLS-ALPN-01, which can't validate while Caddy holds 443.
The first point is how forum topic 279 hit the server-set description bug on 2026.x (fixed on main in 114ad2c, on release/2026 in #205).
Fix: treat an existing HTTP-01 account as usable for the "tls" method (or add an "http" method), and prefer HTTP-01 when port 443 isn't the server's. Both main and release/2026.
The Certificates guide only knows DNS-01 and TLS-ALPN-01 (`CHALLENGE` in `src/features/certificates/shared.ts`, and in `CertificateSetupPage.tsx` on release/2026). The installer sets Let's Encrypt up with HTTP-01, because Caddy holds port 443 and forwards `/.well-known/acme-challenge/` on port 80 to the server (`EnableACME` in inbuxa-installer `internal/jmap/setup.go`).
So on an installer setup:
- the guide never reuses the installer's account (`providerFor` matches on challenge type), and always creates a new one;
- for a domain without automatic DNS it picks TLS-ALPN-01, which can't validate while Caddy holds 443.
The first point is how forum topic 279 hit the server-set `description` bug on 2026.x (fixed on main in 114ad2c, on release/2026 in #205).
Fix: treat an existing HTTP-01 account as usable for the "tls" method (or add an "http" method), and prefer HTTP-01 when port 443 isn't the server's. Both main and release/2026.
Fixed in #209 (main, next 27.1 RC) and #210, released as v2026.10.26.7. The guides now ask whether Let’s Encrypt reaches the server on port 80 or 443, and default to port 80, reusing the installer’s HTTP-01 account, when there is one.
Fixed in #209 (main, next 27.1 RC) and #210, released as v2026.10.26.7. The guides now ask whether Let’s Encrypt reaches the server on port 80 or 443, and default to port 80, reusing the installer’s HTTP-01 account, when there is one.
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.
The Certificates guide only knows DNS-01 and TLS-ALPN-01 (
CHALLENGEinsrc/features/certificates/shared.ts, and inCertificateSetupPage.tsxon release/2026). The installer sets Let's Encrypt up with HTTP-01, because Caddy holds port 443 and forwards/.well-known/acme-challenge/on port 80 to the server (EnableACMEin inbuxa-installerinternal/jmap/setup.go).So on an installer setup:
providerFormatches on challenge type), and always creates a new one;The first point is how forum topic 279 hit the server-set
descriptionbug on 2026.x (fixed on main in114ad2c, on release/2026 in #205).Fix: treat an existing HTTP-01 account as usable for the "tls" method (or add an "http" method), and prefer HTTP-01 when port 443 isn't the server's. Both main and release/2026.
Fixed in #209 (main, next 27.1 RC) and #210, released as v2026.10.26.7. The guides now ask whether Let’s Encrypt reaches the server on port 80 or 443, and default to port 80, reusing the installer’s HTTP-01 account, when there is one.