Homelab

This incident happened on a Dell OptiPlex Micro running Proxmox VE. The machine is my always-on Node02 host and carries critical home infrastructure: Home Assistant AdGuard Home Unbound DNS MQTT Zigbee2MQTT Other LAN support services At first, this looked like a disaster spread across half the house. That host is the backbone for the living room stack. It runs Home Assistant and several supporting services, so when its network dies, the failure can look like everything is broken at once. That is what makes these incidents so sneaky - the real problem is hidden behind a long chain of symptoms. ...

There are two kinds of Uptime Kuma migrations: The one that works. The one where people export JSON, assume life is good, then discover half their setup is missing. This guide is for the first one. The safest and least error-prone way to migrate Uptime Kuma is: Move the ENTIRE data directory. Not screenshots. Not copy-paste. Not “I exported a backup JSON so I should be fine.” The actual source of truth is the database and app data. ...

Stop treating your Proxmox configuration like it’s disposable. Start treating it like code. GitHub: ruhanirabin/pve-config-git The Problem: Configuration Drift Is a Silent Killer I’ve been running Proxmox for years. Multiple nodes, dozens of VMs, complex network configs, storage pools, custom scripts. And like many of you, I made changes directly on the host. A quick edit to /etc/network/interfaces here, a storage tweak there, a firewall rule adjustment to get something working. ...

Let’s get one thing out of the way: Proxmox upgrades are not fragile. People are. Most guides assume: nothing goes wrong you don’t interrupt anything you don’t get stuck in a pager you don’t panic halfway That’s not reality. This guide is based on an actual upgrade — including: interrupted upgrade broken package state lock issues recovery If you follow this, you’ll finish the upgrade even if things go sideways. ...