you need to learn Load Balancing RIGHT NOW!! (and put one in your home network!)

NetworkChuck Technology Careers Career & Money

About this video

Chuck installs Kemp’s free LoadMaster load balancer in his home network and uses it as a secure single entry point to all his home services. He first explains load balancing with a website example: when one server is overwhelmed, a load balancer distributes visitors across multiple servers. The home problem is different: reaching a Plex server, NAS, or website from outside normally means opening a separate router port for each service (he cites port 32400 for Plex), which is insecure, and port 443 can only be forwarded to one internal machine anyway. His fix: forward only port 443 to the Kemp virtual appliance, give its virtual service a virtual IP (10.7.1.30 in his network), and hang each service off it as a sub-virtual service pointing at a real server. The free tier’s main limit is a 20 megabits per second throughput cap. He sets the appliance up on VMware ESXi from the OVF download, pinning static MAC addresses because the license is tied to them, and licenses it free with a Kemp account. For naming and SSL he registers a free Freenom domain (hackwell.tk, 12 months free), moves DNS to Cloudflare, and points A records at his home IP with Cloudflare’s proxy hiding the real address. Cloudflare’s free universal SSL provides a wildcard certificate; he then sets SSL mode to Full (Strict) by generating a CSR on the Kemp, creating a Cloudflare origin certificate from it, installing the certificate and Cloudflare root on the LoadMaster, and enabling SSL acceleration plus re-encryption on the virtual service. The key trick is layer 7 content switching: a content rule matches the Host header, so plex.hackwell.tk routes to his Plex server’s port 32400, while other subdomains reach his two NAS boxes, Proxmox, ESXi, and a website, all over the single open port with valid HTTPS. He demos Kemp’s health checks (switching Proxmox’s check to ICMP ping when HTTPS checks failed), shows the website actually load-balancing across two real servers with automatic failover when he shuts one down, and notes the built-in web application firewall included free. Kemp sponsored the video, and Chuck says he also received a retail license for his own deployment.

Key takeaways

A load balancer in a home network acts as a reverse proxy: one open port (443) reaches every internal service securely
Kemp’s free LoadMaster is a virtual appliance with enterprise features; its main free-tier limit is a 20 Mbps throughput cap
A free Freenom domain plus Cloudflare DNS gives a hidden home IP and a free wildcard SSL certificate
Layer 7 content rules route by subdomain (Host header), sending each name to the right internal server and port
Health checks and weighted real servers give real load balancing and automatic failover, demonstrated live between two web servers

Episode details: published June 18, 2021 · 42:42 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: apt, dpkg, git, Python PiP (Linux Package Management) // Linux for Hackers // EP 5 · Next: You need a NAS RIGHT NOW!! (How I run my Hybrid-Cloud YouTube business) →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube