docker-qbittorrentvpn VS docker-pi-hole

https://github.com/DyonR/docker-qbittorrentvpn is the container I use so I don’t see an easy way to use port forwarding with this method.

I am running this docker image on my raspberry pi (https://github.com/DyonR/docker-qbittorrentvpn) , which runs a qbittorrent over wireguard(client). I have setup a wireguard server on a vps.

Unless he stopped using GitHub idk https://github.com/DyonR/docker-qbittorrentvpn

After changing CIDR I decided to try one more thing. qBittorrentVPN , which previous also didn't work now works like a charm. It doesn't have kill switch hardcoded, so I had manually set them to my new CIDR and my local network. I only worry that other apps from TrueCharts might have hardcoded other CIDR bits witch may be a problem in the future But for now it's victory!

Ummm this sounds naive if you ask me but if you use Hetzner with a torrent client combined with vpn (e.g. https://github.com/DyonR/docker-qbittorrentvpn) you should be good to go. Hetzner isn't bad.

I run this one: https://github.com/DyonR/docker-qbittorrentvpn in my kubernetes cluster. It supports IVPN just fine (at least Wireguard, since I don't use OpenVPN). Once the WG tunnel is active, you should have an interface named "wg0" in the interface list: Tools->Options->Advanced->Network Interface. Select that and QBit will use that interface only (which means it won't communicate if the WG tunnel is down; which is what I want.

Your cheaper option but with some learning involved is to rent a hetzner for example, use swizzin in conjuction with something like a vpn for qbittorrent, some details: How to use a vpn with qbittorent? : qBittorrent (reddit.com) Also I believe there is a docker image, here is one: GitHub - DyonR/docker-qbittorrentvpn: Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection Hetzner is in no way public torrent friendly, which is why public trackers must be used only behind a reliable kill-switch vpn option.

The qBit + VPN is a Docker container that uses Wireguard or OpenVPN to route only the qBittorrent traffic through the VPN. It also has a kill switch built in. The project readme can probably explain how it works better than I can

You can request further assistance here: https://github.com/DyonR/docker-qbittorrentvpn/issues

Yesterday I deployed the official pi hole docker container on my raspberry pi 3 and set a custom DNS address on my phone addressing to the pi.

#pihole   pihole:     container_name: pihole     image: pihole/pihole:latest     ports:       - target: 53         published: 53         protocol: tcp         mode: host       - target: 53         published: 53         protocol: udp         mode: host       - "67:67/udp"       - "8070:80/tcp"       - "8073:443/tcp"     environment:       TZ: 'America/Indianapolis'       WEBPASSWORD: #'TEMP_PASSWORD' #'set a secure password here or it will be random'       WEBPASSWORD_FILE: '/etc/pihole/adminpw.txt'     # Volumes store your data between container upgrades     volumes:       - '~/pihole/etc-pihole:/etc/pihole'       - '~/pihole/etc-dnsmasq.d:/etc/dnsmasq.d'     #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities     cap_add:       - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)     #network_mode: host     restart: unless-stopped     #UPTIME KUMA   uptime_kuma:     image: louislam/uptime-kuma:1     container_name: uptime-kuma     volumes:      - uptime-kuma:/app/data     ports:      - 8060:3001     restart: always

version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped

services: pihole: container_name: pihole image: pihole/pihole:latest hostname: pihole # Container hostname (optional) domainname: mynetwork.local # Container domain (optional) mac_address: f7:55:63:b0:68:83 # Random MAC address (optional) networks: virtualnet: # Name of macvlan ipv4_address: 192.168.100.249 # Desired IP for pihole dns: - 127.0.0.1 - 1.1.1.1 ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" - "443:443/tcp" volumes: - ./pihole-configs/:/etc/pihole/ - ./dnsmasq.d-configs/:/etc/dnsmasq.d/ # DNSMASQ_USER # https://github.com/pi-hole/docker-pi-hole/issues/963 # https://github.com/pi-hole/docker-pi-hole/blob/master/README.md#upgrade-notes environment: FTLCONF_LOCAL_IPV4: 10.59.0.6 # Desired IP for pihole VIRTUAL_HOST: pihole.mynetwork.local DNSMASQ_USER: root PIHOLE_DNS_: 1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001 restart: unless-stopped # Set container to always restart

You could have a look at docker and try to run a more recent Ubuntu image on the Nano https://github.com/pi-hole/docker-pi-hole

My advice would be either use the docker-pi-hole documentation/quick start, or contact the content creator.