Hiding Services Behind HAProxy

  • For anyone that is interested, I've written a short blog post about putting services behind HAProxy. I thought I'd post it here, since it's relevant to people using some of the third-party plugins for things like Sickbeard, Couchpotato, SABnzbd, etc, etc. Plus, if there is sufficient interest, I think HAProxy might be a worthwhile plugin itself.


    Why did I do this?


    Generally, when you set up a service like (say) Sickbeard, it will listen on a particular port (like, say 8080). Any there's a pretty fair chance you'll come across situations where ports like 8080 are blocked -- such as if you are sitting behind a firewall at work, or at university -- but you'd like to access Sickbeard remotely. Of course, you can just configure Sickbeard to listen to port 80, which is the standard port for http traffic, and which is unlikely to be firewalled. But this will conflict with OMV's web interface. Plus, what do you then do with Couchpotato? Or SABnzbd? Or whatever else you are running? They can't all listen on the same port.


    Basically, you can set up HAProxy to listen on port 80, and then redirect traffic according to the URL path. This has a nice little added benefit of allowing you to use URL's that are a bit easier to remember. For example, instead of referencing http://<myserver>:8080 you can use http://<myserver>/sickbeard.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!