Skip to content

v0.1.135 — Remote access: per-server TLS certificates (M8/8b)

Choose a tag to compare

@NebulaSleuth NebulaSleuth released this 04 Jul 23:55
· 73 commits to main since this release

Ships the backend half of automatic per-server TLS for remote access. Dormant by default — no behavior change unless you enable Remote Access in /setup.

What's included

  • Automatic per-server certificate for <serverId>.s.whatsontv.net via ACME (Let's Encrypt) using DNS-01. The backend generates and keeps its own private key — the cloud only publishes the DNS challenge it's asked to.
  • HTTPS on the remote listener — once a cert is obtained, the internet-facing listener terminates TLS itself (valid, publicly-trusted cert that every device accepts).
  • Automatic renewal (twice-daily check, renews under 30 days).
  • /setup → Remote Access now shows certificate status (obtaining… / valid · N days left).

Fleet safety: all of this activates only when Remote Access is enabled (which requires an admin password). Installs with remote access off behave exactly as v0.1.134.

Note: a valid cert + DNS makes the server addressable; opening the port to the internet (UPnP / port-forward) is the next milestone (8c). The Windows updater auto-installs within minutes.