OMV6 With qbittorrent and wireguard?

Zitat von gderf

You posted the container log. What's in the application log?

nothing always empty

This sends *.torrent files and magnet urls to whatever $ip:port qbittorent is on. It did work, but I never really used it but maybe someone can use it as an example. I'm posting because I forgot about it until another thread topic.

#!/bin/bash

function magnet_forward() (
  # used with qbittorrent's webserver to add magnet links or files to the queue
  # requires Bash and cURL

  # the user and pass of the web login
  username="admin"
  password="adminadmin"
  # the ip and port that qbittorrent is listening on
  ip_and_port=127.0.0.1:4600;

  # enforce ".torrent" to be the last 8 characters of a filename
  # 0 = no, 1 = yes
  enforce_name=1;
  # move torrent files to this location (only torrent files, not URLs)
  # - does not overwite, uses: mv -n "$source_file" "$torrents_dir"
  # - must be an existing directory
  # torrents_dir="/home/$USER/torrents";

  if [ "$1" == "no_enforce" ]; then
    enforce_name=0;
    shift;
  fi

  if [ ! "$#" -gt "0" ]; then
    echo "ERROR: requires at least 1 argument, received $#"
    return 1;
  fi

  # NOTE: you only need to get the "SID" ("Session ID") once each time the
  # script runs, not for every command.

  # get the "SID" string
  IFS='=;' read -ra sid <<< $(curl -v -d "username=$username&password=$password" -X POST $ip_and_port/api/v2/auth/login 2>&1 | grep "SID");

  if [ -z "$sid" ] || [ -z "${sid[1]}" ]; then
    echo "ERROR: could not parse SID";
    return 1;
  fi

  sid="${sid[1]}";

  if [ ! -z "$(echo $sid | grep '\s\|;\|,')" ]; then
    echo "ERROR: cookie value contains spaces, a semi-colon or a comma. SID="$(echo $sid | grep '\s\|;\|,')
    return 1;
  fi

  files=();
  links=();
  for i in "$@"; do
    if [ ! -z "$i" ]; then
      if [ ! -f "$i" ]; then
        # if it's not a file then assume it's a URL.
        links+=(-F "urls=$i");
      else
        if [ "$enforce_name" ]; then
          tmp="${i,,}"
          if [ "${tmp: -8}" != ".torrent" ]; then
            continue;
          fi
        fi
        links+=(-F "torrents=@$i");
        # for now, skip the directory check for $torrents_dir
        if [ ! -z "$torrents_dir" ]; then
          files+=("$i");
        fi
      fi
    fi
  done

  if [ "${#links[@]}" -gt "0" ]; then
    curl -v -H "Cookie: SID=$sid" -H 'User-Agent: Fiddler' "${links[@]}" $ip_and_port/api/v2/torrents/add;
    # need error handling, currently assuming success by always returning 0
    if [ ! -z "$torrents_dir" ] && [ -d "$torrents_dir" ]; then
      for i in "${files[@]}"; do
        mv -n "$i" "$torrents_dir"
      done
    fi
    return 0;
  fi
  return 1;
)

(return 0 2>/dev/null)  || { magnet_forward "$@"; return $?; };

# below is a better parser to get the SID, but requires a grep with -P support.
# sid=$(curl -v -d "username=${username}&password=${password}" -X POST $ip_and_port/api/v2/auth/login 2>&1 | grep -o -P '(?<=SID=)[^;]*');

Update:

Qbittorrent has been updated to Release 4.6.3

Release announcement:https://www.qbittorrent.org/news

I have updated the gderf/qbittorrentvpn docker image to this latest version of Qbittorrent.

You can see the list of all my images and their tags, and pull statements here:

https://hub.docker.com/repository/docker/gderf/qbittorrentvpn/tags?page=1&ordering=last_updated

If you pull using the :latest tag in your compose file, you will be upgraded to 4.6.3. If you want to stick with some other release, please use the appropriate tag from the above source.

Hi there, apologies if this is a silly question, but is it worth my time to try and get this setup working on my raspberry pi, or should I start from scratch and built my own docker container?

Zitat von JuniorKickstart

Hi there, apologies if this is a silly question, but is it worth my time to try and get this setup working on my raspberry pi, or should I start from scratch and built my own docker container?

The image I supply will only run on AMD64/Intel hardware and I don't think images for other hardware can be built from the sources I use.

Thanks for the reply that’s what I thought, but if there was the possibility of saving some time I wanted to ask.

I'm interested in installing this container on OM7, but I don't know where to begin. The only two docker containers I've installed for now, were through docker-compose. I don't see a similar file here (https://github.com/gderf/docker-qbittorrentvpn)...?

(Once I'm past that hurdle, I was wondering whether you have experience/an opinion on the allegedly free Proton VPN (https://protonvpn.com/free-vpn)?)

(One hurdle further down the road is that I don't know what should be done with that VPN .conf file...)

Thanks in advance for your help!

If using docker-compose you will need a compose file. I'll paste mine in below but you will have to make changes to it for your use case.

I have no experience with Proton VPN.

Follow the directions on the github page as to where to place the VPN .conf file.

See this page for how to login to the interface the first time.

https://www.reddit.com/r/unRAI…n%20the%20container%20log.

My qbittorrentvpn compose file - You must change some things to match your use case.

---
version: "3"
services:
  qbittorrentvpn:
    image: gderf/qbittorrentvpn:latest
    container_name: qbt
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_ENABLED=yes
      - VPN_TYPE=wireguard
      - ENABLE_SSL=no
      - PUID=1001
      - PGID=100
      - LAN_NETWORK=192.168.1.0/24
      - NAME_SERVERS=8.8.8.8,8.8.4.4
      - UMASK=022
      - HEALTH_CHECK_HOST=one.one.one.one
      - HEALTH_CHECK_INTERVAL=30
      - HEALTH_CHECK_SILENT=1
      - HEALTH_CHECK_AMOUNT=10
      - INSTALL_PYTHON3=no
      - RESTART_CONTAINER=yes
    ports:
      - 7070:8080/tcp
      - 8999:8999/tcp
      - 8999:8999/udp
    volumes:
      - /srv/d0/docker/docker-config/qbittorrentvpn:/config
      - /srv/mergerfs/multimedia/.tmp/qbittorrent-downloads:/downloads
    restart: unless-stopped

Zitat von gderf

My qbittorrentvpn compose file - You must change some things to match your use case.

I didn't change that much. I didn't understand some variables, like NAME_SERVERS, and the HEALTH_CHECK ones. So I figured I would just leave them as is.

---
version: "3"
services:
  qbittorrentvpn:
    image: gderf/qbittorrentvpn:latest
    container_name: qbt
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_ENABLED=yes
      - VPN_TYPE=wireguard
      - ENABLE_SSL=no
      - PUID=${PUID}
      - PGID=${PGID}
      - LAN_NETWORK=192.168.1.0/24
      - NAME_SERVERS=8.8.8.8,8.8.4.4
      - UMASK=022
      - HEALTH_CHECK_HOST=one.one.one.one
      - HEALTH_CHECK_INTERVAL=30
      - HEALTH_CHECK_SILENT=1
      - HEALTH_CHECK_AMOUNT=10
      - RESTART_CONTAINER=yes
    ports:
      - 8080:8080/tcp
      - 8999:8999/tcp
      - 8999:8999/udp
    volumes:
      - ./config:/config
      - CHANGE_TO_COMPOSE_DATA_PATH/Qbittorrentdownloads:/downloads
    restart: unless-stopped

I obtained a Wireguard configuration file using this guide (https://protonvpn.com/support/wireguard-configurations/), and put it in ./config//wireguard and named it wg0.conf.

I'm able to access the WebUI, and added a few magnet links for testing purposes. Qbittorrent seems to be able to do something with them, as the file name is downloaded, but only the first added magnet link gets info about the actual files. Also, none of the torrents dowload. And in the left lower corner, an alarming message reads "qBittorrent client is not reachable".

I would like to test connectivity, both by qbittorrent and by the VPN I'm using, but I don't really know how. (Especially for the VPN, as only the Qbittorrent container is using it, and not the linux machine itself.)

Do I need to forward/open up some ports in my router configuration?

Any thoughts?

Thanks in advance!

Zitat von ErikDB

"qBittorrent client is not reachable".

I get this all the time. I have to restart the docker container and it seems to fix it.

Zitat von BlueCoffee

I get this all the time. I have to restart the docker container and it seems to fix it.

I see. I was on my way to do that, but before doing it, I noticed the warning was gone... However, still nothing is downloading. Not even the metadata of the second magnet link I entered.

Zitat von ErikDB

I see. I was on my way to do that, but before doing it, I noticed the warning was gone... However, still nothing is downloading. Not even the metadata of the second magnet link I entered.

the red flame at the bottom means no open port.

also your docker yaml is wrong

      - ./config:/config
      - CHANGE_TO_COMPOSE_DATA_PATH/Qbittorrentdownloads:/downloads

      - PUID=${PUID}
      - PGID=${PGID}

Zitat von BlueCoffee

also your docker yaml is wrong

Code

      - ./config:/config
      - CHANGE_TO_COMPOSE_DATA_PATH/Qbittorrentdownloads:/downloads

Code

      - PUID=${PUID}
      - PGID=${PGID}

Is it? I used this (https://wiki.omv-extras.org/doku.php?id=omv7:docker_in_omv) guide...

Zitat von BlueCoffee

the red flame at the bottom means no open port.

Ok... What port should I open then?

I added the following in Port forwarding on the UI of my Unifi Dream Router. But the flame is still there. And/or should I restart something?

Zitat von ErikDB

Ok... What port should I open then?

I added the following in Port forwarding on the UI of my Unifi Dream Router. But the flame is still there. And/or should I restart something?

no idea what port you have set you will have to look on qbittorret settings.

Zitat von ErikDB

Is it? I used this (https://wiki.omv-extras.org/doku.php?id=omv7:docker_in_omv) guide...

you have to select your user/group and the path you need for config and downloading.

Zitat von BlueCoffee

you have to select your user/group and the path you need for config and downloading.

root@NASLG2:/appdata/qbittorrentvpn/config/qBittorrent# ls
cache  config  data

Based on this, I've got the impression the container is writing files into the correct config folder. No? I sure didn't create these subfolders.

Zitat von BlueCoffee

no idea what port you have set you will have to look on qbittorret settings.

Isn't it 8999, based on the .yaml file? Also here, I see 8999:

But of course, my understanding can be wrong...

Zitat von ErikDB

Isn't it 8999, based on the .yaml file? Also here, I see 8999:

I have port 44444 open on my router and I have 44444 set in qbittorent.

as for the paths here is my compose yaml to give you an idea.

version: "3"
services:
  qbittorrentvpn:
    image: gderf/qbittorrentvpn:latest
    container_name: qbittorrentvpn
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_ENABLED=yes
      - VPN_TYPE=wireguard
      - ENABLE_SSL=no
      - PUID=1000
      - PGID=1000
      - LAN_NETWORK=10.0.0.0/24
      - NAME_SERVERS=1.1.1.1,1.0.0.1
      - UMASK=022
      - HEALTH_CHECK_HOST=one.one.one.one
      - HEALTH_CHECK_INTERVAL=30
      - HEALTH_CHECK_SILENT=1
      - HEALTH_CHECK_AMOUNT=10
      - INSTALL_PYTHON3=yes
      - RESTART_CONTAINER=yes
    ports:
      - 8080:8080/tcp
      - 8999:8999/tcp
      - 8999:8999/udp
    volumes:
      - /srv/dev-disk-by-uuid-7c0064c6-76c5-410c-8194-6724fea2432e/Data/DockerData/qbittorrentvpn:/config
      - /srv/dev-disk-by-uuid-7c0064c6-76c5-410c-8194-6724fea2432e/Leeching:/downloads
    restart: unless-stopped

Zitat von BlueCoffee

I have port 44444 open on my router and I have 44444 set in qbittorent.

But based on my screenshot, I opened the right port, no?

I see my config file is 'buried too deep' bit since I reference it, is that really a problem? Is that what causes the non-downloading?

(I won't be able to test anything until Monday, but any guidance is always useful and interesting :))

Zitat von ErikDB

But based on my screenshot, I opened the right port, no?

I see my config file is 'buried too deep' bit since I reference it, is that really a problem? Is that what causes the non-downloading?

(I won't be able to test anything until Monday, but any guidance is always useful and interesting :))

Alles anzeigen

IF you have opened that port its fine. The path issue is your main issue and that's why you are having problems.