Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
It tunnels everything that is bound to the same network (see the line with gluetun within the qbittorrent container.
And for anyone using a reverse proxy: that can run against the gluetun container with the bound containers port. (edit: in OPs example gluetun:8090 for qbittorrent web)
Only qbit
I have other stuff in that stack as well, like sonarr and radarr, that I cut out.
The network mode setting in docker acts as a bind. The port is exposed to the host in gluetun. If gluetun throws an error and shuts down, qBit WebUI is no longer accessible.
Does this only tunnel qbittorrent through the VPN or all traffic on the device?
Have exactly the same setup:
It tunnels everything that is bound to the same network (see the line with gluetun within the qbittorrent container.
And for anyone using a reverse proxy: that can run against the gluetun container with the bound containers port. (edit: in OPs example gluetun:8090 for qbittorrent web)
Only qbit I have other stuff in that stack as well, like sonarr and radarr, that I cut out.
The network mode setting in docker acts as a bind. The port is exposed to the host in gluetun. If gluetun throws an error and shuts down, qBit WebUI is no longer accessible.