Build Journal #003 put Tailscale in place as the lab's remote-access layer — a private mesh network, reachable only to devices joined to the same tailnet. This entry covers the lab's move away from that approach, toward a real public domain fronted by a Cloudflare Tunnel.
Tailscale worked, but it meant every device that wanted in — a phone, a laptop, a guest — had to install the Tailscale client and join the tailnet first. A Cloudflare Tunnel trades that for a real domain name anyone can type into a browser, no client install required, at the cost of exposing an actual public hostname instead of a private mesh address.
The domain skyapt.org was registered and its nameservers pointed at Cloudflare. A tunnel was provisioned on Lab PC 2 to expose the local Open WebUI instance (localhost:8080) at https://lab.skyapt.org — routing traffic in from the public internet to a machine that was never given a public IP of its own.
This phase was deliberately scoped to the tunnel only. Cloudflare Access — the identity/login gate meant to sit in front of the URL — was left for a separate, later task on purpose, so that if something broke, it would be clear which layer broke it.
https://lab.skyapt.org resolves and loads. A quick-launch button ("CloudF") was added to the lab's menu page pointing at it, alongside the existing Tailscale-based "Gwen" link.
The setup task called for a full report back — exact cloudflared version, tunnel UUID, the config file as written, a same-machine load test, an off-network test from a phone on cellular data with Wi-Fi off, and a reboot test to confirm the tunnel survives unattended. That report hasn't landed yet, so several of those steps are unverified as written up here.
Configure Cloudflare Access in front of the tunnel, get the full verification report on record, and decide when — or whether — Tailscale gets formally retired rather than just set aside.