Reverse Proxy - Comparing the (now) three brands
With Brandons post about NPMPlus, and at what state I am when it comes to handling my internal network associations, I'm curious on which way I should bend my knee to going forward. Right now, I'm running haProxy under pfsense. I'm going to be moving away from using haProxy to "make the decision on where to route each service request" to "make the decision to see if a valid primary domain is requested, or to geoblock, or let traffic through" and redo/copy my existing setup to a dedicated small container within a dedicated VM. (Basically, look to see if my domain suffix is asked for, then route in as needed) I've always been aware of Nginx, but didn't put my toe into their ecosystem for no reason at all. It just never came up because haProxy was there and I used it. So now with NPMPlus, NPM, and haProxy, why would one go with one of these specific three (Or more) for homelab use? Pros, cons, stuff I'm not understanding or even aware of... haProxy is going to remain my bouncer on pfSense, no question. But once the basic firewalls are put up, and traffic can go through, "something" inside the LAN is going to be acting as the traffic cop. Things I'm looking at is ease to recovery (I killed pfSense once for some unknown reason, no idea how, or why, so rebuilt it and had to redo my configs -- Check your backups!) either by backing up the new haProxy settings (pfSense stores its haProxy config within the pfSense single config file which makes getting at this specific info a pain), ease of management (pfSense isn't that bad for handling the dedicated sites) and of course size for memory pressures and such.