Hero Image
Homepage kept showing My First Group

The Homepage dashboard on my ZimaBoard had never been set up. It was still running the example config it ships with: three groups called “My First Group”, “My Second Group” and “My Third Group”, each with one placeholder service pointed at http://localhost/. I wrote five YAML files to replace the examples, got them onto the board, and checked the page source. It still said “My First Group”.

Saturday, September 19, 2026 | 3 minutes Read
Hero Image
One character in /etc/shadow locked me out

I built a small container to run coding agents on my ZimaBoard, reachable over SSH, key-only, no root login. It is the same box from the Tailscale login that could never finish. The first login was refused: Permission denied (publickey) Narrowing it down An ssh -v trace showed my machine offering the right key and the server rejecting it, so the fault was inside the container. The sshd config was fine: sshd -T confirmed PasswordAuthentication no, PermitRootLogin no and AllowUsers dev, all as intended.

Saturday, September 19, 2026 | 2 minutes Read
Hero Image
The Tailscale login that could never finish

zimaboard2 appeared in my tailnet, I approved it, and then it sat there: offline, last seen 19m ago. I wanted the agent box on the ZimaBoard I rebuilt in January reachable from a laptop away from home. Tailscale rather than a forwarded port: it only carries traffic addressed to my own devices, so the rest of the LAN and every machine without it installed are untouched. No exit node, no subnet routing. I installed it on the board as a compose app with host networking, so the tailnet address reaches every port the board already publishes.

Saturday, September 19, 2026 | 3 minutes Read