Proxmox VE
Virtualization for application hosting, game services, the web proxy, and monitoring.
Inside the workshop / Software
The platforms and services running on the lab, what they do for me, and how I work to keep them dependable.
01 / The foundation
Virtual machines separate the major jobs, containers package applications, and the website shares the public side of the workshop.
Virtualization for application hosting, game services, the web proxy, and monitoring.
Containerized applications with persistent data and repeatable service definitions.
Routes approved web traffic to the appropriate service and manages HTTPS certificates.
The static website you're viewing, with source changes tracked in a private Git repository.
02 / Self-hosted services
A selection of the platforms and services I use for files, photos, gaming, and hands-on learning.
Personal files and collaboration.
A self-hosted home for photos and videos.
A growing collection of self-hosted games, managed through CubeCoders AMP.
AMP 3 evaluation & integrationsDashboards, metrics, and service checks.
Loki brings logs together for troubleshooting.
03 / AdGuard Home
DNS translates a name a device asks for into an address it can use. AdGuard Home checks those requests against filtering rules, helping block advertising and tracking domains before the device connects to them. It can also apply domain-based security and content policies.
See the two dedicated Raspberry Pi devices supporting DNS.
Both can answer DNS requests. The network supplies both resolver addresses to clients; the second is not a sleeping standby. Device behavior determines which resolver is used and how quickly it retries another. Neither DNS service needs the main Proxmox server to be running.
Redundancy, maintenance safeguards, monitoring, and recovery work together.
Two wired Raspberry Pis keep DNS separate from the main virtualization host. A server reboot does not inherently require taking DNS down.
Configuration synchronization keeps shared rules aligned. If synchronization stops, each resolver keeps serving its existing configuration.
Scheduled system backups check that the other resolver can answer first. A shared lock prevents the two backup jobs from pausing DNS at the same time, and recovery hooks restart and check the service afterward.
Checks watch DNS answers, filtering, service health, and backup results. Off-device configuration and system backups provide a recovery path beyond simply replacing a failed Pi.
In controlled tests, each surviving resolver answered normal requests and blocked a test domain while its peer was down. That demonstrates independent resolver operation; it does not guarantee instant failover on every client.
UPS-backed power helps bridge short power interruptions, but shared power, the gateway, and network connectivity remain common dependencies. Two DNS servers do not protect against every outage.
DNS filtering applies to devices using these resolvers. It does not remove every advertisement, inspect downloaded files, or replace endpoint protection. Ads served from the same domains as the content, including many video ads, can remain. Devices using their own DNS or a VPN may bypass the local filtering.
Whole-system shutdown and recovery coordination remains part of the ongoing build.
04 / Protection & recovery
Snapshots, backup copies, and application database backups cover different parts of recovery. Monitoring helps identify a failed job; restore tests check whether the saved data can actually be used.
I’ve restored the application server from backup into a separate test VM and verified the recovery. RAID, snapshots, and backups each do a different job; the restore test checks that the pieces can work together.