Yesterday's entry (Build Journal #002) left mobile access half-finished on purpose: LAN access worked, and cellular/Tailscale access was deliberately deferred. Today was about closing that gap — getting the iPhone to reach Open WebUI on Node A from anywhere, Wi-Fi off entirely. Full technical detail lives in the Field Guide, Part 2 — this entry is the narrative version.
Node A already had Tailscale installed and had shown up in earlier notes with address 100.80.190.11. That looked like a solid starting point for today's test.
It wasn't. Node A's Tailscale client turned out to be signed into a personal tailnet — not the shared AI Lab tailnet that Node B and the iPhone were already members of. Two devices on different tailnets simply can't see each other, no matter how correctly everything else is set up. This wasn't a bug so much as a mix-up: it's easy to sign into the wrong one when more than one tailnet is available at login.
Node A got logged out of Tailscale and back in, this time explicitly selecting the shared AI Lab tailnet instead of the personal one:
Signing in wasn't quite the finish line, either — the join request still needed to be approved by the tailnet's admin before Node A actually showed up for the other devices. Deliberate access control, not a hiccup.
Once approved, tailscale status showed all three devices together for the first time: Node A at a new address, 100.115.162.13; Node B at 100.81.51.91; and the iPhone, showing up as iphone171, at 100.110.16.81.
Somewhere in the middle of all this, a smaller but genuinely useful improvement landed: a pair of one-click batch scripts to start and stop the whole local stack — checking whether Ollama and Open WebUI are already running, starting Ollama if not, warming up the default model, then launching Open WebUI. It doesn't survive a reboot on its own, but it turns "reconstruct the launch command from memory" into "double-click a script," which was most of the actual daily friction.
Along the way, the Open WebUI Desktop app's own window occasionally threw a bare Failed to fetch error while the server underneath it was completely healthy — confirmed with curl against both 127.0.0.1:8080 and localhost:8080. The Desktop app's shell turned out to be less trustworthy than just using a browser, which is also exactly what the iPhone has to do anyway.
With Wi-Fi switched off on the iPhone — cellular data only — Safari loaded:
Open WebUI came up, login succeeded, qwen3:8b got selected, and a test question — "Who invented AI?" — got a real answer back. No home Wi-Fi involved anywhere in that path.
A device can look perfectly healthy on Tailscale — connected, online, reporting an IP — and still be unreachable from another device, simply because the two aren't on the same tailnet. That's a different failure mode from anything in yesterday's LAN troubleshooting, and worth remembering as its own category of "everything looks fine, but it isn't" problem.