#self-hosting
My NAS was doing a server's job, so I bought it a serverMy ZimaBoard was holding my photos, my documents, my monitoring and my AI agents in 7.5 GiB. The agents were the reason the fix had to be a second machine.- The 03:37 alert that was never sentMy monitoring pinned a 3am outage on Cloudflare within seconds, and my notes said my phone was paged at 03:37. Nothing had been sent, ever.
- Every site is monitored twiceI set up uptime monitoring for my sites and nearly made every check meaningless. They all sit behind Cloudflare, and a plain HTTP check there proves that Cloudflare answered, not that my app is alive.
- Homepage kept showing My First GroupI replaced the example config on my Homepage dashboard and the page source still showed the examples. It survived a full container recreate, because it was never my config to begin with.
- The Tailscale login that could never finishI installed Tailscale in a container, approved the login link, watched the node appear in my tailnet, and then watched it sit offline. It had sixty seconds to log in, and a browser login takes longer than that.
- The ZimaOS update the updater never offeredMy ZimaBoard had been running an eight-month-old alpha since January, and the built-in updater said there was nothing newer. There was. Getting to it meant learning what 100% on the root filesystem actually means on this box.
- When RAID1 saved the data but not the stateA homelab migration filled the system disk and the storage layer lost track of a perfectly healthy array. Here is why I wiped and rebuilt from backup instead of recovering in place.