How I configured Wazuh as a full XDR platform for my Debian 12 LXC fleet and integrated a local Ollama LLM for automated alert triage – all self-hosted, no cloud dependencies.

The split-brain problem is not a Proxmox limitation. Every hypervisor platform – VMware, Hyper-V, Proxmox, XenServer – requires three voters to prevent it. Here is how each one handles it.

A practical guide to weekly Proxmox VE maintenance across multiple sites, including ZFS health monitoring, backup validation, memory optimization, and the scripts I use to keep everything running.

Step-by-Step: Install and Configure Pi-hole with the Proxmox Community Script

This guide covers a full technical setup for Pi-hole on Proxmox using the Community Scripts installer.

It includes:

• creating the Pi-hole LXC
• assigning a static IP
• verifying DNS is working
• configuring your router, ISP modem, or firewall DHCP server to hand out Pi-hole as DNS
• fallback options when your ISP equipment does not allow custom DNS
• post-install Pi-hole configuration
• basic validation and troubleshooting

What this guide assumes

You have:

Part 2: Set Up Nginx Proxy Manager on Proxmox with Cloudflare DNS & pfSense

In Part 2 of this series, we’re setting up Nginx Proxy Manager (NPM) inside Proxmox so we can start exposing our local services with clean HTTPS URLs and valid SSL certificates.

This is where the home lab starts feeling real.

Instead of accessing Home Assistant with something like:

• http://192.168.1.20:8123

…we’ll be able to use:

• https://ha.domain.com

And because we’re using Cloudflare DNS validation, we can issue a wildcard certificate for our domain and keep everything secure and polished.

Why Proxmox Is One of the Best Hypervisors You Can Run in a Home Lab

There’s something incredibly satisfying about owning your infrastructure.

Not renting it.
Not trusting it to some mysterious black box.
Actually owning it.

That’s the spirit behind home labs, and it’s exactly why Proxmox VE has become one of the most powerful hypervisors available to builders, tinkerers, and serious self-hosters.

It’s fast.
It’s powerful.
It’s ridiculously flexible.

About Me

Network engineer with a focus on Azure, Microsoft 365, identity, and modern infrastructure.

I build, break, and document systems so I can rebuild them better.

But this site is more than a bio, it’s a living record of my journey.

Because while my day job lives in the cloud, my real learning often starts at home, in the rack, behind the firewall, inside the lab.

Why This Site Exists

I created this site for a simple reason:

Let’s Connect

If you’ve made it this far, chances are we have something in common.

Maybe you’re building a home lab that started as “just a spare PC” and somehow turned into a rack.

Maybe you’re tuning pfSense rules at midnight trying to figure out why VLAN 30 won’t talk to VLAN 10.

Maybe you’re spinning up another Proxmox node because “this time I’ll document it properly.”

Or maybe you’re deep in Azure networking and Conditional Access policies at 11:47 PM wondering why one test account refuses to cooperate.

Building the Foundation: Where a Real Home Lab Actually Begins

Key principle:

Terminate TLS at a single reverse proxy.
Expose one entry point.
Keep everything else internal.

That’s discipline.

The Real Reason to Do It This Way

This isn’t about running Plex on better hardware.

This is about understanding:

• How packets move
• How identity works
• How segmentation reduces risk
• How public DNS interacts with private services
• How virtualization abstracts hardware

You can buy ecosystems.