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