[BUG] "Couldn't fetch auth token from ghcr.io" in 5.0.4-r0-ls389

[adamkobor]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Using the vuetorrent docker mod stopped working in 5.0.4-r0-ls389, works with 5.0.4-r0-ls388.

Expected Behavior

Docker mod should be loaded

Steps To Reproduce

1. Deploy the aforementioned version with the provided docker-compose.yml definition

Environment

- OS: Ubuntu 24.0.2 LTS
- How docker service was installed: docker-compose + Portainer

CPU architecture

x86-64

Docker creation

services:
  torrent:
    image: lscr.io/linuxserver/qbittorrent:5.0.4-r0-ls389
    container_name: qbitwireguard
    network_mode: service:vpn
    deploy:
      resources:
        limits:
          memory: 2048M
    labels:
      - deunhealth.restart.on.unhealthy=true
      - wud.tag.include=^\d+\.\d+\.\d+$$
      - wud.tag.exclude=^(20|14)\.\d+\.\d+$$
    healthcheck:
      test: cd /config/qBittorrent/`curl http://localhost:8088/api/v2/transfer/info | jq -r .connection_status` || exit 1
      interval: 120s
      timeout: 30s
      start_period: 180s
      retries: 10
    environment:
      - WEBUI_PORT=8088
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Vienna
      - DOCKER_MODS=ghcr.io/vuetorrent/vuetorrent-lsio-mod:latest
    volumes:
      - /home/home/docker/config:/config
      - /home/home/docker/config/qBittorrent/scripts:/scripts
      - /disks/data:/downloads
    depends_on:
      vpn:
        condition: service_healthy
    restart: always
# ...
networks:
  frontend:
    name: vpn

Container logs

[mod-init] Running Docker Modification Logic
[mod-init] Adding vuetorrent/vuetorrent-lsio-mod:latest to container
[mod-init] (ERROR) Couldn't fetch auth token from ghcr.io, switching to offline mode for vuetorrent/vuetorrent-lsio-mod:latest
[mod-init] (ERROR) OFFLINE: vuetorrent/vuetorrent-lsio-mod:latest not found in modcache, skipping
[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:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 5.0.4-r0-ls389
Build-date: 2025-04-13T06:54:20+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
A WebUI röviddel a belső előkészületek után elindul. Kérlek várj...
******** Információ ********
qBittorrent irányításához nyissa meg a Web UI-t itt: http://localhost:8088
Connection to localhost (127.0.0.1) 8088 port [tcp/omniorb] succeeded!
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[aptalca]

Looks like a networking issue, likely due to network_mode: service:vpn. Unfortunately we do not support for containers using another container's network and/or through vpn containers

[adamkobor]

Looks like a networking issue, likely due to network_mode: service:vpn. Unfortunately we do not support for containers using another container's network and/or through vpn containers

thanks for your quick answer @aptalca, but why does it work with ls388 then?

[j0nnymoe]

Try if without the VPN and do you get the same issue?

[adamkobor]

Try if without the VPN and do you get the same issue?

it works without the intermediate VPN, but I think it's a quite common use case that people are using a VPN in front of their containerized torrent client, and it's also suspicious that the exact same setup worked without any problem in the previous build

[TheCoolestPaul]

I am also running into this issue. I am not qbit with a VPN but I am routing it through another container for the VPN. This used to work.

[adamkobor]

@j0nnymoe so it's not planned to make this work again, did I get it right?

[j0nnymoe]

There is nothing for us to change, something with your VPN config is likely tripping this up because you've shown it works fine without.

[adamkobor]

There is nothing for us to change, something with your VPN config is likely tripping this up because you've shown it works fine without.

yeah and it also worked with my vpn before this release, and it still works, because i nailed my tag to the working one, so i really can't see how it could be the problem of the vpn config. but i got the message, it's out of your responsibility...

[arteeh]

Adding a health check to the compose file fixed this error for me. This way it won't try to start downloading docker mods before the VPN is connected.

Under gluetun:

healthcheck:
  test: ["CMD", "/gluetun-entrypoint", "healthcheck"]
  start_period: 10s
  interval: 5s
  timeout: 5s
  retries: 1

Under linuxserver/qbittorrent:

depends_on:
  gluetun:
    condition: service_healthy

[adamkobor]

Adding a health check to the compose file fixed this error for me. This way it won't try to start downloading docker mods before the VPN is connected.

Under gluetun:

healthcheck:
  test: ["CMD", "/gluetun-entrypoint", "healthcheck"]
  start_period: 10s
  interval: 5s
  timeout: 5s
  retries: 1

Under linuxserver/qbittorrent:

depends_on:
  gluetun:
    condition: service_healthy

thanks for the hint, but I think in my case that's not the problem, added a healthcheck to the VPN container, but I'm still getting the same error

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.