Most homelab buying guides start with the case or the drives, but the CPU and motherboard decide almost everything downstream of them. PCIe lane count sets how many cards you can run at once. ECC support decides whether a bit flip in RAM silently corrupts your ZFS pool or gets caught and corrected. IOMMU group layout decides whether GPU or HBA passthrough to a VM is a ten-minute config change or a wall you can’t get past no matter what you try. None of that shows up on a spec sheet the way clock speed and core count do, which is exactly why it gets skipped over until someone hits it the hard way. ...

Proxmox ships with a real, iptables-backed firewall built into the platform, and most homelabs never turn it on. It’s not enabled by default at any level, so unless you’ve gone looking for it in the UI, there’s a good chance your VMs and containers are sitting behind nothing but whatever VLAN segmentation you’ve set up, if any. That’s often fine. It stops being fine the moment you’re running something internet-facing, or you want one VM to be reachable only from your management network and nowhere else, or a compromised guest shouldn’t be able to freely talk to everything else on its VLAN just because they share a broadcast domain. This is what the built-in firewall is actually for, and it’s worth understanding the shape of it before you flip it on. ...

Ditching Google Drive or Dropbox is one of the most common reasons people start self-hosting in the first place, and it’s also one of the easiest to get wrong by picking the wrong tool for the job. Nextcloud and Syncthing both get your files off someone else’s server, but they’re built on completely different models, and picking the one that doesn’t match how you actually work is how people end up frustrated and quietly back on Dropbox six months later. Here’s what each one actually is, where they overlap, and how to pick. ...

Most data hoarders don’t start with a matched set of drives. They start with whatever was on sale, whatever got shucked (see the hard drive shucking guide if that’s new to you), and whatever got inherited from an old build, added one or two at a time over a couple of years. The RAID redundancy guide on this site, and ZFS along with it, both assume something that mismatched-drive hoarders usually don’t have: drives that are the same size, ideally bought in a batch, treated as one block device. Buy a 4TB, then an 8TB eighteen months later, then a random 6TB that came out of a NAS somebody was tossing, and a real RAID array either wastes most of the bigger drives down to the smallest one’s capacity, or just won’t build at all. ...

Every homelab guide eventually tells you to “get a managed switch,” usually without saying why, or which one, or what happens if you buy the wrong one. This site has already covered when 10GbE is worth the upgrade and how to configure VLANs, bridges, and bonding once you’re inside Proxmox. This article is the piece that comes before both of those: picking the actual switch hardware sitting between your gear, the decision that either makes everything downstream easy or makes you fight your network for the next three years. ...

The Proxmox-vs-ESXi comparison on this site already covers why so many homelabbers are moving off VMware since the Broadcom licensing changes gutted the free ESXi tier. This one skips the “should I switch” question and gets into the part that actually trips people up: what breaks when you move a real VM from ESXi to Proxmox, and how to get ahead of it instead of debugging a guest that won’t boot at 11pm. ...

Most people’s first smart home purchase is a cloud-connected bulb or plug, and most people’s first regret is realizing that bulb stops working the moment the manufacturer’s cloud service has a bad day, changes its app, or shuts down entirely. Home Assistant exists to fix that: a self-hosted automation hub that talks to your devices locally whenever possible, keeps the logic on hardware you control, and doesn’t care if the internet is up. For a homelab operator who already runs Proxmox and a stack of Docker containers, it’s one of the more satisfying things you can add, because it’s the one self-hosted service that actually reaches out and touches physical stuff in your house. ...

Once a media library and a media server are both sorted out, the next question most data hoarders hit is how everything actually gets into the library in the first place. Doing it by hand, manually searching, downloading, renaming, and moving files into the folder structure your media server expects, works fine at a few dozen items. It falls apart well before a few hundred. The *arr stack (Sonarr, Radarr, Prowlarr, and a handful of siblings) is the standard homelab answer: a set of small, single-purpose applications that watch for content you want, find it, grab it, rename it, and drop it into your library automatically. ...

A UPS without a way to talk to your hosts is just an expensive surge protector with a battery in it. It’ll keep the lights on for a few minutes, but the moment that battery runs out, every VM and container you’re running goes down exactly as hard as it would have without a UPS at all, just a little later. The part that actually protects you, a UPS that tells your hosts “power’s out, shut down now while you still can,” is a separate piece of software most people never get around to setting up. Here’s how to size the UPS itself, and how to wire up Network UPS Tools (NUT) so an outage ends in a clean shutdown instead of a dirty one. ...

Every homelab operator hits the same wall eventually: you need a fifth Ubuntu VM for some new service, and the thought of walking through another OS installer, setting the hostname, adding your SSH key, and running updates makes you want to just leave the last one running forever instead. Cloud-init templates fix this. Build the template once, and every new VM after that is a clone plus a few lines of config, done in under a minute instead of fifteen. This is the same workflow cloud providers use to spin up instances on demand, and Proxmox supports it natively, no extra tooling required to get the basics working. ...