Code Monkey home page Code Monkey logo

docker-qbittorrent's Introduction

linuxserver.io

Blog Discord Discourse Fleet GitHub Open Collective

The LinuxServer.io team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Discord - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • Fleet - an online web interface which displays all of our maintained images.
  • GitHub - view the source for all of our repositories.
  • Open Collective - please consider helping us by either donating or contributing to our budget

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

The Qbittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.

qbittorrent

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/qbittorrent:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 amd64-<version tag>
arm64 arm64v8-<version tag>
armhf

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag Available Description
latest Stable qbittorrent releases
libtorrentv1 Static qbittorrent builds using libtorrent v1

Application Setup

The web UI is at <your-ip>:8080 and a temporary password for the admin user will be printed to the container log on startup.

You must then change username/password in the web UI section of settings. If you do not change the password a new one will be generated every time the container starts.

If you are running a very old (3.x) kernel you may run into this issue which can be worked around using this method

WEBUI_PORT variable

Due to issues with CSRF and port mapping, should you require to alter the port for the web UI you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.

For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090

TORRENTING_PORT

A bittorrent client can be an active or a passive node. Running your client as an active node has the advantage of being able to connect to both active and passive peers, and can potentially increase the number of incoming connections. This requires an open port on the host machine which might differ from container's internal one.

Similarly to the WEBUI_PORT, to set the port to 6887 you need to pass -p 6887:6887, -p 6887:6887/udp and -e TORRENTING_PORT=6887 arguments to Docker.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

docker-compose (recommended, click here for more info)

---
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - /path/to/qbittorrent/appdata:/config
      - /path/to/downloads:/downloads
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped
docker run -d \
  --name=qbittorrent \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e WEBUI_PORT=8080 \
  -e TORRENTING_PORT=6881 \
  -p 8080:8080 \
  -p 6881:6881 \
  -p 6881:6881/udp \
  -v /path/to/qbittorrent/appdata:/config \
  -v /path/to/downloads:/downloads \
  --restart unless-stopped \
  lscr.io/linuxserver/qbittorrent:latest

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 8080 WebUI
-p 6881 tcp connection port
-p 6881/udp udp connection port
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e TZ=Etc/UTC specify a timezone to use, see this list.
-e WEBUI_PORT=8080 for changing the port of the web UI, see below for explanation
-e TORRENTING_PORT=6881 for changing the port of tcp/udp connection, see below for explanation
-v /config Contains all relevant configuration files.
-v /downloads Location of downloads on disk.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

  • Shell access whilst the container is running:

    docker exec -it qbittorrent /bin/bash
  • To monitor the logs of the container in realtime:

    docker logs -f qbittorrent
  • Container version number:

    docker inspect -f '{{ index .Config.Labels "build_version" }}' qbittorrent
  • Image version number:

    docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/qbittorrent:latest

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose

  • Update images:

    • All images:

      docker-compose pull
    • Single image:

      docker-compose pull qbittorrent
  • Update containers:

    • All containers:

      docker-compose up -d
    • Single container:

      docker-compose up -d qbittorrent
  • You can also remove the old dangling images:

    docker image prune

Via Docker Run

  • Update the image:

    docker pull lscr.io/linuxserver/qbittorrent:latest
  • Stop the running container:

    docker stop qbittorrent
  • Delete the container:

    docker rm qbittorrent
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)

  • You can also remove the old dangling images:

    docker image prune

Image Update Notifications - Diun (Docker Image Update Notifier)

tip: We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-qbittorrent.git
cd docker-qbittorrent
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/qbittorrent:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 25.05.24: - Remove qbittorrent-cli as it still requires openssl 1.1 which is EOL.
  • 14.02.24: - Only set/override torrenting port if the optional env var is set.
  • 14.02.24: - Add torrenting port support.
  • 31.01.24: - Remove obsolete compat packages.
  • 25.12.23: - Only pull stable releases of qbittorrent-cli.
  • 07.10.23: - Install unrar from linuxserver repo.
  • 10.08.23: - Bump unrar to 6.2.10.
  • 17.06.23: - Deprecate armhf as per https://www.linuxserver.io/armhf.
  • 10.06.23: - Bump unrar to 6.2.8.
  • 23.02.23: - Add qt6-qtbase-sqlite to support SQLite database for resume files.
  • 29.11.22: - Add openssl1.1-compat for qbittorrent-cli.
  • 31.10.22: - Add libtorrentv1 branch.
  • 31.08.22: - Rebase to Alpine Edge again to follow latest releases.
  • 12.08.22: - Bump unrar to 6.1.7.
  • 16.06.22: - Rebase to Alpine 3.16 from edge.
  • 25.05.22: - Fetch qbitorrent-cli from upstream repo.
  • 02.03.22: - Add unrar, 7zip, and qbitorrent-cli.
  • 01.03.22: - Add python for search plugin support.
  • 23.02.22: - Rebase to Alpine Edge, install from Alpine repos.
  • 19.02.22: - Add jq to build-stage
  • 07.01.22: - Rebase to Alpine, build from source.
  • 06.01.22: - Deprecate unstable branch.
  • 10.02.21: - Rebase to focal.
  • 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
  • 12.11.20: - Stop creating /config/data directory on startup
  • 03.04.20: - Fix adding search engine plugin
  • 02.08.19: - Add qbitorrent-cli for processing scripts.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 14.01.19: - Rebase to Ubuntu, add multi arch and pipeline logic.
  • 25.09.18: - Use buildstage type build, bump qbitorrent to 4.1.3.
  • 14.08.18: - Rebase to alpine 3.8, bump libtorrent to 1.1.9 and qbitorrent to 4.1.2.
  • 08.06.18: - Bump qbitorrent to 4.1.1.
  • 26.04.18: - Bump libtorrent to 1.1.7.
  • 02.03.18: - Bump qbitorrent to 4.0.4 and libtorrent to 1.1.6.
  • 02.01.18: - Deprecate cpu_core routine lack of scaling.
  • 19.12.17: - Update to v4.0.3.
  • 09.02.17: - Rebase to alpine 3.7
  • 01.12.17: - Update to v4.0.2.
  • 27.11.17: - Update to v4 and use cpu_core routine to speed up builds.
  • 16.09.17: - Bump to 3.3.16, Add WEBUI_PORT variable and notes to README to allow changing port of webui.
  • 01.08.17: - Initial Release.
  • 12.02.18: - Initial Release.

docker-qbittorrent's People

Contributors

aptalca avatar chbmb avatar drizuid avatar j0nnymoe avatar linuxserver-ci avatar mynameisbogdan avatar nemchik avatar ngosang avatar owkkuri avatar pcdevil avatar pl77 avatar rchenzheng avatar rootforbid avatar roxedus avatar sigismund avatar sintan1729 avatar sparklyballs avatar thelamer avatar thespad avatar tobbenb avatar zaggash avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-qbittorrent's Issues

Slow speeds after updating to latest docker image

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

Total download speed should only be limited by the ISP speed.

Current Behavior

I am on a fiber connection
image

image

Sometimes it even looks like that
image

But most of the time this is what i am getting (after the latest update)
image

These are my settings
image

Steps to Reproduce

  1. Install QBittorrent latest image (from 26 or 27 of august from Docker Hub)
  2. Start the container and go into GUI
  3. Add torrent
  4. Watch it having multiple seeds (i have a torrent with 600+ seeds but still speed never goes above 500kb/s) and almost no speed

Environment

OS: Unraid 6.8.3
CPU architecture: x86_64/arm32/arm64 amd64
How docker service was installed: Unraid out-of-the-box installation of Docker

Command used to create docker container (run/create/compose/screenshot)

QBittorrent image from Apps section of Community Applications, just simple "image pull > start container" with default config

Docker logs

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    99
User gid:    100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Connection error while using SOCKS5 proxy in QBittorent and using research plugins

linuxserver.io

Hello, I use a connection proxy of type SOCKS5 in QBittorent. However, I get a connection error when I try to do a research on Jackett v0.16. It works without using the connection proxy on QBittorent.

The server proxy works well for the download/upload inside QBittorent and the research in Jackett works well without the proxy.

I launch QBittorent and Jackett thanks to a docker-compose file.

I have tried to add RUN_OPTS=-chttpclient2 option as mentionned in issue : Jackett/Jackett#4862 but it is just an option for SOCKS5 proxy inside jacket and using SOCKS5 proxy inside Jackett works correctly.

Edit : No one of other research plugins is working with the SOCKS5 proxy on QBittorent. They work only without the proxy.


Expected Behavior

The results of the research should appear in the list

Current Behavior

error message : "Jackett connection error! Click 'Go to description button to open help. Configuration file: ..."

Steps to Reproduce

1/ There is my docker-compose.yml

version: "2.2"

services:

  jackett:
    image: linuxserver/jackett
    container_name: jackett
    environment:
      - PUID=1024
      - PGID=100
      - TZ=Europe/Paris
      - RUN_OPTS=-chttpclient2
    volumes:
      - "./jackett/config:/config"
      - "./downloads:/downloads"
    ports:
      - 9117:9117
    restart: unless-stopped
    networks:
      - torrent

  qbittorrent:
    image: linuxserver/qbittorrent
    container_name: qbittorrent
    environment:
      - PUID=1024
      - PGID=100
      - TZ=Europe/Paris
      - UMASK_SET=022
      - WEBUI_PORT=8081
    volumes:
      - "./qbittorent/config:/config"
      - "./downloads:/downloads"
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 8081:8081
    restart: unless-stopped
    networks:
      - torrent

networks:
  torrent:

2/ Configure connection with Jackett, add indexes and test research on Jackett.
3/ Configure the QBittorrent connection on SOCKS5 proxy with a vpn server.
4/ Test the download with new IP.
5/ Try the research on Jackett and get the resulting "Jackett connection error! Click 'Go to description button to open help. Configuration file: ..."

Environment

OS: Ubuntu 18.04
CPU architecture: amd64

Docker logs

No logs from jackett docker
No logs from qBitorrent docker

Thank you for your help

Unable to connect to Jackett via UI

linuxserver.io

Hello, I'm actualy unable to connect docker-qbittorrent to Jackett.

I tried first with official qbittorrent client and it worked but it doesn't with docker-qbittorrent. "Jackett" is launched (https://hub.docker.com/r/linuxserver/jackett/) with default configurations on localhost (https://github.com/Jackett/Jackett).


Expected Behavior

The results of the research should appear in the list

Current Behavior

error message : "Jackett connection error! Click 'Go to description button to open help. Configuration file: ..."

Steps to Reproduce

  1. Launch jackett with default configurations via docker-compose (https://hub.docker.com/r/linuxserver/jackett/), add some random indexers, and ensure that it works with manual research.
  2. Launch officiel qbitorrent client, add default plugin and check that connection works well for Jackett.
  3. Now try with docker-qbittorrent by creating docker-compose.yml file and insert this code inside. Replace [my_path] and following path by the location of your own folders.
version: "2.1"
services:
  qbittorrent:
    image: linuxserver/qbittorrent
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - UMASK_SET=022
      - WEBUI_PORT=8080
    volumes:
      - [my_path]/qbittorent/config:/config
      - [my_path]/qbittorent/downloads:/downloads
      - [my_path]/qbittorent/data-qBittorrent:/config/data/qBittorrent
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 8080:8080
    restart: unless-stopped

  1. docker-compose up, the app is launched.
  2. A volume is created on data/qBittorent, get the "API key" displayed in Jackett (http://localhost:9117/UI/Dashboard) and insert it inside your config file thanks to the volume data-qBittorrent ([my_path]/qbittorent/data-qBittorrent/nova3/engines/jackett.json
{
    "api_key": "nrroibkuhiy3rfs7oz8bkp33740d0day",
    "tracker_first": false,
    "url": "http://127.0.0.1:9117"
}

  1. Try to do a research on plugin Jackett via docker-qbittorrent and get the resulting "Jackett connection error! Click 'Go to description button to open help. Configuration file: ..."

Environment

OS: Ubuntu 18.04
CPU architecture: amd64

Docker logs

No logs from jackett
No logs from qBitorrent

Thank you for your help

Rclone Support

##Feature Request

--> The Downloaded files from Qbittorrent will be cloned into the Rclone Remote as soon as the download Stopped

qBittorrent folder structure has changed in v4.3.0+

Explanation

In qBittorrent v4.2.5 and earlier, the application's data was saved in /config/data/qBittorrent and /config/qBittorrent. This changed with the release of v4.3.0. All application data is now saved in /config/qBittorrent and the old folder structure, while it still works, has been deprecated, with a warning being printed if it is detected at startup.

I think it's the job of qBittorrent itself to migrate the application data from the legacy directory to the new directory if or when support for the legacy folder structure is removed in a future version, but this issue isn't about that. This issue is about the linuxserver.io image unconditionally creating the /config/data directory at startup even when one is using qBittorrent v4.3.0 or later, where this folder remains unused and empty.

I'll be opening a pull request to fix this issue shortly.

Steps to Reproduce

  1. Install qBittorrent using the linuxserver.io container image for v4.3.0 or later.
  2. Observe the /config/data directory being created on container startup even though these qBittorrent versions don't use it.

Environment

OS: Debian 10
CPU architecture: x86_64
How docker service was installed: From the official Docker repository

Feature request: environment variable for "port used for incoming connections"

It would be cool if there was an env variable like "INCOMING_PORT" or something that set "port used for incoming connections" in the config as well as set which ports were exposed.

I'm using another container for a VPN that requests a forwarded port and stores that port in text file. Setting the environment variable with -e FILE__INCOMING_PORT=/vpn/forwarded_port would be awesome!

Thanks for the hard work!

exec format error

Trying to run this on unRAID 6.3.5 (Linux 4.9.30-unRAID x86_64) using the settings

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="qbittorrent" --net="bridge" -e TZ="Australia/Brisbane" -e HOST_OS="unRAID" -p 10001:6881/tcp -p 10001:6881/udp -p 10000:8080/tcp -v "/mnt/user/appdata/q":"/config":rw -v "/mnt/user/Warez/Downloads/":"/downloads":rw lsioarmhf/qbittorrent

and getting

panic: standard_init_linux.go:175: exec user process caused "exec format error" [recovered]

panic: standard_init_linux.go:175: exec user process caused "exec format error"


goroutine 1 [running, locked to thread]:
panic(0x6ee920, 0xc420128620)
/usr/lib64/go1.7.1/go/src/runtime/panic.go:500 +0x1a1
github.com/urfave/cli.HandleAction.func1(0xc42009b750)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/urfave/cli/app.go:478 +0x247
panic(0x6ee920, 0xc420128620)
/usr/lib64/go1.7.1/go/src/runtime/panic.go:458 +0x243
github.com/opencontainers/runc/libcontainer.(*LinuxFactory).StartInitialization.func1(0xc42009b1a0, 0xc420022048, 0xc42009b240)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/opencontainers/runc/libcontainer/factory_linux.go:259 +0x18f
github.com/opencontainers/runc/libcontainer.(*LinuxFactory).StartInitialization(0xc4200bc320, 0xaa19a0, 0xc420128620)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/opencontainers/runc/libcontainer/factory_linux.go:277 +0x353
main.glob..func8(0xc42009ea00, 0x0, 0x0)
/tmp/SBo/runc-1.0.0-rc2/main_unix.go:26 +0x66
reflect.Value.call(0x6d97c0, 0x764dc8, 0x13, 0x73787b, 0x4, 0xc42009b710, 0x1, 0x1, 0x4d0928, 0x72d6e0, ...)
/usr/lib64/go1.7.1/go/src/reflect/value.go:434 +0x5c8
reflect.Value.Call(0x6d97c0, 0x764dc8, 0x13, 0xc42009b710, 0x1, 0x1, 0x0, 0xc42009b6f0, 0x4d9906)
/usr/lib64/go1.7.1/go/src/reflect/value.go:302 +0xa4
github.com/urfave/cli.HandleAction(0x6d97c0, 0x764dc8, 0xc42009ea00, 0x0, 0x0)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/urfave/cli/app.go:487 +0x1e0
github.com/urfave/cli.Command.Run(0x737a4b, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x748eb7, 0x51, 0x0, ...)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/urfave/cli/command.go:191 +0xc3b
github.com/urfave/cli.(*App).Run(0xc4200ca000, 0xc420076060, 0x2, 0x2, 0x0, 0x0)
/tmp/SBo/runc-1.0.0-rc2/Godeps/_workspace/src/github.com/urfave/cli/app.go:240 +0x611
main.main()
/tmp/SBo/runc-1.0.0-rc2/main.go:132 +0xb65

Docker version of unraid appears to be
Docker version 1.12.6, build 6b644ec

any ideas?

Could not parse Nova search engine capabilities

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.

Search engine plugins are not being added/installed

Expected Behavior

Search engine plugins should be installed

Current Behavior

Web UI does not do anything when installing a search plugin

Steps to Reproduce

  1. docker-compose up
  2. login to webui localhost:8080
  3. add a search plugin

Environment

OS: MAC Catalina 10.15.4
CPU architecture: x86_64
How docker service was installed:
brew installation

Command used to create docker container (run/create/compose/screenshot)

$ docker-compose up

---
# docker-compose.yml
version: "3"
services:
  qbittorrent:
    image: linuxserver/qbittorrent
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Toronto
      - UMASK_SET=022
      - WEBUI_PORT=8080
    volumes:
      - /Users/rchenzheng/test/qbittorrent/config:/config
      - /Users/rchenzheng/test/downloads:/downloads
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 8080:8080
    restart: unless-stopped

Docker logs

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Could not parse Nova search engine capabilities, msg:
Error:  Traceback (most recent call last):
  File "/config/data/qBittorrent/nova3/nova2.py", line 36, in <module>
    import urllib.parse
ImportError: No module named parse

Ability to add packages

It would be cool if there is a variable where we could provide addtional packages to be installed during the build.

One of the common use cases would be to run unrar on torrent completion, this does also require the multiverse repository to be enabled as well.

I lost my webui password

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

I forget my webui password, how can I find or reset the password?

Current Behavior

Steps to Reproduce

Environment

**OS:Ubuntu 18.04 LTS
CPU architecture: x86_64
How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

Docker logs

Upload rate limit setting ignored

Since updating to the latest version, my upload rate limit is being ignored. Download limit is still respected. Haven't changed any settings.

Moving files slow

With docker using native paths, if I move torrent from /mnthdd/shows to /mnt/movies it is instant. When I mapped that paths to /shows and /movies and then move from /shows to /movies it is super slow, like 10 or 20 MBPs.

Category Folders Do Not Work & Monitor Folder Configs Do Not Save

Hey Guys -

I installed the latest build of qBittorrent's Docker container this morning for the first time as I'm considering switching from Deluge which I run on Windows. Everything is going great except for one thing.

Seemingly, I cannot save configurations in qBittorrent for Monitoring folders. Also, when creating Categories with a save path do save, but once the download completes, the completed download is moved to the default download location - not the one for the category it was assigned.

At first I thought it was an issue with the subfolders of mounted volumes as it was saving downloads to the root of the mounted volume (/downloads) -however - when reviewing logs, I saw that it was correctly saving the downloads into the subfolder /downloads/incomplete as configured then moving to the default path once finished.

Below is the string I used to install the container:

docker run -d
--name=qBittorrent
-v /var/roothome/qbtorrent:/config:z
-v /var/home/user/downloads:/downloads:z
-e PGID=0 -e PUID=0
-e UMASK_SET=022
-e WEBUI_PORT=8484
-e TZ=America/Chicago
-p 6881:6881
-p 6881:6881/udp
-p 8484:8484
linuxserver/qbittorrent

I must add ":z" to end of mounting strings since using Atomic which uses SysLinux and provides full access to the path

As you can see above, I mounted the host folder "/var/home/user/downloads" to the container's folder "/downloads". The host folder already contained many other folders as well - each set to 0777 recursively and successfully used by other containers in the past. I know the paths I am entering exist as well as I can copy/paste them into an SSH session connected to the container to cd to them.

Connecting to the container, I had cd to /downloads where I can view and seemingly have full access to all of the folders I should see including ones like "/downloads/complete/", "/downloads/autoadd/", etc. I opened qBittorrent's config files in a text editor to see if I could manually make the changes, but do not see where these settings would be/are saved (in plain text at least.)

Monitor Folders
Below are a examples for how I've tried to configure a couple of the Monitor Folders which do not save. The paths already exist.

  • Source 1: /downloads/autoadd/qbittorrent/complete/
  • Other (Save Location) 1: /downloads/complete/
  • Source 2: /downloads/autoadd/qbittorrent/isos/
  • Other (Save Location) 2: /downloads/isos/

Category Folders
Similar to Monitor Folders but more important to me as the Category folders. I am able to enter paths into them which save and able to assign a category to a torrent. However, once the torrent completes, it saves into the default download folder instead of the one defined for the category. Below are exmaples of paths I'm using:

  • Default Download Path: /downloads/
  • Path for Category "complete": /downloads/complete/
  • Path for Category "isos": /downloads/isos/
    I also tried removing the trailing slash which didn't help...

I examined qbittorrent.log after another failed test where it was not saved in a category's save path. The only things it mentioned were adding a number of trackers to the torrent, successfully moving the torrent from my incomplete folder to the default download folder, then when it reached the max ratio for seeding.

The container is installed on my host running Atomic Fedora 29. It is one of over 20 containers which do not have similar issues.

Any suggestions? Thank You!

Feature request: add in qbittorrent-cli for post download processing

Please include https://github.com/fedarovich/qbittorrent-cli for those of us that use qbittorrent with things like radarr, sonarr etc. Using labels and the use of post download scripts we (at least myself) would like to do things such as use the qbittorrent-cli to do things such as once a download is finished and is hardlinked or copied over to our plex server there is a need to clean up such as deleting the torrent. Having the qbittorrent-cli would make this process much easier.

I see that the qbittorrent-cli project uses dot-net which can be a very bulky install (especially to build). I am actually looking into using your docker image as well as another to do a multistage docker build so that I can just copy the resulting binary needed over.
https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds

linuxserver.io

Thanks, team linuxserver.io

I also would like to take this time to thank you for your work.

WebUI Display Error in chrome/chromium Edge

version v4.2.5
Windows 10 1909 Home

Update 21:11 Beijing June 14

I found the reason for the error now. Open the webui in chrome at 100% zoom. Drag to change the proportion of the left side bar and the main interface, the main interface has a great chance of turning into a white screen. At this time, stop dragging, and the main interface will remain white.

This is most likely due to a problem with page refresh. Curiously, when the zoom ratio is not 100%, the chance of the main interface becoming a white screen is much smaller.

In fact, I don't mind if the main interface turns white when it turns to drag, but when the drag is over, the main interface should return to normal. I suggest adding the operation of refreshing the main interface at the end of dragging.

I also attached the video.
qBittorrent v4.zip

拖动改变左侧边栏和主界面的比例的时候,主界面有很大几率会变成白屏。此时停止拖动,主界面就会保持白屏。
这很有可能是因为页面刷新出现的问题。奇怪的是,当缩放比例不是100%的时候,主界面变成白屏的几率会小很多。
实际上变成拖动的时候主界面变成白屏我并不介意,但是当拖动结束时,主界面应该恢复正常。我建议在拖动结束时增加刷新主界面的操作。

=====================================================
I install the docker in qnap container station, but when I open the webui in Chrome/Chromium Edge, the task list cannot display normally. In the sidebar, the number of tasks is normal, and the task classification is also normal. However, tasks are not displayed in the main interface.

But when I use chrome in Ubuntu 20.04LTS Home to open the WebUI, it displays normally. And when I open it on my phone/or in my Windows laptop but use wechat to open, it displays normally, too.

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

Web UI display normally.

Current Behavior

When I open the webui in Chrome/Chromium Edge, the task list cannot display normally. In the sidebar, the number of tasks is normal, and the task classification is also normal. However, tasks are not displayed in the main interface.

Environment

OS: Win 10 1909 Home
CPU architecture: x86_64
How docker service was installed: Pull the docker in docker hub

Jackett is not working

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

When going into http://:9117/UI/Dashboard jackett should open. But I get a connection refused error. I am using portainer and the port 9117 has been mapped. the qBittorrent is working fine

Steps to Reproduce

  1. Install using portainer with this docker image and follow the steps.

Environment

OS: Proxmox latets
CPU architecture: arm64
How docker service was installed: Using portainer

Command used to create docker container (run/create/compose/screenshot)

Docker logs

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[s6-init] ensuring user provided files have correct perms...exited 0.

[fix-attrs.d] applying ownership & permissions fixes...

[fix-attrs.d] done.

[cont-init.d] executing container initialization scripts...

[cont-init.d] 01-envfile: executing...

[cont-init.d] 01-envfile: exited 0.

[cont-init.d] 10-adduser: executing...


      _         ()


     | |  ___   _    __


     | | / __| | |  /  \ 


     | | \__ \ | | | () |


     |_| |___/ |_|  \__/

Brought to you by linuxserver.io


To support LSIO projects visit:

https://www.linuxserver.io/donate/


GID/UID


User uid: 0

User gid: 0


[cont-init.d] 10-adduser: exited 0.

[cont-init.d] 30-config: executing...

[cont-init.d] 30-config: exited 0.

[cont-init.d] 99-custom-scripts: executing...

[custom-init] no custom files found exiting...

[cont-init.d] 99-custom-scripts: exited 0.

[cont-init.d] done.

[services.d] starting services

[services.d] done.

Everything seems fine with the docker installation.

Thanks in advance for the help.
Jackett: api key error! Right-click this row and select 'Open description page' to open help. Configuration file: '/config/data/qBittorrent/nova3/engines/jackett.json'

the file is created

Not Moving to Category Upon Completion

I have torrents being snatched under specific categories but upon completion they are not being moved to the categories directory. From what I have read there should be an option under...

"options > Downloads. For "Default Torrent Management Mode" choose "Automatic" AND click "Use Subcategories" AND for "Default Save Path" write in the path of your all_inbox_links (or whatever you have called it) directory."

I am not seeing this option, but it's available per torrent under it's right click menu. qBittorrent v4.0.3 Web UI.
Thanks.

UMASK_SET - subfolders

Current Behavior

version: version-14.3.0.99202010231047-7094-260e48b70ubuntu18.04.1

If I change the UMASK_SET=007 the RW - group is not propagateing to subfolders.
Ex: /my_software - dir and files in it has RW access but
/my_software/old - dir and files in it has just R access.
Is this good ?

All the child directorys and files has that permission as the root dir has.

New API breaks Sonarr and radarr

With the new 4.2.0 version a new API has been introduced that many applications has yet adopt so communication between qbittorrent and Sonarr/Radarr doesn't work.

I think the best is to have a new branch/tag with the previous version (clear tag) for all these that doesn't work to upgrade (my case was accidental upgrade of the container).

Cannot use "--net=container" option, "Error response from daemon: conflicting options"

Super new to docker, but long story short:

I can run the default set of commands and get Qbit up and running just fine. However, adding --net=container:vpn throws the error

Error response from daemon: conflicting options: port publishing and the container type network mode

I am using Docker for Windows. Here is my command:

docker create --net=container:vpn 

--name=qbittorrent 

-e PUID=1000 

-e PGID=1000 

-e TZ=America/Los_Angeles 

-e UMASK_SET=022 

-e WEBUI_PORT=8080

-p 6881:6881 

-p 6881:6881/udp 

-p 8080:8080 

-v C:\DockerStuff\Qbit_Plain:/config 

-v B:\Download:/downloads 

--restart unless-stopped 

linuxserver/qbittorrent

ver4.15 port forwarding failed, I don't know why

I can use curl in the container's bash to get the result.

But outside is not accessible, I have done port forwarding.

image

image

image

Other containers don't have this problem

log

******** Information ********
To control qBittorrent, access the Web UI at http://localhost:8080
The Web UI administrator user name is: admin
The Web UI administrator password is still the default one: adminadmin
This is a security risk, please consider changing your password from program preferences.
Catching signal: SIGTERM
Exiting cleanly
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Unable to connect to seeds/peers

I'm running linuxserver/qbittorrent (latest) and see my container launch as expected. However, none of my torrents are able to connect to any seeds or peers.

I'm launching the container as follows:

 docker run --rm --name qb_test -p 8080:8080 -e TZ="America/New_York" -p 6882:6882 -p 6882:6882/udp  linuxserver/qbittorrent

I've also created the appropriate port forwarding mappings in my router to allow port 6882 from the internet to my docker host port 6882. I have futher tested the mapping using telnet from a public IP to ensure that I am able to connect qbittorrent in the container; the telnet connection gets established.

At this point, I'm not sure where I have to go track down this issue. Is this a problem with the container? with my docker host configuration? Something completely different?

Docker Engine:
CentOS Linux release 7.5.1804 (Core)
Docker version 18.06.1-ce, build e68fc7a

I have nothing specific in the logs showing up either:

[eric@localhost ~]$  docker run --name qb_test -p 8080:8080 -e TZ="America/New_York" -p 6882:6882 -p 6882:6882/udp  linuxserver/qbittorrent
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

******** Information ********
To control qBittorrent, access the Web UI at http://localhost:8080
The Web UI administrator user name is: admin

Any suggestions what I can do to validate if it is the container, my host, or just some silly missing configuration? If I install qbittorrent-nox on the host directly, then my seeds connect fine.

downloading speed is zero

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

Current Behavior

after add magnet link, the speed is always 0. qbittorent can find peers ,and the "Tracker status" is working ,But the download speed is always 0. )..(

Steps to Reproduce

Environment

OS:
CPU architecture: x86_64/arm32/arm64
How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

Docker logs

Username and password authentication broken

linuxserver.io

I can't log into qbittorrent, so I reset the password by deleting 2 lines in config/qBittorrent/qBittorrent.conf and managed to log in with default admin password. I changed the password again in the web ui, and it was working for a week and now I can't login again. I have sonarr, radarr, nzb360 accessing qbittorrent and they suddenly reporting to lost connection to qbittorrent.


Expected Behavior

Current Behavior

Steps to Reproduce

Environment

OS:
CPU architecture: x86_64/arm32/arm64
How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

Docker logs

Feature Request: RSS feed support

Is there a way to add RSS feed support from the original Qbittorrent project? Need the feature for automated download on Asustor NAS. Thanks in advance!

Disabling Login

Is there a way to disable the login page when on a local network?

Thank you

chown on Container Startup Hangs

The container is not necessarily going to have the ability or permissions to change ownership of the /downloads directory. This causes the container to hang.


Expected Behavior

qBitorrent should start

Current Behavior

/var/run/s6/etc/cont-init.d/30-config:

# chown download directory if currently set to root
if [[ "$(stat -c '%U' /downloads)" != "abc" ]]; then
       chown -R abc:abc /downloads
fi

Steps to Reproduce

  1. Start the container down a /downloads directory with no permission to change or a filesystem that doesn't support ownership

Environment

OS: Unraid
CPU architecture: x86_64
How docker service was installed: Unraid

Command used to create docker container (run/create/compose/screenshot)

Unraid

Docker logs

Feature request: python 3 instead of python 2

Is it possible to install the 'python3' package instead of 'python'(which actually points to python 2) in the Dockerfile? I would like to run a python script as a post-completion command and it'd be nice to be able to use python 3 to write this with. https://github.com/qbittorrent/qBittorrent/blob/master/INSTALL says that python3 (>= 3.3) is supported, although I haven't tried building a container from a modified Dockerfile to verify that it would actually work yet.

QBittorrent stuck at downloading metadata

Hey,

When adding new magnet torrents via webui they get stuck in "downloading metadata".. Sometimes they eventually recovers.. in minutes , hours or days. However sometimes they don't.
Thought it could be my local DNS resolution server on host, but no. Logs don't say much as well.
Anyway port 6881 is allowed on host.

BTW on the same LAN using qb on win and no issues whatsoever.. same magnet starts immediately at full speed.

Host: Debian Buster
Image: latest

Docker-Compose:

version: "3.7"

services:
  qbittorrent:
    image: linuxserver/qbittorrent
    container_name: qbittorrent.528
    restart: always
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 52880:52880
    volumes:
      - $PWD/config:/config
      - /lvm/raid/private/media/.downloads:/downloads
    environment:
      - TZ=Europe/Prague
      - PUID=1000
      - PGID=994
      - UMASK_SET=022
      - WEBUI_PORT=52880
    labels:
      - traefik.enable=true
      - traefik.port=52880
      - traefik.frontend.entryPoints=https
      - traefik.frontend.rule=Host:qb.example.com
      - traefik.backend=qbittorrent.528
      - traefik.frontend.headers.forceSTSHeader=true
      - traefik.frontend.headers.STSSeconds=315360000
      - traefik.frontend.headers.STSIncludeSubdomains=true
      - traefik.frontend.headers.STSPreload=true

networks:
  default:
    name: qbittorrent.528

However googling around found this issue: qbittorrent/qBittorrent#5006 (comment) and it seems to be the case.
Another reddit thread: https://www.reddit.com/r/qBittorrent/comments/7x03yk/stuck_on_downloading_metadata_on_one_pc/
And from linustechtips forum:
image

So just by changing the port it starts immediately working again. They say this needs to be done on every startup..

Any ides how to address this for the future? Thanks

Cannot use WebUI only in Chrome.

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.

Cannot use WebUI in Chrome.

Current Behavior

Chrome returns HTTP ERROR 401, but it's fine in Safari.

Steps to Reproduce

  1. All the settings are default settings
  2. Open the WebUI in chrome

Environment

OS: unraid 6.8.1
CPU architecture: x86_64
How docker service was installed: unraid default

Command used to create docker container (run/create/compose/screenshot)

unraid default

Docker logs

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...


      _         ()
     | |  ___   _    __
     | | / __| | |  /  \ 
     | | \__ \ | | | () |
     |_| |___/ |_|  \__/

Brought to you by linuxserver.io

To support LSIO projects visit:
https://www.linuxserver.io/donate/

GID/UID

User uid: 99
User gid: 100

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Add unrar for automatic extraction upon torrent completion

Could unrar be added to the list of runtime packages so we can configure the external program execution to unpack torrents for radarr and sonarr? I've pulled and built my own docker based on yours but it would be nice if it was included. Thanks!

FYI, I'm using the following syntax.
/usr/bin/unrar x -r "%F/." "%F/"

Segfaulting as of last push

linuxserver.io

Host OS: Synology DSM 6.2-23739

Docker constantly segfaults, will present login screen momentarily but fails.

Error:
root@linuxserver-qbittorrent1:/$ dmesg
[3703803.235974] qbittorrent-nox[7998]: segfault at 7fc7584c4000 ip 00007fc7575c38ca sp 00007fc7584c06c0
error 6 in libtorrent-rasterbar.so.9.0.0[7fc757374000+5e0000]
[3703806.211666] qbittorrent-nox[8041]: segfault at 7ff6977ad000 ip 00007ff6968ac8ca sp 00007ff6977a96c0
error 6 in libtorrent-rasterbar.so.9.0.0[7ff69665d000+5e0000]
[3703808.877900] docker0: port 2(docker5b67ed9) entered forwarding state
[3703809.140893] qbittorrent-nox[8090]: segfault at 7f0ad1d91000 ip 00007f0ad0e908ca sp 00007f0ad1d8d6c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f0ad0c41000+5e0000]
[3703813.618495] qbittorrent-nox[8116]: segfault at 7f64b1fc9000 ip 00007f64b10c88ca sp 00007f64b1fc56c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f64b0e79000+5e0000]
[3703816.554403] qbittorrent-nox[8154]: segfault at 7f7d96e3a000 ip 00007f7d95f398ca sp 00007f7d96e366c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f7d95cea000+5e0000]
[3703819.501990] qbittorrent-nox[8205]: segfault at 7f1ffe960000 ip 00007f1ffda5f8ca sp 00007f1ffe95c6c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f1ffd810000+5e0000]
[3703822.441683] qbittorrent-nox[8238]: segfault at 7fe1775f0000 ip 00007fe1766ef8ca sp 00007fe1775ec6c0
error 6 in libtorrent-rasterbar.so.9.0.0[7fe1764a0000+5e0000]
[3703825.333638] qbittorrent-nox[8261]: segfault at 7fe1963a5000 ip 00007fe1954a48ca sp 00007fe1963a16c0
error 6 in libtorrent-rasterbar.so.9.0.0[7fe195255000+5e0000]
[3703828.260455] qbittorrent-nox[8294]: segfault at 7f340faf8000 ip 00007f340ebf78ca sp 00007f340faf46c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f340e9a8000+5e0000]
[3703831.166156] qbittorrent-nox[8316]: segfault at 7f543ae4b000 ip 00007f5439f4a8ca sp 00007f543ae476c0
error 6 in libtorrent-rasterbar.so.9.0.0[7f5439cfb000+5e0000]
[3703834.054371] qbittorrent-nox[8351]: segfault at 7ff2db84e000 ip 00007ff2da94d8ca sp 00007ff2db84a6c0
error 6 in libtorrent-rasterbar.so.9.0.0[7ff2da6fe000+5e0000]
[3703836.945012] qbittorrent-nox[8376]: segfault at 7fd02b9c7000 ip 00007fd02aac68ca sp 00007fd02b9c36c0
error 6 in libtorrent-rasterbar.so.9.0.0[7fd02a877000+5e0000]
[3703839.830493] qbittorrent-nox[8409]: segfault at 7fa4357b7000 ip 00007fa4348b68ca sp 00007fa4357b36c0
error 6 in libtorrent-rasterbar.so.9.0.0[7fa434667000+5e0000]

I have verified that WebUI settings are in place in config, a suggestion from google-fu and on the lsio-qbittorrent homepage:
WebUI\Address=*
WebUI\ServerDomains=*

This container worked perfectly prior to Friday's update.

The docker can't use IPV6

linuxserver.io

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.


Expected Behavior

Current Behavior

Steps to Reproduce

Environment

OS:
CPU architecture: x86_64/arm32/arm64
How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

Docker logs

https://github.com/qbittorrent/qBittorrent/pull/11592
https://github.com/qbittorrent/qBittorrent/issues/11561

Can't run wget in external script file

My file with script to run after torrent download:

#!/bin/bash

wget -q -O - --header 'Access-Token: o.yvNpDvj4TcOyhoMUTESGDSGmUKLHPCdJ3Q' --header="Content-Type: application/json" https://api.pushbullet.com/v2/pushes --post-data="{\"type\": \"note\", \"title\": \"Torrent is ready\", \"body\": \"QBittorent finished downloading: $1\"}" > /dev/null 2&>1

QBittorrent setting:

image

Error when script is called after torrent completed:

image

EDIT: After remove '> /dev/null 2&>1' script is working. Why?

Error 401 when used behind nginx reverse proxy

I have my docker containers run behind nginx reverse proxy. qbittorrent runs on default port 8080. nginx configured as follows:

server {
    listen 80;
    listen [::]:80;
    server_name torrents.lan;

    location / {
        proxy_buffering off;
        ;proxy_set_header Host 192.168.1.200:8080;  ; tried with and without.
        proxy_pass http://192.168.1.200:8080/;
    }
}

Loading WebUI fails to load images and css files with error 401. Attempt to log in also fails with error 401.

When loading WebUI directly everything works as expected.

Could this also be related to csrf "improvements"? I did not use qbittorrent container previously so i do not know if it used to work or not.

WebUI settings not persistent

After updating the container, or even after a day, the webui settings are reset. I'm not talking about the options like ports advanced options, those are persistent, but only for the interface, like view options, the different statistics like "uploaded, tracker, speed in titlebar, etc"

They need to be manually readded everytime. Is there a way to make them *stick?
Cheers

Radarr/Sonarr/Lidarr won't connect after recent upgrade

Hi,

After recent upgrade none of the Sonarr/Radarr/Lidarr will connect with your qbittorent container. I did no configuration changes just performed new docker image pull and it stopped working.

Error log from console:

sonarr | [v2.0.0.5344] NzbDrone.Core.Download.Clients.DownloadClientException: Failed to connect to qBittorrent, check your settings. ---> System.Net.WebException: Error: ConnectFailure (Connection timed out): 'https://192.168.255.11:52880/api/v2/app/webapiVersion' ---> System.Net.WebException: Error: ConnectFailure (Connection timed out) ---> System.Net.Sockets.SocketException: Connection timed out
sonarr |   at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x00014] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.Sockets.Socket.EndConnect (System.IAsyncResult asyncResult) [0x0002c] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.Sockets.SocketTaskExtensions+<>c.<ConnectAsync>b__2_1 (System.IAsyncResult asyncResult) [0x00006] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00019] in <254335e8c4aa42e3923a8ba0d5ce8650>:0
sonarr | --- End of stack trace from previous location where exception was thrown ---
plex.529.sonarr.82 |
sonarr |   at System.Net.WebConnection.Connect (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x0019b] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |    --- End of inner exception stack trace ---
sonarr |   at System.Net.WebConnection.Connect (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00217] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x000cc] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.WebOperation.Run () [0x0009a] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at System.Net.HttpWebRequest.GetResponse () [0x00016] in <91935ad653254a93b9d73a9f8f2f7a2d>:0
sonarr |   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0011b] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:82
sonarr |    --- End of inner exception stack trace ---
sonarr |   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x001ca] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:113
sonarr |   at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:35
sonarr |   at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x0007e] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:121
sonarr |   at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:57
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxyV2.IsApiSupported (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00019] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxyV2.cs:36
sonarr |    --- End of inner exception stack trace ---
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxyV2.IsApiSupported (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x0006b] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxyV2.cs:58
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxySelector.FetchProxy (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxySelector.cs:75
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxySelector+<>c__DisplayClass6_0.<GetProxy>b__0 () [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxySelector.cs:70
sonarr |   at NzbDrone.Common.Cache.Cached`1[T].Get (System.String key, System.Func`1[TResult] function, System.Nullable`1[T] lifeTime) [0x0006a] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Cache\Cached.cs:81
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxySelector.GetProxy (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings, System.Boolean force) [0x00049] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxySelector.cs:70
sonarr |   at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrent.TestConnection () [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrent.cs:227
plex.529.sonarr.82 |
sonarr | [Warn] NzbDroneErrorPipeline: Invalid request Validation failed:
sonarr |  -- Unknown exception: Failed to connect to qBittorrent, check your settings.

Credentials are correct and they work via webUI. I dont really understands why it times-out :/

WebUI is accessible as before. Just something wrong on the API level..

I wanted to try older version but was so confused with your tags. Please list in your image description how to rollback e.g. to 4.2.0 or 4.1.1 because your tags make no sense to me and I cannot see any correlation..

Thanks, Michal

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.