I run a Proxmox homelab, a Synology NAS, a monitoring stack and a pile of public servers. 32 incidents logged. 88 guides published. Everything on this site is something that actually broke.
Every item below links to a real write-up. Read it before you decide.
Most backups are never tested. They look fine right up until you need one.
A certificate renewal silently stopped every backup on my own fleet at once. Nothing alerted. I set up Proxmox Backup Server, run a real restore in front of you, and show you how to test it yourself.
Read what broke →A dashboard full of green is not monitoring.
I found a notification rule on my own fleet that matched zero events. Fleet wide. It had looked healthy for months. I set up Checkmk and verify a real alert lands in your inbox before I call it done.
Read what broke →IoT junk and cameras sitting on the same flat network as your NAS.
VLANs, firewall zones, and a test that proves the block works. My first block rule silently ate return traffic for connections the trusted network started. That is the kind of thing you only catch by testing it.
Read what broke →One of my hosts took 1,118 SSH brute force attempts from 37 addresses in 8 hours. It shipped with password login on root.
Key only auth, source restricted firewall, fail2ban, kernel hardening, security headers, monitoring, and backups that have been restore tested.
Read what broke →Photos, files, passwords, calendar, chat.
Immich, Seafile, Vaultwarden, Radicale. Self hosted, backed up, and reachable from your phone when you are not at home. I have moved all of it off Google and iCloud and documented the migrations.
Browse the guides →You have Proxmox. Things fall over. Nobody knows why.
I find the actual cause and write it down. Sometimes it is a typo in a download path. Sometimes it is a bridge with a duplicate IP that only the host could use. You get the write-up either way.
Browse the guides →Send an email describing the problem. I will tell you whether I can help and what it costs. That part is free.
Fixed price for scoped work. Hourly for open ended digging. You approve before anything starts.
I write everything down as I go, same as the wiki. You end up with the fix and the document that explains it, not just a machine someone else touched.
Work is remote. No onsite visits.
No Windows desktop support and no general IT helpdesk.
Nothing I have not actually run myself. If you ask about something I have not run, I will say so instead of learning on your money.
Email is the best way in. Describe the problem and what you have already tried.