OMV6 docker

Quote from gderf

You tried that with the alpine-qbittorrentvpn image?

Oh hell I am sorry, I forgot you moved onto that. It was Dyonir. MY BAD

Quote from gderf

5) Down the container and bring it back up. This will install python3 when it first runs.

Okay, got this to work.

But:

(I) 2024-08-20T20:14:54 - Python gedetecteerd, naam van executable: 'python3', versie: 3.11.9
(I) 2024-08-20T20:14:57 - Plugin dmhy wordt niet ondersteund.

Google translate:

(I) 2024-08-20T20:14:54 - Python detected, executable name: 'python3', version: 3.11.9
(I) 2024-08-20T20:14:57 - Plugin dmhy is not supported.

I tried it with a number of search plugins... All the same result.

The search plugins work for me. I even installed the dmhy plugin via its URL.

Where did you get that stuff in the code box you posted?

Quote from gderf

Where did you get that stuff in the code box you posted?

/appdata/qbittorrentvpn-trigus/qBittorrent/data/logs/qbittorrent.log

Maybe the VPN or Wireguard isn't working properly? Can I test that somehow?

If the VPN or Wireguard is not working then either the QBT web GUI will not start or it will show an error that qBittorrent client is not reachable

So that's not it... Maybe I should create an issue in Github?

Is the problem that the search doesn't work or the entire container doesn't work?

Quote from gderf

Is the problem that the search doesn't work or the entire container doesn't work?

The container looks like it's working. But I can't install a search plugin, so I can't test the actual downloading (since I don't have a download link)...

Open the Search Tab and click on the Search plugins button and post a screenshot.

Although, after clicking "Controleren op updates", it looks like this:

And all of a sudden, I can install search plugins... Only "zoogle" is still not supported.

Now it's just a matter of disabling the ones that don't give working links (like LimeTorrents). Is there a way to uninstall a search plugin?

Thanks for your intensive help, once again!

Quote from gderf

apk add speedtest-cli > /dev/null

What does this do? I mean, I can take a guess of course But how would it work?

Quote from BernH

While setting up the new $3/month provider (purevpn) in the qbittorrent-vpn container I figured it might be prudent to check the vpn speed, ip address and check for DNS leaks, just to be 100% comfortable.

So I bashed into the container and ran a speedtest and a curl ifconfig.co to confirm the ip address, and grabbed this to check for DNS leaks. While easy to install and run, it might be a good script to include in the image build.

https://github.com/macvk/dnsleaktest

How exactly did you do this?

Quote from ErikDB

How exactly did you do this?

How did I do what? Set up a new vpn, bash into the container, use the dns leak test, run the commands, etc?

Quote from BernH

bash into the container, use the dns leak test, run the commands, etc?

This

In the shell:

docker exec -it container_name bash

Once inside you can type supported commands.

Type exit to leave.

The link I posted to the leak test is just shell script. Save it into a directory that is mapped into the container, make it executable and the run it once you bash into the container by navigating to the directory and running the script.

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.