HAProxy-WI: Run Lots Of Public Services On Your Home Server
Added 2020-07-22 16:11:01 +0000 UTC
Version 2!
Comments
I was originally doing the forwarding bit via nginx, exposing 80 and 443 directly from my home. Using a cheap cloud vm is a neat idea.
Being stuck at home, I've started switching to a home network setup with dnsmasq resolving subdomains to local servers (e.g. plex.my.network -> 192.168.1.X). Since letsencrypt supports auth by dns, I don't have to expose those services publicly and I still get ssl.
Was planning to keep it all local and only expose a VPN service so I can connect to my home network when remote to access plex, freenas, etc.
Are there specific advantages or disadvantages for home use (not a prod web service) to go this route vs a VPN-gated alternative?
2020-07-26 18:35:35 +0000 UTC
you totally could. the haproxy-wi front-end can report more/better stats from haproxy but all the features haproxy has that nginx doesnt mostly doesnt matter for this setup.
Level1 Techs
2020-07-24 14:33:07 +0000 UTC
OK here is a maybe stupid question that I don't think was addressed in the video... couldn't the forwarding be done by just the nginx as well? nginx can act as a reverse-proxy. which HAProxy is doing here as well (since it's not actually load-balancing), no? So why/where does HAProxy come into play here? Why not just use nginx without HAProxy? Did I just miss it in the video?