Write-ups from a rack in a spare room: Proxmox, Kubernetes, self-hosted game servers, and the failure modes that aren't in anyone's documentation. Written down while the details are fresh, mostly so the next person doesn't lose the same week I did.
| pve1 | A | 10.10.0.10 | Proxmox host. Everything else is its problem. |
| pihole1 | A | 10.10.0.4 | Ad blocking, and one memorable outage of its own making. |
| duneawakening | A | 10.10.0.69 | Alpine guest, k3s, 30 game maps, far too much RAM. |
| @ | A | CloudFront | This page. S3 behind it. Static, cheap, boring. |
Write-ups
The battlegroup reported healthy, the gateway registered with Funcom, and the heartbeat succeeded every thirty seconds — while a wedged Steam manifest quietly kept the server eleven days behind. Plus four other undocumented failures you hit running the appliance on Proxmox instead of Hyper-V.
I run a small homelab and write down the parts that took longest to figure out. Most of what's here started as an error message with no useful search results.
Corrections are welcome and credited. If something here saved you an evening, that's the whole point — pass it along.