rpi3 64bit running on omv6 has qbittorent locked out

    Hi there,

    I am messing around with my configuration of my docker, a lot lately, and I have broke the login web-gui of qbittorent.


    here is the compose image I run:

    ---

    version: "2.1"

    services:

    qbittorrent:

    image: lscr.io/linuxserver/qbittorrent:latest

    container_name: qbittorrent

    environment:

    - PUID=1000

    - PGID=1000

    - TZ=Europe/Rome

    - WEBUI_PORT=8080

    volumes:

    - /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/Docker:/config

    - /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/Downloads:/downloads

    ports:

    - 8080:8080

    - 6881:6881

    - 6881:6881/udp

    restart: unless-stopped



    here is the output of id:

    uid=1000(alessio) gid=100(users) groups=100(users),0(root),1(daemon),2(bin),3(sys),4(adm),5(tty),6(disk),7(lp),8(mail),9(news),10(uucp),12(man),13(proxy),15(kmem),20(dialout),21(fax),22(voice),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),33(www-data),34(backup),37(operator),38(list),39(irc),40(src),41(gnats),42(shadow),43(utmp),44(video),45(sasl),46(plugdev),50(staff),60(games),101(systemd-journal),102(systemd-network),103(systemd-resolve),104(input),105(kvm),106(render),107(crontab),108(netdev),109(systemd-timesync),110(messagebus),111(ssh),112(bluetooth),113(avahi),114(ssl-cert),115(postfix),116(postdrop),117(_chrony),118(sambashare),990(docker),991(openmediavault-notify),992(openmediavault-webgui),993(openmediavault-admin),994(openmediavault-engined),995(openmediavault-config),996(systemd-coredump),997(gpio),998(i2c),999(spi),1001(sftp-access),65534(nogroup)




    here is the "tree -L 2" output under /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/Docker

    ├── qBittorrent

    │ ├── BT_backup

    │ ├── GeoDB

    │ ├── categories.json

    │ ├── ipc-socket

    │ ├── lockfile

    │ ├── logs

    │ ├── qBittorrent-data.conf

    │ ├── qBittorrent.conf

    │ ├── rss

    │ └── watched_folders.json


    For the sake of completion, I was trying to download a torrent but failed because qBittorent returned me the error status of any torrent I wanted to download


    Previously the login was "admin" and psw "adminadmin". I deleted everything and redeployed everything and nothing i broke it. I also tried to follow this guide but I cannot find the config file let alone the line :https://github.com/qbittorrent…O-X-%28qbittorrent-nox%29

    Quote from Ale_110

    here is the output of id:

    uid=1000(alessio) gid=100(users) groups=100(users),0(root),1(daemon),2(bin),3(sys),4(adm),5(tty),6(disk),7(lp),8(mail),9(news),10(uucp),12(man),13(proxy),15(kmem),20(dialout),21(fax),22(voice),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),33(www-data),34(backup),37(operator),38(list),39(irc),40(src),41(gnats),42(shadow),43(utmp),44(video),45(sasl),46(plugdev),50(staff),60(games),101(systemd-journal),102(systemd-network),103(systemd-resolve),104(input),105(kvm),106(render),107(crontab),108(netdev),109(systemd-timesync),110(messagebus),111(ssh),112(bluetooth),113(avahi),114(ssl-cert),115(postfix),116(postdrop),117(_chrony),118(sambashare),990(docker),991(openmediavault-notify),992(openmediavault-webgui),993(openmediavault-admin),994(openmediavault-engined),995(openmediavault-config),996(systemd-coredump),997(gpio),998(i2c),999(spi),1001(sftp-access),65534(nogroup)

    If your USER is on ALL those groups, it's the same as using root user (WRONG!!!!!!!!!!!)

    Linux is NOT windows where the user is always administrator (windows root) unless you create a new one with less priviledges.

    Quote from Ale_110

    volumes:

    - /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/Docker:/config

    Are you using the same PATH on any other container?

    oh well... I guess I got scolded... but thanks it helps. I will limit it to just the basics I guess, but then i must have an administrator so what is the difference I still have the same password.


    Yes I am having the same abs path for any other container. is it wrong?

    Quote from Ale_110

    I will limit it to just the basics I guess, but then i must have an administrator so what is the difference I still have the same password.

    Create a new user on the GUI. That USER will only be on some basic groups that is enough to operate.

    If/when you need to perform tasks that require higher priviledges, you use a USER with sudo or the root itself.


    Quote from Ale_110

    Yes I am having the same abs path for any other container. is it wrong?

    You need to seperate each container config folder. If you reuse the same PATH on every container, can you imagine the mess it is inside that folder?


    You can use, for eg

    Code
    volumes:

- /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/config/qbittorrent:/config


    On another container (jellyfin, for eg)

    Code
    volumes:

- /srv/dev-disk-by-uuid-ea2e47ee-25a7-4afd-81d9-e92b5f749966/config/jellyfin:/config


    And so on, and so on....

    If you are running Qbittorrent 4.6.1 (the latest recent upgrade) using the default login credentials to the WebUI, it will not let you in because those credentials have been deprecated and disabled.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login