OMV6 With qbittorrent and wireguard?

I finally got around to switching my qbittorrent to the Trigus42/alpine-qbittorrentvpn one. There was a question posed earlier about can you just change the image name, so I figured I'd try it.

For those interested, it does work to just change the name (I did back up the existing configs first as a safety), but you will still have to do the extras script gderf posted above to get back the python install.

The new container came up with all the setting in place that I had made and kept the status of the torrents. As noted earlier in the thread, I do have qbittorrent bound to my wg0 interface, so I also tested taking the wg0 interface down (dropping the vpn) to make sure it didn't continue to download and I'm happy to say the downloads stopped, then after a few seconds the container restarted to initiate the connection again, so it appears to give the same functionality as with the DyonR container and with the container gderf was continuing with for a while.

Has anyone configured this Jackett plugin? Or isn't it a plugin? Or a different docker container?

My search plugins don't seem to respond anymore...

I don't know why "search engine" reads 192.168.1.9, because that's a different device than the one running OMV (and thus Qbittorrent). 192.168.1.9 is my primary DNS server, but does that mean it should be listed there?

Anyway, no other plugins give results, although there are plugins activated:

If I click "controleren op updates", I see this in /config/qBittorrent/data/logs/qbittorrent.log:

(I) 2024-11-17T17:59:53 - Python-executable teruggevonden. Naam: "python3". Versie: "3.11.10"
(I) 2024-11-17T18:00:49 - Alle plugins zijn al bijgewerkt.

So Qbittorrent claims all plugins are up-to-date.

Is there a way to uninstall plugins? Google doesn't really give answers. But maybe that wouldn't solve anything anyway...

Does anyone have a wonderful idea?

Much obliged!

The jacket plugin is a link to a running jackett instance. Do you have a jackett container running? You need that to link it to. Did you also create the extras script mentioned above? It installs python inside the container, which is used by the plugin. If python is not installed the plugin will not work.

Quote from BernH

The jacket plugin is a link to a running jackett instance. Do you have a jackett container running? You need that to link it to. Did you also create the extras script mentioned above? It installs python inside the container, which is used by the plugin. If python is not installed the plugin will not work.

Python is installed. It's now apparently version 3.11.10, where it was 3.11.9 when I originally created that extra script, but I assume that's not the reason for a problem...

I'll look into adding Jackett to the container. (Or is it better to create a separate container?)

Quote from ErikDB

Python is installed. It's now apparently version 3.11.10, where it was 3.11.9 when I originally created that extra script, but I assume that's not the reason for a problem...

I'll look into adding Jackett to the container. (Or is it better to create a separate container?)

I run it as a separate container

Here is my compose file for reference

services:
  jackett:
    image: lscr.io/linuxserver/jackett:latest
    container_name: jackett
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/St_Johns
      - AUTO_UPDATE=true #optional
      - RUN_OPTS= #optional
    volumes:
      - /srv/dev-disk-by-uuid-d69073e2-e8f5-4605-aaa2-eb2c662b20b4/appdata/jackett:/config
    ports:
      - 9117:9117
    restart: always

If you run prowlarr, you can also add this to the qbittorrent /qBittorrent/data/nova3/engines directory in the persistent data directories to use it as a search engine either in addition to or in place of jackett

GitHub - swannie-eire/prowlarr-qbittorrent-plugin: Prowlarr Plugin for Qbittorrent

Prowlarr Plugin for Qbittorrent. Contribute to swannie-eire/prowlarr-qbittorrent-plugin development by creating an account on GitHub.

github.com

Quote from BernH

I finally got around to switching my qbittorrent to the Trigus42/alpine-qbittorrentvpn one. There was a question posed earlier about can you just change the image name, so I figured I'd try it.

For those interested, it does work to just change the name (I did back up the existing configs first as a safety), but you will still have to do the extras script gderf posted above to get back the python install.

The new container came up with all the setting in place that I had made and kept the status of the torrents. As noted earlier in the thread, I do have qbittorrent bound to my wg0 interface, so I also tested taking the wg0 interface down (dropping the vpn) to make sure it didn't continue to download and I'm happy to say the downloads stopped, then after a few seconds the container restarted to initiate the connection again, so it appears to give the same functionality as with the DyonR container and with the container gderf was continuing with for a while.

Just did the same this morning, everything kept, even the tun0 interface it was using, so all seems good thus far.

gderf or BernH ive been really Ill for the past 3 months and have just got back on the computer. any chance one of you fine people could share the compose yaml you use for this new vpn torrent. Thanks

Quote from gderf

Code

services:

  qbittorrent:
    image: trigus42/qbittorrentvpn:latest
    container_name: alp-qbt

    environment:
      - VPN_TYPE=wireguard
#      - VPN_TYPE=openvpn
      - BIND_INTERFACE=yes
      - DEBUG=yes
      - DOWNLOAD_DIR_CHOWN=yes
      - ENABLE_SSL=no
      - HEALTH_CHECK_HOST=1.1.1.1
      - HEALTH_CHECK_INTERVAL=30
      - HEALTH_CHECK_TIMEOUT=20
      - NAME_SERVERS=1.1.1.1,1.0.0.1
      - PGID=100
      - PUID=1001
      - TZ=America/New_York
      - UMASK=022
      - VPN_ENABLED=yes

    volumes:
      - /srv/d0/docker/docker-config/alpine-qbittorrentvpn:/config
      - /srv/mergerfs/multimedia/.tmp/qbittorrent-downloads:/downloads
     
    ports:
     - 7071:8080
     - 8999:8999/tcp
     - 8999:8999/udp

    restart: unless-stopped

    cap_add:
      - NET_ADMIN

    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv6.conf.all.disable_ipv6=1

Display More

Thanks do I still use the wg0 file same as before?

Quote from BlueCoffee

Thanks do I still use the wg0 file same as before?

Yes.

I noticed that the update to the trigus container a couple of months ago seems to have stopped a tinyproxy container I run from using the qbittorrent container network. As an alternative I have been looking at using the hotio qbittorrent container instead as it has the same kind of vpn capability and already has privoxy incorporated.

Preliminary tests look good but it isn't as simple as swapping the container like it was with the trigus container as the queue is not migrating, so I am waiting until my current queue decreases is size before doing the change to the hotio one, so I will have a much smaller amount to manually migrate. If you don't have a large queue in progress, it might be worth looking at that one too.

Is the coldsilk fork in this thread going to be updated to qbittorrent 5? I don't how or where to ask about this, but I've been using this container for about a year without problems but I want new features from 5.x. This forum was the 4th hit for search "coldsilk docker-qbittorrentvpn" and I can't find anything besides the github.The container was last updated a few weeks ago but only to the last/final 4.6.7 version along with libtorrent to 1.2.20 but qbittorrent 5.x has libtorrent 2.x and has larger memory support, which is what I want.

Or can someone update it? I found that the "source" and is actually inside the image you pull in "/_app_src/" and I've tried to edit the Dockerfile the best I know (very little) to get 5.x/2.x working but it is not working and I feel lost. I also tried getting libtorrent 2.x to work with 4.6.7 and that did not work.

coldsilk's docker-qbittorrentvpn seems to be inactive to me, and it was forked from an image I no longer maintain.

I suggest using Trigus42's image instead.

https://github.com/Trigus42/alpine-qbittorrentvpn

hub.docker.image was updated some weeks ago, but only to the final 4.6.7 qbittorrent, so I think it is finally inactive now. I tried Trigus42, but do not see same options I use. Do you know something I can add to the "Trigus42" to get the coldsilk options?I can't find other Docker that has same options. Maybe someone can add these coldsilk options? "HEALTH_CHECK_FAILURES" "VPN_DOWN_SCRIPT" "VPN_CONF_SWITCH"? Or are these options in Trigu42 and I do not see them? I have 3 thousand of torrents and the Docker will not stay working without these.

Thank you for the help. I will try Trigus42 and see if it can stay working longer.

I can't help you with what you seek other than to say try to figure out how to build the coldsilk image yourself but with the latest Qbittorent version. The options you are looking for are not in the Trigus version.

Quote from nopromises

hub.docker.image was updated some weeks ago, but only to the final 4.6.7 qbittorrent, so I think it is finally inactive now. I tried Trigus42, but do not see same options I use. Do you know something I can add to the "Trigus42" to get the coldsilk options?I can't find other Docker that has same options. Maybe someone can add these coldsilk options? "HEALTH_CHECK_FAILURES" "VPN_DOWN_SCRIPT" "VPN_CONF_SWITCH"? Or are these options in Trigu42 and I do not see them? I have 3 thousand of torrents and the Docker will not stay working without these.

Thank you for the help. I will try Trigus42 and see if it can stay working longer.

The Dyonr qbittorrent container and then the gderf fork/improved versions were the best ones I have seen so far, and the trigus one was not a bad alternative.

I'm not sure if this info will help you, but just figured I'd throw it out there as the same concepts can be used on a lot of containers.

I have personally switched to the hotio qbittorrent. I switched to the hotio one because I wanted to use a tinyproxy or privoxy attached to the vpn in the container to allow for easy vpn access by other containers without having to run a second vpn connection. I used to do this easily, but a trigus update about 6 or 8 months ago caused this to stop working and I couldn't seem to figure out what was happening and how to handle the inbuilt firewall that seemed to be blocking it. The hotio container has an inbuilt privoxy, and it doesn't seem to suffer from some of the quirks I had before when trying to attach the proxy to the qbittorrent vpn that required doing a proxy restart on a schedule.

However, it does not have the health check and vpn connectivity options to restart the container in the event of problems.

To get around this, I have implemented a compose based heath check that checks for connectivity through the wg vpn only by trying to curl a website or ping an ip address depending on the check you want (other checks can be used for other containers is needed), and if it fails, it tags the container as unhealthy. I then have another container running called autoheal that monitors for any container that is marked unhealthy and restarts it. This compose based healthcheck with the autoheal container type of process can be implemented on any container to get it to automatically restart if it is not functioning correctly.

GitHub - willfarrell/docker-autoheal: Monitor and restart unhealthy docker containers.

Monitor and restart unhealthy docker containers. Contribute to willfarrell/docker-autoheal development by creating an account on GitHub.

github.com

    healthcheck:
      # Choose one of the following 2 tests and adjust as required based on container requirements
      test: "curl --interface wg0 -sf https://example.com  || exit 1"
      #test: "ping -I wg0 -c 1 8.8.8.8 || exit 1"
      interval: 5m
      timeout: 10s
      retries: 3