Repository navigation
v1.0.48
What's fixed
The installer asks again — so the domain and the Cloudflare answer can be changed on any run. And it no longer gets "Automatic SSL/TLS" wrong.
- Every interactive installer run now prompts for the console address and for the Cloudflare SSL/TLS mode. Both prompts show the stored values as defaults, so Enter keeps the current setup; typing a new domain or changing the y/n answer updates .env (the WireGuard endpoint follows a domain change, and peers are reminded to re-download their configs). Non-interactive runs keep the stored values; CONSOLE_DOMAIN=... / WGCONSOLE_TLS=... override them for automation.
- The Cloudflare question now asks about Flexible only: Flexible is the only mode that needs a plain-HTTP origin (Caddy on :80, no TLS). Full, Full (strict) and Automatic SSL/TLS all expect the HTTPS origin that domain mode provides — Automatic probes the origin over HTTP and HTTPS and only ever upgrades the encryption mode, it never downgrades, so a plain-HTTP origin would prevent the upgrade. Default answer is N.
- New installs default to domain mode: Caddy obtains a public certificate and serves HTTPS on :443. WGCONSOLE_TLS=domain is an explicit, documented value; unknown legacy values fall back to domain mode instead of the IP-only listener.
- After the stack starts, a public-URL probe warns with the exact fix when it detects the Flexible redirect loop (it never changes configuration by itself).
- New scripts/tls-mode.sh (classification + resolution helpers) with tests, wired into the local test runner.
Upgrade with the usual installer (console rebuild); it will ask the two questions and keep your current values on Enter:
curl -fsSL https://raw.githubusercontent.com/garyhooi/wireguard-console/main/install.sh | sudo bash
Verified: tls-mode tests, firewall suite, AdGuard healthy-skip test, bash -n on every installer script, entrypoint sh -n.