htpc-download-box VS gluetun

This is a decent starting point: https://github.com/sebgl/htpc-download-box

I want to setup a Plex media server and I have been following this tutorial which uses a dockerised sonarr, radarr, etc. I want to set this up on an old PC without needing a monitor. I was hoping to access the sonarr and radarr web ui through my Mac which is my main laptop. Is this possible? I’ve been searching for a while but I can’t find an answer that works. Any help and/or tips is appreciated. Thank you!

I use Docker to host Radarr/Sonarr for organization, other stuff for getting files and Plex for playing. A modified version of https://github.com/sebgl/htpc-download-box.

I use docker for my... gathering... basically a variation of https://github.com/sebgl/htpc-download-box. the stack that supports plex.

As far as 'tutorial', I don't know what's out there. I don't know if you're a Linux user or Windows. There are various docker containers and builds out there for setting this stuff up but I don't know how it all works under Windows (or if it even does). https://github.com/sebgl/htpc-download-box seems maybe relevant.

I use a modified version of this

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki