This is a continuation of the previous post here. Left off with the Traefik setup in k3s not picking up the certificate, and if you read that post one thing that immediately comes to mind is “Did you check the right TLS secret was being used?” Since I’m working

After the whole VM boot ordering not working the way i wanted, I finally decided to uncluster the nodes. (Also very likely a skill issue). To be fair having the nodes in a cluster made it easier for centralized management and easy VM migrations. From LXC to K3s This is

After running Proxmox for about 2 months, I realized I hadn’t tried out LXC containers yet. What better way to start than setting up a reverse proxy? What’s a Reverse Proxy? Think of a reverse proxy like a bartender - you ask for a drink, and they handle

It turns out that Proxmox’s quorum requirements are not as “simple” as I thought. The initial solution of setting quorum expectations to 1 worked… sort of. Here’s what happened: When a node booted up (remember it can’t initially “see” the other node), OPNsense would start (great!), provide

I got a new Netgear managed switch yesterday and so today was all about network segmentation and fighting with OPNsense. Also learned some interesting bits about Proxmox clustering that I didn’t expect to deal with. First up, got OPNsense reinstalled on the N100 box - fresh start for the