Qbittorrent docker6/22/2023 ![]() ![]() This file can be found in the dockers config directory in /qBittorrent/config WebUI: Invalid Host header, port mismatch This is the default setting unless changed. WebUI\CSRFProtection must be set to false in nf if using an unconfigured reverse proxy or forward request within a browser. GID applied to config files and downloadsĪpplies WebUI port to qBittorrents config at boot (Must change exposed ports to match)Īpplies Incoming port to qBittorrents config at boot (Must change exposed ports to match)Īccess from a browser on the same network. UID applied to config files and downloads If username and password provided, configures ovpn file automatically In the meantime, the container's DNS resolver is set using the DNS environment suggests using docker-autoheal by adding the autoheal=true label to the container to automatically restart it when the container becomes unhealthy (qBittorrent or OpenVPN crashes).Variables, Volumes, and Ports Environment Variables Variable I have not managed to write proper iptables rules to allow this traffic, if you have any idea how, leave an issue ?. No support for docker's built in DNS server Docker has an embedded DNS server that containers query to get the IPs of other containers, however, Docker does some weird iptables trick to redirect containers' DNS requests to its resolver at 127.0.0.11.No IPv6 support I have not installed iptables for IPv6 as such the firewall kill switch will probably not work with IPv6 (I have not tested it) if you need it, file an issue and I'll look into it when I have some time.This means that in order to use qBittorrent's torrent Search functionality you have to use the version of this image based on the official python alpine docker image, this image is tagged python, in order to download it, please use guillaumedsde/alpine-qbittorrent-openvpn:python. In order to be as light as possible, the latest tagged docker image does not include python. ovpn file at /config/openvpn/config.ovpn optionally set your OPENVPN_USERNAME and OPENVPN_PASSWORD leaving the OPENVPN_PROVIDER empty and the container will load your configuration upon start. If your provider is not in the supported list or if is currently not working, you can mount your. Selecting a preloaded configuration works the same way as the haugene container (see below for an example). It is possible I might have messed something up, so if one provider is not working for you, make sure to leave an issue on this repository's Github page. This image makes use of the VPN providers' OpenVPN configurations from the latest version of haugene/docker-transmission-openvpn cheers to that project ?! ? OpenVPN configuration Officially supported ?):Īll you have to do is use a recent version of docker and it will pull the appropriate version of the image guillaumedsde/alpine-qbittorrent-openvpn from the docker hub. This container is built for many hardware platforms (yes, even ppc64le whoever uses that. NET_ADMIN image: guillaumedsde/alpine-qbittorrent-openvpn:latest ?️ Supported platforms "/etc/localtime:/etc/localtime:ro " environment: ↔️ Port forwarding support for PrivateVPN, Private Internet Access and Perfect Privacy.? Compatible with most OpenVPN providers.?️ Runs as unprivileged user with minimal permissions.?️ Minimal software dependencies installed.?️ Alpine Linux small and secure base Docker image.The image aims to be safe, small and generally minimal by installing as little dependencies as possible and running qBittorrent and OpenVPN as different unprivileged users. ![]() This container is based on an Alpine Linux and uses the S6-overlay for starting setting up the firewall, VPN tunnel and lastly starting qBittorrent. The container is built automatically whenever the Alpine container is updated, the final image is available on the docker hub and the documentation is hosted on gitlab pages. This repository contains the code to build a docker container with the qBittorrent torrent client with all traffic routed through an OpenVPN tunnel with firewall rules preventing traffic outside of the tunnel. I will leave this repository up for archival purposes and will add a disclaimer to the docker image at launch. I would advise migrating to another solution for running a containerized qbittorrent with a VPN tunnel such as: This project has served me well for a while, but has important SECURITY ISSUES that I no longer have time to fix: I no longer have time to maintain this project. ![]()
0 Comments
Leave a Reply. |