linuxserver-mod-vuetorrent icon indicating copy to clipboard operation
linuxserver-mod-vuetorrent copied to clipboard

Published 20 hours ago • verified publisher icon gabe565

Unacceptable file type, only regular file is allowed.

Open glanc opened this issue 1 year ago • 15 comments

Hello,

it seems that I cannot use anymore the vuetorrent ui, I get the error in the title. If I change the ui to nightwalker in qBittorent.conf in the docker volume, it works. I was using the vuetorrent ui until yesterday. After starting the docker, I cannot find the vuetorrent folder in the default config dir.

This is my docker:

qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent cap_add: - NET_ADMIN network_mode: service:gluetun depends_on: gluetun: condition: service_started environment: - PUID=1000 - PGID=1000 - TZ=Europe/Rome - WEBUI_PORT=9080 - DOCKER_MODS=ghcr.io/gabe565/linuxserver-mod-vuetorrent - LAN_NETWORK=192.168.111.0/24 volumes: - .qbit_config:/config - /mnt/data/torrents:/data/torrents restart: always labels: - autoheal=true # Required for willfarrell/docker-autoheal - com.centurylinklabs.watchtower.enable=true healthcheck: # Required for willfarrell/docker-autoheal test: curl --fail --ipv4 https://google.com || exit 1 interval: 60s timeout: 5s retries: 3

The logs:

(N) 2024-06-14T16:45:49 - qBittorrent v4.6.5 started (N) 2024-06-14T16:45:49 - Using config directory: /config/qBittorrent (N) 2024-06-14T16:45:49 - Trying to listen on the following list of IP addresses: "0.0.0.0:10154,[::]:10154" (I) 2024-06-14T16:45:49 - Peer ID: "-qB4650-" (I) 2024-06-14T16:45:49 - HTTP User-Agent: "qBittorrent/4.6.5" (I) 2024-06-14T16:45:49 - Distributed Hash Table (DHT) support: ON (I) 2024-06-14T16:45:49 - Local Peer Discovery support: ON (I) 2024-06-14T16:45:49 - Peer Exchange (PeX) support: ON (I) 2024-06-14T16:45:49 - Anonymous mode: ON (I) 2024-06-14T16:45:49 - Encryption support: ON (I) 2024-06-14T16:45:49 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/10154" (I) 2024-06-14T16:45:49 - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/10154" (I) 2024-06-14T16:45:49 - Successfully listening on IP. IP: "172.30.172.2". Port: "TCP/10154" (I) 2024-06-14T16:45:49 - Successfully listening on IP. IP: "172.30.172.2". Port: "UTP/10154" (I) 2024-06-14T16:45:49 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Sat Jun 1 02:35:40 2024. (N) 2024-06-14T16:45:49 - Using custom WebUI. Location: "/config/qBittorrent/vuetorrent". (W) 2024-06-14T16:45:49 - Couldn't load WebUI translation for selected locale (en). (N) 2024-06-14T16:45:49 - WebUI: Now listening on IP: *, port: 9080 (N) 2024-06-14T16:47:02 - WebAPI login success. IP: ::ffff:172.30.172.30 (N) 2024-06-14T16:47:03 - WebAPI login success. IP: ::ffff:172.30.172.20 (N) 2024-06-14T16:47:03 - WebAPI login success. IP: ::ffff:172.30.172.10

glanc avatar Jun 14 '24 14:06 glanc

I tried this one and the other one, both do it, And after reading through Google, this error plagues qbittorrent, and they never give a reason as to why it happens. They just say "disable Webui". Not a solution.

Aetherinox avatar Jun 15 '24 20:06 Aetherinox

I am able to replicate. Still figuring out what is triggering this so that I can implement a fix.

Related VueTorrent issue: https://github.com/VueTorrent/VueTorrent/issues/1736

gabe565 avatar Jun 17 '24 08:06 gabe565

After some troubleshooting, I think this is because the LinuxServer scripts think the mod has already been applied. If you check the Docker logs with docker compose logs qbittorrent, which of these do you see?

  1. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [mod-init] Installing gabe565/linuxserver-mod-vuetorrent
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent applied to container

  2. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent at 
sha256:e13dd95584b75b06ae8e3cf91ca7634056127423d4b2ddb09ac9aeefda02fea0 has been previously applied skipping

If your logs look like number 2 and you don't see the /vuetorrent dir inside the container, then I have two ideas that could solve this (see below). I'm not yet sure why the mod wasn't installed during the new version startup.

To fix, you can either remove the state file and restart:

  1. docker compose exec qbittorrent bash
  2. rm /gabe565.linuxserver-mod-vuetorrent.latest
  3. exit
  4. docker compose restart qbittorrent

Or you can recreate the container:

  1. docker compose rm --stop qbittorrent
  2. docker compose up -d

gabe565 avatar Jun 17 '24 08:06 gabe565

I have the manual version installed and just woke up. Give me about an hour to get my eyes open, and I'll remove the manual, reinstall yours, and check the logs and report back.

Appreciate it.

Aetherinox avatar Jun 17 '24 09:06 Aetherinox

Initial log:

qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [mod-init] Installing gabe565/linuxserver-mod-vuetorrent
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent applied to container

[[ logo, bunch of nonsense ]]

qbittorrent  | Linuxserver.io version: 4.6.5-r0-ls335
qbittorrent  | Build-date: 2024-06-12T20:12:36+00:00
qbittorrent  | ───────────────────────────────────────
qbittorrent  |     
qbittorrent  | [custom-init] No custom files found, skipping...
qbittorrent  | /usr/bin/with-contenv: line 6: umask: 18: octal number out of range
qbittorrent  | /usr/bin/with-contenv: line 6: umask: 18: octal number out of range
qbittorrent  | WebUI will be started shortly after internal preparations. Please wait...
qbittorrent  | 
qbittorrent  | ******** Information ********
qbittorrent  | To control qBittorrent, access the WebUI at: http://localhost:8880

Removing the file and doing a restart appears to work.

Aetherinox avatar Jun 17 '24 11:06 Aetherinox

After some troubleshooting, I think this is because the LinuxServer scripts think the mod has already been applied. If you check the Docker logs with docker compose logs qbittorrent, which of these do you see?

  1. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [mod-init] Installing gabe565/linuxserver-mod-vuetorrent
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent applied to container

  2. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent at 
sha256:e13dd95584b75b06ae8e3cf91ca7634056127423d4b2ddb09ac9aeefda02fea0 has been previously applied skipping

If your logs look like number 2 and you don't see the /vuetorrent dir inside the container, then I have two ideas that could solve this (see below). I'm not yet sure why the mod wasn't installed during the new version startup.

To fix, you can either remove the state file and restart:

  1. docker compose exec qbittorrent bash
  2. rm /gabe565.linuxserver-mod-vuetorrent.latest
  3. exit
  4. docker compose restart qbittorrent

Or you can recreate the container:

  1. docker compose rm --stop qbittorrent
  2. docker compose up -d

Done that, ans now I se this in the container log:

glanc avatar Jun 17 '24 12:06 glanc

After some troubleshooting, I think this is because the LinuxServer scripts think the mod has already been applied. If you check the Docker logs with docker compose logs qbittorrent, which of these do you see?

  1. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [mod-init] Installing gabe565/linuxserver-mod-vuetorrent
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent applied to container

  2. qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] gabe565/linuxserver-mod-vuetorrent at 
sha256:e13dd95584b75b06ae8e3cf91ca7634056127423d4b2ddb09ac9aeefda02fea0 has been previously applied skipping

If your logs look like number 2 and you don't see the /vuetorrent dir inside the container, then I have two ideas that could solve this (see below). I'm not yet sure why the mod wasn't installed during the new version startup. To fix, you can either remove the state file and restart:

  1. docker compose exec qbittorrent bash
  2. rm /gabe565.linuxserver-mod-vuetorrent.latest
  3. exit
  4. docker compose restart qbittorrent

Or you can recreate the container:

  1. docker compose rm --stop qbittorrent
  2. docker compose up -d

Done that, ans now I see this in the container log:

mod-init] Running Docker Modification Logic [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io [mod-init] Installing gabe565/linuxserver-mod-vuetorrent [mod-init] gabe565/linuxserver-mod-vuetorrent applied to container [migrations] started [migrations] no migrations found usermod: no changes

glanc avatar Jun 17 '24 12:06 glanc

My fault! The ui path was wrong in my qBittorent.conf!

glanc avatar Jun 17 '24 12:06 glanc

@glanc That makes sense! I wish qBittorrent served a more helpful error when that happened, and then fell back to serving the built-in web UI...

gabe565 avatar Jun 17 '24 20:06 gabe565

Removing the file and doing a restart appears to work.

It seemed like it would. I'll continue to see if I can fully replicate. Let me know if it happens again!

gabe565 avatar Jun 17 '24 20:06 gabe565

@daNutzzzzz Moving conversation from #56 to here. Are you still having this issue? If so, can you post your container logs?

gabe565 avatar Jul 23 '24 05:07 gabe565

@daNutzzzzz Moving conversation from #56 to here. Are you still having this issue? If so, can you post your container logs?

Hi, no, there was another QBT update and it worked again.

danutzzzzz avatar Jul 23 '24 14:07 danutzzzzz

@gabe565 Hi. I am getting the same issue after the jump to qBittorrent 5.0.1 to address CVE-2024-51774 but my logs are saying:

qbittorrent  | [mod-init] Running Docker Modification Logic
qbittorrent  | [mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
qbittorrent  | [mod-init] Downloading gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [mod-init] (ERROR) Invalid tarball, could not download gabe565/linuxserver-mod-vuetorrent from ghcr.io
qbittorrent  | [migrations] started
qbittorrent  | [migrations] no migrations found
qbittorrent  | usermod: no changes
qbittorrent  | ───────────────────────────────────────
qbittorrent  | 
qbittorrent  |       ██╗     ███████╗██╗ ██████╗
qbittorrent  |       ██║     ██╔════╝██║██╔═══██╗
qbittorrent  |       ██║     ███████╗██║██║   ██║
qbittorrent  |       ██║     ╚════██║██║██║   ██║
qbittorrent  |       ███████╗███████║██║╚██████╔╝
qbittorrent  |       ╚══════╝╚══════╝╚═╝ ╚═════╝
qbittorrent  | 
qbittorrent  |    Brought to you by linuxserver.io
qbittorrent  | ───────────────────────────────────────
qbittorrent  | 
qbittorrent  | To support LSIO projects visit:
qbittorrent  | https://www.linuxserver.io/donate/
qbittorrent  | 
qbittorrent  | ───────────────────────────────────────
qbittorrent  | GID/UID
qbittorrent  | ───────────────────────────────────────
qbittorrent  | 
qbittorrent  | User UID:    1000
qbittorrent  | User GID:    1000
qbittorrent  | ───────────────────────────────────────
qbittorrent  | Linuxserver.io version: 5.0.1-r0-ls362
qbittorrent  | Build-date: 2024-11-02T05:49:15+00:00
qbittorrent  | ───────────────────────────────────────
qbittorrent  |     
qbittorrent  | [custom-init] No custom files found, skipping...
qbittorrent  | WebUI will be started shortly after internal preparations. Please wait...
qbittorrent  | 
qbittorrent  | ******** Information ********
qbittorrent  | To control qBittorrent, access the WebUI at: http://localhost:8090
qbittorrent  | Connection to localhost (::1) 8090 port [tcp/*] succeeded!
qbittorrent  | [ls.io-init] done.

Your workaround does not seem to help. This did not happen with 4.6.3, which is what I was running just prior to the update.

ak-42 avatar Nov 04 '24 05:11 ak-42

Hi I'm seeing this issue now with the following setup:

qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    network_mode: service:vpn
    container_name: qbittorrent
    depends_on:
      - vpn
    environment:
      - PUID=0
      - PGID=0
      - TZ=${TZ}
      - WEBUI_PORT=8080
      - DOCKER_MODS=ghcr.io/gabe565/linuxserver-mod-vuetorrent
    volumes:
      - ${COMMON_PATH}:${COMMON_PATH}
      - ${COMMON_PATH}/configs/qbittorrent:/config
      - ${COMMON_PATH}/qbittorrent/downloads:/downloads
    restart: unless-stopped

Here are my logs:

[mod-init] Running Docker Modification Logic
[mod-init] Adding gabe565/linuxserver-mod-vuetorrent to container
[mod-init] (ERROR) gabe565/linuxserver-mod-vuetorrent digest could not be fetched from ghcr.io
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

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

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    0
User GID:    0
───────────────────────────────────────
Linuxserver.io version: 5.0.1-r0-ls362
Build-date: 2024-11-02T05:49:15+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
QtSingleCoreApplication: listen on local socket failed, QLocalServer::listen: Unknown error 22
WebUI will be started shortly after internal preparations. Please wait...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080
Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!
[ls.io-init] done.

apotenza92 avatar Nov 04 '24 08:11 apotenza92

Got around this issue by using DOCKER_MODS=ghcr.io/vuetorrent/vuetorrent-lsio-mod:latest insead from the instructions here: https://github.com/VueTorrent/VueTorrent/wiki/Installation#using-lsio-docker-mod

apotenza92 avatar Nov 04 '24 09:11 apotenza92