# For persisting qBitTorrent configuration files Image: ghcr.io/linuxserver/qbittorrent:14.3.9 # I recommend using this for the time being, because 4.4.x seems to be having various issues, including performance and memory leak issues. # `:14.3.9` locks the qBitTorrent version to v4.3.9. # This means that the host's port "8080" will now forward to port "8888" on the qBitTorrent container. # The secondary `8888` matches the `WEBUI_PORT` on the qBitTorrent container. # I run NGINX on the host server for a reverse proxy. # based on the filename of `nf` in `/etc/wireguard/nf` # Keep in mind that the "Network interface" within qBitTorrent (second screenshot on wiki) is named # The last part after `:` isn't important, besides the fact it needs to be within `/etc/wireguard`. If you use `nf` instead, the line should look similar to: # Alternatively: change the line below to match your local filename. # and put it in the same folder as `docker-compose.yml` I also recommend forcing qBitTorrent to use the Mullvad network interface (Advanced -> Network interface), though I'm not sure if it matters much Port forwardingįor port forwarding to work via Mullvad, you have to set the "Listening port" (Settings -> Connection -> Listening port) in qBitTorrent to the correct forwarded port from Mullvad. You will also restrict the amount of peers you can upload (seed) to. Keep in mind that without port forwarding, you'll usually end up with less peers and thus downloads make take longer. Port forwarding will only work if the VPN provider supports port forwarding, but torrenting might still work regardless. Note: In theory this should work with other VPN providers, but I have only tested it with Mullvad specifically. Sample Docker Compose configuration for running qBitTorrent as a container routed through another Mullvad container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |