Apache HTTP/2 emergency, Docker backups that prove themselves, and a thirty-five dollar drive test bench

Homelab Highlights for 2026-11-13: self-hosting and homelab notes worth knowing.

[Audio embed placeholder]

The Lead: Critical vulnerability in Apache with HTTP2 module enabled

A critical unauthenticated remote code execution vulnerability (CVE-2026-119618, CVSS 9.8) in Apache’s mod_http2 affects versions 2.4.55 through 2.4.70. A proof of concept is already public. The fix is in Apache 2.4.71. The module may be enabled by default on some distros, including NextcloudPi on Debian 13.

Why it matters: If you run an internet-facing Apache with HTTP/2 enabled, this is urgent. The PoC is public, so exploitation is likely. Patch to 2.4.71 or disable mod_http2 immediately. If Apache sits behind a reverse proxy that handles HTTP/2, the backend may not be exposed, but verify rather than assume.

Source: r/NextCloud

News Roundup

Pi-hole vs AdGuard Home: Which One Should You Self-Host?

A month-long comparison of Pi-hole and AdGuard Home on the same network. The deciding difference: AdGuard Home ships encrypted DNS (DoH, DoT, DNSCrypt) natively, while Pi-hole needs a sidecar. AdGuard Home also offers per-device SafeSearch and scheduled blocking out of the box. Pi-hole counters with a larger community and deeper blocklist ecosystem. Neither blocks in-app ads on YouTube or Facebook.

Why it matters: Choosing between these two DNS sinkholes is a common homelab decision. This comparison gives a practical, experience-based verdict: AdGuard Home for encrypted DNS and per-device control, Pi-hole for community and blocklist depth.

Source: dev.to

fail2ban kept “banning” IPs that kept hammering my Docker ports — the bans were landing in the wrong iptables chain

On a Docker host, fail2ban’s default action drops rules into the INPUT chain, but packets to published ports are processed by Docker’s DOCKER-USER chain first. The fix: point the jail’s action at DOCKER-USER. Verify by listing rules in that chain and checking the packet counter.

Why it matters: A common and frustrating misconfiguration that makes fail2ban bans ineffective on Docker hosts. The one-token fix is easy to apply, and the verification step prevents silent failures.

Source: r/selfhosted

Gitea Actions on k3s: Self-Hosted CI Without GitHub

A guide to running Gitea Actions on k3s as a self-hosted CI replacement for GitHub Actions. Gitea reads the same YAML workflow format, and most workflows migrate with minimal changes. The author notes limitations: some workflow syntax is only partly supported, and Docker-in-Docker for image builds requires privileged containers or a socket mount.

Why it matters: For homelabbers burning through GitHub’s 2,000 free CI minutes, Gitea Actions on your own hardware is a practical alternative. The tradeoffs are clearly laid out, including the security implications of Docker-in-Docker.

Source: dev.to

A simple way to keep your self-hosted website accessible during outages

A workaround for self-hosted site downtime: save static snapshots of public pages and serve them from Cloudflare Workers when the origin is unavailable. No second server needed, works on the free tier. Commenters suggest tagging fallback responses with a custom header and skipping pages with forms or CSRF tokens.

Why it matters: A clever, low-cost way to improve uptime for self-hosted sites without adding infrastructure. The commenter tips make it more practical for real-world use.

Source: r/selfhosted

Tool & Software Highlight: DockNest Backs Up Your Docker Apps and Tests Whether They Can Be Restored

DockNest is a self-hosted Docker backup and recovery tool that automates backups, tests restores, and helps migrate applications between servers. It supports Docker Compose projects and static nginx sites, with encrypted backups to SFTP or S3-compatible storage. The restore testing feature restores into an isolated environment and checks whether the application starts successfully.

Why it matters: The restore testing is the standout feature: it verifies backups continuously, not just during a disaster. For anyone who has discovered a broken backup at the worst possible time, this is a significant improvement.

Source: GitHub

Community Highlight: Poor person’s HDD burn-in station

A budget HDD burn-in station built from a $35 used PC, a 4-channel LSI HBA, Linux Mint, and the Spearfoot disk-burnin-and-testing script. The rig was running eight 8TB drives for over 60 hours. The thread explains why burn-in matters: drive failures follow a bathtub curve, and used drives may have been handled carelessly.

Why it matters: A practical, low-cost approach to testing used drives before trusting them with data. The thread includes useful tips like using tmux to manage sessions and ensuring adequate airflow.

Source: r/DataHoarder

Sources

Transcript

Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.

Host A: Let’s start with the one that needs attention today. There’s a critical vulnerability in Apache HTTP Server when the HTTP/2 module is enabled, and it’s being discussed hard on the Nextcloud subreddit right now. The CVE number is 2026-119618, it’s rated 9.8, and it’s an unauthenticated remote code execution in mod_http2. Versions 2.4.55 through 2.4.70 are affected, and the fix is in 2.4.71.

Host B: And the part that makes this urgent rather than just annoying: a proof of concept is already public. So this isn’t a theoretical window. If someone is running an internet-facing Apache with mod_http2 loaded, the clock started yesterday. The original poster on r/NextCloud found the module was active on a NextcloudPi install on Debian 13, which is exactly the kind of default nobody double-checks.

Host A: Right, and that’s the trap here. Plenty of people run Apache purely as a reverse proxy in front of Nextcloud and never consciously chose HTTP/2. The module ships enabled in a lot of distro configs. The practical checks are simple though: confirm the Apache version is at 2.4.71 or later, and if the patch isn’t available yet, disable the http2 module and reload. One commenter posted exactly that workflow, disable the module, run a config test, reload Apache.

Host B: There’s also a useful nuance in the thread about reverse proxy stacks. One commenter pointed out that if Nextcloud sits behind Nginx Proxy Manager, plain HTTP/1.1 is what reaches the backend, so HTTP/2 only exists between the browser and the proxy. Same question came up for Traefik in front of a Docker Nextcloud. That logic seems sound, but the thread’s advice was to verify rather than assume, and honestly, checking what protocol actually hits the backend is the only way to know for a given setup.

Host B: Alright, moving on to the rest of the news. First, a comparison piece on DEV Community from someone who ran Pi-hole and AdGuard Home on the same network for a month, switched between them, and switched back. The verdict: neither is a bad choice, but the deciding difference is encrypted DNS. AdGuard Home ships DoH, DoT and DNSCrypt natively in both directions from the first-run wizard, while Pi-hole speaks plain DNS on port 53 and needs a sidecar like unbound for encrypted upstreams. The other gap is per-device control: AdGuard Home does per-client SafeSearch enforcement and scheduled blocking out of the box, which the author found decisive in a house with a kids’ tablet. Pi-hole counters with a bigger community and a deeper blocklist ecosystem. It’s worth noting the limitation either way: no DNS filter blocks in-app ads on YouTube or Facebook, because those come from the same domains as the content.

Host A: Next, a war story from r/selfhosted that’s worth a quick mention for anyone running fail2ban on a Docker host. Someone spent days wondering why banned IPs kept hammering a Docker-published WordPress login. The bans were real, fail2ban reported them, but the traffic never stopped, because fail2ban’s default action drops rules into the INPUT chain, and packets to published ports get processed by Docker’s DOCKER-USER chain first. The fix was pointing the jail’s action at DOCKER-USER instead. The key takeaway from the commenter is to verify the ban by listing the rules in that chain and actually see the address there, and check the packet counter, because a rule with zero hits looks exactly like a working ban.

Host B: Switching gears to CI, there’s a write-up on running Gitea Actions on k3s as a self-hosted GitHub Actions replacement. The reasoning behind it: GitHub’s free tier gives 2,000 minutes a month for private repos, and a homelab infrastructure repo running Terraform plan, Ansible lint and container builds burns through that in about a week. Gitea Actions reads the same YAML workflow format, the act_runner binary polls for jobs, and most workflows migrate by moving the file into a Gitea workflows directory. The author also notes some limitations: some workflow syntax is only partly supported, and Docker-in-Docker for image builds means privileged containers or a socket mount, which is a real security tradeoff on a home cluster.

Host A: And one more thing from r/selfhosted: a workaround for one of the challenges of self-hosting a public site, which is visitors getting an error page when the server is down. The poster saves static snapshots of public pages and serves them from Cloudflare Workers whenever the origin is unavailable, no second server needed, and it works on the free tier. A commenter suggested tagging fallback responses with a custom header so logs show when the snapshot is serving, and skipping pages with forms or CSRF tokens, since a stale token fails quietly.

Host A: For the tool highlight, this one hits close to home for a lot of us: DockNest, a self-hosted Docker backup and recovery tool, AGPL licensed, on GitHub. The idea is backups you can actually trust, and that second half is what makes it interesting.

Host B: Because the classic homelab failure isn’t the backup, it’s the restore. Volumes and compose files are safely stored somewhere, and then the one time a restore is actually needed, the app refuses to start. DockNest connects to Linux servers over SSH, discovers Docker Compose projects and static nginx sites automatically, and backs up container images, volumes, bind mounts, and databases including PostgreSQL, MariaDB and Redis. Backups are encrypted with AES-256-GCM and can land on SFTP or S3-compatible storage like MinIO or Cloudflare R2, with per-app schedules and retention. It also supports migrating applications between servers, with a visual interface and a seven-day rollback window.

Host A: The restore testing is the feature worth dwelling on. DockNest can restore an application into an isolated environment and check whether it actually starts, and those restore tests can be scheduled, so the verification happens continuously instead of during a disaster. That’s the difference between having backups and having confidence in them. Notifications can be sent through ntfy, Gotify, or Discord, so you know when something goes wrong.

Host B: This week’s community highlight is from r/DataHoarder, and it’s called, with some self-awareness, the poor person’s HDD burn-in station. The poster buys used hard drives because that’s the budget, and being the nervous sort, wanted to test them before trusting data to them.

Host A: The build is wonderfully scrappy. A used PC for thirty-five US dollars, a 4-channel LSI PCIe HBA that had been sitting in a drawer for at least five years, Linux Mint on top, and the Spearfoot disk-burnin-and-testing script from GitHub doing the actual work. At the time of posting, the rig had been churning through eight 8TB drives for over sixty hours. The poster’s own words: it’s a kluge, but it’s humming along, and it buys some perhaps unjustified confidence. A commenter suggested using tmux to manage the sessions, so you don’t have to worry about accidentally closing a terminal window.

Host B: The thread does a good job explaining why burn-in is a thing. One commenter explained it as a stress test that writes to every block to force early weaknesses to surface, because drive failures follow a bathtub curve: a cluster of early failures, a long stable stretch, then a spike at end of life. Used datacenter drives, and these are SAS drives, have already survived their early-failure window, but there’s no way to know how they were handled before they arrived, which is exactly what the burn-in is for. Another commenter pointed out the importance of airflow over the drives, which the poster addressed with a desk fan.

Host A: That’s Homelab Highlights for Friday. Until next time, happy hosting!