Building the Main Proxmox Node

Paper to Reality

The idea of building my own homelab has always appealed to me as a tangible way to learn and explore the systems that power modern digital infrastructure. As someone fascinated by networking, security, virtualization, and storage solutions, I decided to stop consuming tutorials and start building something real. My journey began with a single node, a modest yet more than capable machine built from the remains of a retired gaming PC. The system centers around an Intel i7-2700K processor paired with 32GB of DDR4 RAM from G.SKILL, mounted on an MSI Gaming motherboard. Storage is split across a 1TB NVMe SSD for the OS, two 1TB mirrored hard drives for resilience, and a 250GB SSD for overflow or testing environments. It’s all housed in a 3U ATX rackmount case (used from Facebook Marketplace) powered by a Corsair RM850 PSU and cooled by a Thermalright low-profile CPU air cooler, 120mm, 80mm and two 60mm fans to improve airflow in the confined chassis.

While the part list looks neat on paper, you can always count on a few surprises when piecing a system together. The original AIO cooler wouldn’t fit in the 3U case, so I had to pivot to a more compact solution. The front panel wiring (power, reset, and USB) was fried, requiring creative workarounds (using my old front panel connectors for the meantime). My GPU's PCIe cable wouldn’t clear the chassis, so I made a careful modification to the case itself to allow the cable through. I reused the hard drive bay from my previous case and temporarily taped it inside which I know is not ideal, but serviceable for the time being until I upgrade my storage. Only one standard 120mm fan fit along side a 80mm as intake at the front, and two 60mm as exhaust near the I/O panel. BIOS settings also had to be reset from previous setup. The hiccups were minor and expected, nothing a bit of tinkering couldn’t resolve.

A Node with a Purpose

This node is the foundation of my future homelab. Running Proxmox VE, it’s more than just a bare-metal hypervisor. It’s a hands-on platform for exploring cybersecurity concepts, practicing ethical hacking techniques, and experimenting with ZFS storage pools and self-hosted services. I intend to cluster it with other lightweight nodes (a spare laptop, Raspberry Pis, etc.) over time, gradually building a distributed lab environment that mirrors small-scale enterprise networks. Right now, it’s connected directly to my ISP-provided modem/router, but that’s temporary. I’m planning to introduce a dedicated pfSense mini PC and properly structured VLANs for greater control and segmentation.

Even before the full network stack is in place, the node has already been active. I began by hardening and configuring Proxmox itself, such as disabling the enterprise repository, enabling the no-subscription and test repos, updating the system, and removing the infamous nag screen. I experimented with OPNsense using a secondary PCIe NIC to visualize basic firewall behavior, but ultimately paused that effort in anticipation of transitioning to purpose-built firewall hardware. I created a Pi-hole container to explore DNS-based ad-blocking across my LAN, which worked beautifully. For a brief period I also spun up an Ubuntu Server VM to host a temporary game server, primarily to test NAT rules and port forwarding from my ISP's router.

Why I Chose to Build

Why build when you can buy? I could have picked up a Synology NAS or a used enterprise server off eBay. It would’ve been easier in some ways, but thankfully, I didn’t. With their latest 2025 Plus models, Synology has doubled down on locking users into their own overpriced hard drives, limiting full functionality if you dare to use trusted alternatives like Seagate IronWolf or WD Red. It’s a move that feels like a slap in the face to longtime users: paying more, getting less, and losing the freedom to choose your own hardware. Seeing all that unfold reaffirmed that building my own system was absolutely the right call. Not only do I get more control over my hardware and software, but I’ve also gained hands-on experience and sharpened my skills. Troubleshooting boot issues, managing airflow in a tight chassis, resetting BIOS quirks, and configuring Proxmox from scratch, these aren’t just technical chores but instead they’re formative experiences. They teach you how things work beneath the surface, and how to fix them when they don’t.

If you’re just getting started with your own homelab like me, here’s what I’d say: don’t wait for perfection. Don’t hold off until you’ve found the “right” server case or bought a full rack. Just start. Use what you have. Adapt and evolve as you go. Use tape if you must, cut a case panel if it gets the job done!

Looking ahead, my next priority is building out the network infrastructure around this node. That includes setting up a dedicated pfSense router, installing a proper access point, and configuring my managed switch to support VLANs and segmentation. These steps will lay the foundation for a more secure and scalable environment. Hardware-wise, I may eventually upgrade to a quieter, more spacious 4U case, but that’s a consideration for the future, first I a proper rack to house everything. For now, this node does exactly what I need it to do: serve as a functional, flexible core for a lab that’s designed to grow with me.