Fast cache hits
Varnish handles cacheable 200/301/302 responses at the edge and keeps dynamic traffic flowing safely to Apache.
An open-source Varnish caching layer for cPanel & WHM servers — built for modern AlmaLinux, Ubuntu and CloudLinux hosting stacks.
Why it exists
ReefCache gives hosting operators a clean, auditable replacement path for legacy cPanel Varnish integrations while keeping Apache and WHM in control.
Varnish handles cacheable 200/301/302 responses at the edge and keeps dynamic traffic flowing safely to Apache.
Hitch terminates TLS and passes PROXY data so cPanel vhosts, HTTPS detection and real visitor IPs behave correctly.
Designed around EasyApache, cPanel Apache ports, WHM hooks, certificate sync and the realities of shared hosting servers.
Simple shell, Python, VCL and PHP components make the stack easy to inspect, fork, repair and uninstall.
ReefCache sits in front of cPanel Apache instead of replacing it, preserving normal hosting workflows.
Built for root admins who want predictable commands, readable config files and reversible changes.
Architecture
The intended production flow is transparent and easy to debug: visitors reach Hitch on 443, Varnish caches on 80, and Apache serves origin traffic on non-public cPanel ports.
Install path
Before running any installer, test on a disposable cPanel server, keep WHM access open, snapshot the VPS and confirm firewall rules for ports 80 and 443.
# review first, run second git clone https://github.com/YOUR-ORG/reefcache.git cd reefcache less install.sh bash install.sh # verify response headers curl -I https://your-domain.tld/ x-reefcache-cache: HIT
FAQ
ReefCache is an open-source Varnish caching and SSL proxy integration for cPanel & WHM servers.
No. It is server-side caching in front of Apache. WordPress benefits from faster anonymous page delivery, but the cache sits at the server layer.
No. Apache remains the cPanel origin web server while Varnish and Hitch handle public traffic in front of it.
No. ReefCache is an independent open-source project intended to provide a transparent modern replacement path for similar server-cache workflows.