Can't login qBittorrent webUI

LSIO Discussion Container Support
1

Hello All,

I installed qBittorrent with docker I can access webUI but when i tried to login with admin/adminadmin it stays in the login screen if i tried with any other credentials it will say login credentials are wrong so it looks like webUI should be working.

  --name=qbittorrent \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/Amsterdam \
  -e WEBUI_PORT=9019 \
  -p 6881:6881 \
  -p 6881:6881/udp \
  -p 9019:9019 \
  -v /srv/dev-disk-by-uuid-30a01947-9aad-499e-a7d2-5a931bf55c5d/Media_Shared/Containers:/config \
  -v /srv/dev-disk-by-uuid-30a01947-9aad-499e-a7d2-5a931bf55c5d/Media_Shared:/downloads \
  --restart unless-stopped \
  lscr.io/linuxserver/qbittorrent

qBittorent.conf

[AutoRun]
enabled=false
program=

[LegalNotice]
Accepted=true

[Preferences]
Connection\PortRangeMin=6881
Connection\UPnP=false
Downloads\SavePath=/downloads/
Downloads\TempPath=/downloads/incomplete/
Queueing\QueueingEnabled=true
WebUI\Address=*
WebUI\Port=9019
WebUI\ServerDomains=*

Please help me!

2

Can you provide logs? what you have posted all looks correct.

edit: did you deploy this container using portainer or any other gui?

3

I have the same issue, useing portainer and deploying from the stack

4

This will happen if you’re clicking on the link from within portainer to get to the qbittorrent webui.

Or if you’re running into a libseccomp issue (will be shown in the docker logs)

5

Hello yes I used portainer. After inspecting the logs I was able to login after I updated libeseccomp. Now I’m not able to get to webUI at all.
Logs gives the address (myip:9019 is not available)
Which is weird the port is open on my router and run plex on same server which worked normal. I’m quite new with Linux not sure where to Find it I can ping to my local ip address just fine. I even delete the container and image and installed it again.

6

Here is my log i can only assube that benish has the same issue but it might help
[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] 00-env-file-init: executing… ,
[cont-init.d] 00-env-file-init: exited 0.,
[cont-init.d] 00-start-container: executing… ,

ENVIRONMENT

1
PGID=100

Executing usermod…
Applying permissions to /config
[cont-init.d] 00-start-container: exited 0.
[cont-init.d] 01-configure-app: executing…
[cont-init.d] 01-configure-app: exited 0.
[cont-init.d] 02-setup-wg: executing…
[cont-init.d] 02-setup-wg: exited 0.
[cont-init.d] 03-setup-privoxy: executing…
[cont-init.d] 03-setup-privoxy: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
QWaitCondition::wait(): cv wait failure: Invalid argument
QWaitCondition::wait(): cv wait failure: Invalid argument

7

here is my log:

User gid: 1000

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

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

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

[cont-init.d] 90-custom-folders: executing…

[cont-init.d] 90-custom-folders: 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.

“Web UI: Unable to bind to IP: , port: 9019. Reason: The address is not available”

8

this implies port 2019 is already in use. you need to use something that doesn’t conflict.

9

please provide full docker logs (use paste/hastebin if you need to fit more. the issue described is usually caused by leveraging the link within portainer or libseccomp

11

(thats everything in 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] 00-env-file-init: executing…

[cont-init.d] 00-env-file-init: exited 0.

[cont-init.d] 00-start-container: executing…

ENVIRONMENT

1

PGID=100

2

TZ=Europe/London

WEBUI_PORTS=8080/tcp,8080/udp

VPN_ENABLED=false

VPN_LAN_NETWORK=

VPN_CONF=wg0

VPN_ADDITIONAL_PORTS=

PRIVOXY_ENABLED=false

Executing usermod…

Applying permissions to /config

[cont-init.d] 00-start-container: exited 0.

[cont-init.d] 01-configure-app: executing…

[cont-init.d] 01-configure-app: exited 0.

[cont-init.d] 02-setup-wg: executing…

[cont-init.d] 02-setup-wg: exited 0.

[cont-init.d] 03-setup-privoxy: executing…

[cont-init.d] 03-setup-privoxy: exited 0.

[cont-init.d] done.

[services.d] starting services

[services.d] done.

QWaitCondition::wait(): cv wait failure: Invalid argument

QWaitCondition::wait(): cv wait failure: Invalid argument

12

we don’t offer support for tunneling our containers through other conainers (also that still wasnt a full log, our logs begin with our ascii logo)

please remove all the vpn configuration and try to recreate the problem

i’m also not entirely sure this is even our container.

13

Sweet after changing my port it works thank you very much😁

14

its fine ill just delete the container and find a new instalation tutorial thank anyway :slight_smile:

15

glad you got it sorted, have fun!