Welcome to my tiny corner of the internet
I
write
about ml, infra, devops, photogrpahy and anything else that comes to mind
2025-01-16 | #100daysofhomelab #buildlog #homelab #proxmox
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?”
2025-01-15 | #100daysofhomelab #buildlog #homelab #proxmox
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.
2025-01-13 | #100daysofhomelab #buildlog #devops #homelab #proxmox
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?
Think of a reverse proxy like a bartender - you ask for a drink, and they handle getting it from the right place. More technically, it’s a server that sits between clients and your web services, forwarding requests.
2025-01-12 | #100daysofhomelab #homelab #proxmox
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 DHCP and network connectivity (also great!), but then things got interesting. Once the network was up and the Proxmox nodes could talk to each other, the other VMs would fail to start with cryptic errors like:
2025-01-11 | #100daysofhomelab #homelab
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.