OMV6 With qbittorrent and wireguard?

Me neither

Zitat von olduser

Does anyone use the SSL option in this qbittorrentvpn container? If so, why?

Nor I. Honestly did not even realize it was an option until this more recent responses on this thread.

Zitat von fbeye

Nor I. Honestly did not even realize it was an option until this more recent responses on this thread.

I knew it was an option, just never saw a need for it if I am only accessing it from my lan, and I wouldn’t want it exposed to the internet, so to me there is absolutely no need.

HTTPS seems to be required if you want to register the client to use magnet links. Click on the Tools menu.

I can't answer any questions about this though.

Zitat von gderf

HTTPS seems to be required if you want to register the client to use magnet links. Click on the Tools menu.

I can't answer any questions about this though.

I just copy and paste magnet links when I need to.

Since qbittorrent is not actually running on the same system as my browser, there is no local client to register in the browser, so I never even thought to pursue it.

Zitat von BernH

I just copy and paste magnet links when I need to.

Since qbittorrent is not actually running on the same system as my browser, there is no local client to register in the browser, so I never even thought to pursue it.

I don't copy and paste magnet links. The Remote Torrent Adder browser extension allows me to "send" them to Qbt running on the server and/or the foreign seedbox I use.

Did OMV 7 add a firewall? omv.local:9090 is timing out to the NAS.

Admittedly, I haven't tested with OMV 7 before, I've been using OMV 6 for a while at work for testing. The container is up and running correctly on the NAS, I just can't connect to the webui, the connection times out.

I haven't changed this script in a long time and it works on the host machine's Docker using localhost:9090, but it times out connecting to the NAS with omv.local:9090 (also using the ip 192.168...)

What am I overlooking?

EDIT: Nevermind, it is definitely something to do with this qbittorrentvpn container. linuxserver's works fine and so does gluetun and so does gluetun+qbittorrent.

sudo docker run -d \
  --name="qbittorrent" \
  --cap-add=NET_ADMIN \
  --device=/dev/net/tun \
  --net="downloaders" \
  --ip "172.18.0.100" \
  -v "$downloads/qbittorrent":"/downloads" \
  -v "$downloads/qbittorrent":"/config" \
  -e "INSTALL_PYTHON3=yes" \
  -e "PUID=1000" \
  -e "PGID=1000" \
  -e "VPN_TYPE=wireguard" \
  -e "LAN_NETWORK=192.168.0.0/16,172.18.0.0/16" \
  -e "QBT_WEBUI_PORT=9090" \
  -p 9090:9090 \
  -p 45000:8999 \
  -p 45000:8999/udp \
  --restart unless-stopped \
  "$image"

It's container issue. The file "iptables.sh" effectively hardwires port 8080 for the WebUI, so QBT_WEBUI_PORT isn't observed.

Zitat von olduser

It's container issue. The file "iptables.sh" effectively hardwires port 8080 for the WebUI, so QBT_WEBUI_PORT isn't observed.

What image are you using here?

Your image or any image with that exact "iptables.sh" file. Here's yours: https://github.com/gderf/docke…ittorrent/iptables.sh#L85 Every rule with a port uses 8080...

Sample:

# accept input to qBittorrent webui port
iptables -A INPUT -i "${docker_interface}" -p tcp --dport 8080 -j ACCEPT
iptables -A INPUT -i "${docker_interface}" -p tcp --sport 8080 -j ACCEPT

Zitat von olduser

Your image or any image with that exact "iptables.sh" file. Here's yours: https://github.com/gderf/docke…ittorrent/iptables.sh#L85 Every rule with a port uses 8080...

Sample:

Code

# accept input to qBittorrent webui port
iptables -A INPUT -i "${docker_interface}" -p tcp --dport 8080 -j ACCEPT
iptables -A INPUT -i "${docker_interface}" -p tcp --sport 8080 -j ACCEPT

Well, I am running on 7070 but don't use a QBT_WEBUI_PORT= statement. Is that even supported?

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

Is that even supported?

Yeh, it's one of the few... https://github.com/qbittorrent/docker-qbittorrent-nox

Sadly, there isn't one for the torrent port :-/.

These are the few I see listed:

EDIT: actually this isn't the official doc :-/, sorry just noticed. It does work however.

  QBT_EULA=<put_accept_here> \
  QBT_VERSION=latest \
  QBT_WEBUI_PORT=8080 \
  QBT_CONFIG_PATH="<your_path>/config" \
  QBT_DOWNLOADS_PATH="<your_path>/downloads"

Zitat von olduser

Yeh, it's one of the few... https://github.com/qbittorrent/docker-qbittorrent-nox

Sadly, there isn't one for the torrent port :-/.

These are the few I see listed:

EDIT: actually this isn't the official doc :-/, sorry just noticed. It does work however.

Code

  QBT_EULA=<put_accept_here> \
  QBT_VERSION=latest \
  QBT_WEBUI_PORT=8080 \
  QBT_CONFIG_PATH="<your_path>/config" \
  QBT_DOWNLOADS_PATH="<your_path>/downloads"

Alles anzeigen

But QBT_WEBUI_PORT isn't listed as an available option or environment variable in Dyonr's image.

Zitat von gderf

isn't listed as an available option ... in Dyonr's image.

I don't know how to convince you of this but... Dyonr .... didn't .... care!!! Please believe me on this. I don't blame him either, I really don't, not when you can use compose with Gluetun and qBittorrent and be done with it. I only started modifying it to add a conf switcher, I should have stopped there :-/.

Actually I'm wrong again, QBT_TORRENTING_PORT=xxxx is apparently supported. Here's the --help print for qbittorrent-nox:

root@cd6ba3712fc0:/opt# /usr/local/bin/qbittorrent-nox --help
Usage:
    /usr/local/bin/qbittorrent-nox [options] [(<filename> | <url>)...]
Options:
    -v | --version             Display program version and exit
    -h | --help                Display this help message and exit
    --webui-port=<port>        Change the WebUI port
    --torrenting-port=<port>   Change the torrenting port
    -d | --daemon              Run in daemon-mode (background)
    --profile=<dir>            Store configuration files in <dir>
    --configuration=<name>     Store configuration files in directories
                               qBittorrent_<name>
    --relative-fastresume      Hack into libtorrent fastresume files and make
                               file paths relative to the profile directory
    files or URLs              Download the torrents passed by the user

Options when adding new torrents:
    --save-path=<path>         Torrent save path
    --add-paused=<true|false>  Add torrents as started or paused
    --skip-hash-check          Skip hash check
    --category=<name>          Assign torrents to category. If the category
                               doesn't exist, it will be created.
    --sequential               Download files in sequential order
    --first-and-last           Download first and last pieces first
    --skip-dialog=<true|false> Specify whether the "Add New Torrent" dialog
                               opens when adding a torrent.

Option values may be supplied via environment variables. For option named
'parameter-name', environment variable name is 'QBT_PARAMETER_NAME' (in upper
case, '-' replaced with '_'). To pass flag values, set the variable to '1' or
'TRUE'. For example, to disable the splash screen: 
QBT_NO_SPLASH=1 /usr/local/bin/qbittorrent-nox
Command line parameters take precedence over environment variables

Zitat von olduser

I don't know how to convince you of this but... Dyonr .... didn't .... care!!! Please believe me on this. I don't blame him either, I really don't, not when you can use compose with Gluetun and qBittorrent and be done with it. I only started modifying it to add a conf switcher, I should have stopped there :-/.

Actually I'm wrong again, QBT_TORRENTING_PORT=xxxx is apparently supported. Here's the --help print for qbittorrent-nox:

qbittorrent-nox is not dyonr/qbittorrentvpn.

Zitat von gderf

qbittorrent-nox is not dyonr/qbittorrentvpn.

Login into your running container, run: ps -e.

Zitat von olduser

Login into your running container, run: ps -e.

I didn't say anything about the binary. I said that the images are not the same, and that's where big differences in options can come in.

Zitat von gderf

QBT_WEBUI_PORT= statement. Is that even supported?

Zitat von gderf

QBT_WEBUI_PORT isn't listed as an available option

Zitat von gderf

qbittorrent-nox is not dyonr/qbittorrentvpn.

Zitat von gderf

I didn't say anything about the binary

QBT_WEBUI_PORT is supported and so is QBT_TORRENTING_PORT and other variables. The scripts in this "qbittorrentvpn" container do not use any variables that start with "QBT_", so you can add those to your compose/run script.

The SSL option isn't needed to send magnets/files. The SSL option kind of promotes bad usage and since nobody seems to use it, I'm going to remove it from my next image (after qBittorrent v5.0 is final).

I've posted this script before for magnets and *.torrent files. If you set "Bypass authentication for clients in whitelisted IP subnets" to 192.168.1.0/24 (or whatever) you won't need the username and password. If you're using a browser in Ubuntu's Snap or similar, it won't work since curl is not package with it, you'll have to RTFM on how to get curl working.

#!/bin/bash

# exec &> >(tee -a "$HOME/Downloads/$(basename "$0").log.txt")

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
  # If you set "Bypass authentication for clients in whitelisted IP subnets" to
  # 192.168.1.0/24 (or whatever) you won't need the username and password.
  username="admin"
  password="adminadmin"
  # the ip and port that qbittorrent is listening on
  ip_and_port=omv.local:8080;

  # enforce ".torrent" to be the last 8 characters of a filename
  # 0 = no, 1 = yes
  enforce_name=1;
  # write magnets and move torrent files to this directory (magnets are saved with .magnet extension)
  # - does not overwite, uses: mv -n "$source_file" "$torrents_dir"
  # - must be an existing directory
  # torrents_dir="$HOME/torrents/";

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

  if [ "$1" == "no_enforce" ]; then
    enforce_name=0;
    shift;
  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 "sid is:$sid"
    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=();
  magnets=();
  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");
        magnets+=("$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
      for j in "${magnets[@]}"; do
        idx=0;
        while true; do
          idx=$(($idx + 1));
          dn="$(echo "$j" | cut -d '&' -f $idx)"
          if [ "$dn" == "" ]; then break; fi
          dn_temp="${dn:0:3}"
          if [ "${dn_temp,,}" == "dn=" ]; then
            echo "$i" > "$torrents_dir/${dn:3}.magnet.torrent"
            break;
          fi
        done
      done
    fi
    return 0;
  fi
  return 1;
)

# (return 0 2>/dev/null) || { magnet_forward "$@"; return $?; };
# # Determines if the script was sourced or not.
# # If ! (return 0 2>/dev/null) evaluates to true, then not sourced.
if ! (return 0 2>/dev/null); then
  magnet_forward "$@"
  exit $?;
fi

# 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=)[^;]*');

Zitat von olduser

QBT_WEBUI_PORT is supported and so is QBT_TORRENTING_PORT and other variables. The scripts in this "qbittorrentvpn" container do not use any variables that start with "QBT_", so you can add those to your compose/run script.

What is the purpose of these two variables? What does using them offer? What is the penalty for not using them?

Zitat von gderf

What does using them offer?

As usual, conflicting ports. If you put all of your downloaders on 1 docker network you might have a problem using port 8080 with qBittorrent if you're also using Sabnzbd's default of 8080 with this image https://docs.linuxserver.io/images/docker-sabnzbd/

linuxserver.io also mentions potential CSRF if all the ports don't match but, I don't understand how that would be a factor unless you run it internet facing.