Acting as a DNS-level ad blocker, Pi-hole intercepts and blocks requests to known ad and tracking domains before they ever reach your devices. It’s fast, private, and works network wide.

Because Pi-Hole is intercepting DNS requests, we need to be careful about its availability, if your DNS goes down, your internet goes down. That’s why, in my VLAN segmented home network, I decided to go with Redundant/highly available Pi-hole deployment for resiliency.

Migrating OMV bare metal to a Proxmox VM

Recently, I decided to move my OpenMediaVault (OMV) setup into a VM on my Proxmox server.

Previously, OMV was running bare-metal on an Intel NUC for years without any issues. It’s been rock solid. But I started thinking about rearranging things, possibly moving Home Assistant from a VM back to bare metal NUC, and that got me curious about trying OMV in a VM instead.

I recently faced a critical situation with a locally hosted Nexus 3 repository running in a Docker container, using the embedded OrientDB. The admin password had been lost. To make things worse, the disk filled up, taking the entire repository offline. We needed access restored fast.

I tried prompting an LLM for help, but most answers were generic or overly drastic, some even suggested reinstalling Nexus, which sounded overkill.

My first instinct was to try resetting the password by editing a config file or injecting a default password hash. But this approach quickly failed as I learned Nexus 3 stores all its configuration data inside the embedded OrientDB, so there’s no flat file on the host that you can edit, good for security.