Homelab · DevOps · Security · Ongoing
Self-hosted infrastructure
My own production environment across two sites: five Proxmox VE nodes, an OPNsense firewall with HAProxy, backups encrypted at the source and replicated between sites, single sign-on with MFA, and a Telegram bot to run it all. This website is served from it.
- 2sites, each with its own fibre line and rack
- 5Proxmox VE nodes, plus a TrueNAS NAS
- 30+Linux containers, patched automatically every day
- 3-2-1backups, encrypted before they leave each server
Highlights
- No management interface is exposed to the Internet: administration only over WireGuard, with SSH and web logins tied to two YubiKeys.
- Backups encrypted before they leave each server and pulled every night by the other site (3-2-1), with tested restores.
- Single sign-on with Authentik (OpenID Connect) and mandatory MFA for the eight users of the photo library.
- Monitoring, UPS automation and a Telegram bot (ChatOps) to operate both sites from my phone.
- Everything documented as code: a private MkDocs wiki with CI checks (strict build, secret scanning with gitleaks), a decision log and a root-cause entry for every incident.
- This site: Python/Flask behind nginx, SQLite, systemd hardening and its own privacy-friendly analytics with a Telegram bot.
Architecture
Two independent sites, each with a fibre line and a dynamic public IP. The main site runs OPNsense as router and firewall (segmented networks, HAProxy, CrowdSec, WireGuard), three Proxmox VE nodes, a TrueNAS NAS and a UPS; the second runs two Proxmox VE nodes behind Nginx Proxy Manager with equivalent protections. There is no permanent site-to-site VPN: the only link is a point-to-point WireGuard tunnel between the two backup servers. DNS lives in Cloudflare (DNS only) and certificates are issued through DNS-01 challenges, independently of what is exposed.
Security by design
Management interfaces (Proxmox, firewall, NAS, server iLOs) are never published: administration happens only over WireGuard, and SSH and web logins require one of two YubiKeys (FIDO2, WebAuthn or TOTP). Every network is default-deny and may only reach the Internet unless a rule allows a specific service. At the edge: automatic TLS, per-IP connection and request limits, brute-force detection, GeoIP rules and CrowdSec, which blocks attackers at the firewall. Containers patch themselves every day from the distribution's repositories; third-party software is updated by hand after a backup.
Backups and recovery
3-2-1 with Proxmox Backup Server: each node encrypts its backups before sending them (AES-256-GCM), so neither backup server can read what it stores. Every night each site pulls the other's backups through a WireGuard tunnel that only allows the backup service, and a backup deleted at the source is never deleted from the replica. Host configuration, the firewall and the NAS are backed up too; the encryption keys are also kept on paper, and restores are tested.
Monitoring and automation
An Uptime Kuma instance at each site watches the other site's public services, so even a site that goes down entirely gets reported; a small relay I wrote groups the alerts into one message per incident. A Telegram bot answers with backups, temperatures, pending updates, WAN and VPN status and CrowdSec decisions, and can power servers on and off through their iLO (Redfish). During a power cut the UPS (NUT) triggers an orderly shutdown, and the servers come back through iLO or Wake-on-LAN once power is stable. The rack screen at the second site runs Rackdash, a FastAPI and SQLite dashboard I built for its touchscreen.
A contained AI agent
Hermes, a personal assistant on Telegram that delegates coding work to Claude Code, runs in its own VM: its commands execute inside a Docker sandbox, the VM's firewall only lets it reach the Internet, and its GitHub token is limited to a single repository. The design follows the “lethal trifecta” threat model for agents (Willison, 2025): private data, untrusted content and outbound access together are what makes a prompt injection dangerous.
Technologies
- Proxmox VE
- Proxmox Backup Server
- OPNsense
- HAProxy
- WireGuard
- CrowdSec
- Authentik
- TrueNAS
- Docker
- Uptime Kuma
- Linux
- systemd
- Python
- Bash