If you only access the Web UI from the host PC, plain HTTP is fine. The moment you access it over LAN (let alone WAN), you want HTTPS so passwords and session cookies aren't in the clear. AASM v0.8.3 ships a one-click Install Certificates button that generates a self-signed root CA + a server cert for the Web UI - and optionally installs the root into Windows' trusted store so your browser stops warning.
Prerequisites:
Server tab (any server) → Maintenance sub-tab → Maintenance & Management. Scroll to the Quick Actions & Management card → SYSTEM OPERATIONS section.
The cyan Install Certificates button (next to Open Firewall Ports) generates the cert chain. Windows will prompt for elevation - approve it.
AASM creates a self-signed root CA + a server certificate bound to the host PC's common names (e.g. localhost, the LAN IP, the machine's hostname). The certs are stored next to AASM's data directory.
Open the App Settings dialog → Web UI section. If a Use HTTPS toggle appears (it should now that the cert exists), enable it. The Web UI restarts and now listens on the same port over TLS.
Update the URL you use to reach the Web UI:
https://192.168.1.42:3000
First visit, the browser will show a "Not secure" warning because the root CA isn't trusted yet. Step 5 fixes that.
On the AASM host PC, the root CA was already installed during step 2 (Windows trusted-root store). On other devices (your laptop, phone, etc.) you need to install it manually:
Self-signed certs are fine for LAN. For real WAN exposure, get a Let's Encrypt cert via your domain name and point AASM at it (advanced; see the Discord for help).
The Web UI is now served over HTTPS with a self-signed cert. Trust the root on every device you connect from to silence the browser warning.