Correct the "web client requires HTTPS" claim across the wiki The client now runs over plain http:// using Media Source Extensions, so the pages saying it could not — and specifically that it "cannot be worked around in JavaScript" — were wrong and are corrected rather than softened. Web-Client-Requires-HTTPS rewritten: what each path gives you in a table, why the difference exists, and an explicit note that the page previously said the opposite. The filename is kept so existing links and any URLs already shared do not 404, but the title and link text are now "Web client and HTTPS". Troubleshooting's first web-client question was "are you on HTTPS?", which is no longer the useful question. It now asks about the WebSocket URLs and their scheme, which is the actual common failure — ws:// from an HTTPS page is refused as mixed content. Advice on getting a trusted certificate on an internal network is unchanged and still correct; HTTPS remains the better path.

marcpope committed Jul 27, 2026

Add reverse proxy and TLS page (Caddy, Traefik, nginx); cross-link from install and HTTPS pages

Marc Pope committed Jul 26, 2026

Add: why the web client requires HTTPS, and how to get a cert on a LAN

marcpope committed Jul 25, 2026