[BUG] <New Install, possible UI Bug as result of default password changes?>

[mousethatischarles]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Debianx64-based OS (DietPi x64) on ESXi 7u3 Migrating over to a new server install:

qBittorrent Docker running fine on old install... yes, yes... I changed the default qBittorrent WebUI password!
New docker pull: ghcr.io/linuxserver/qbittorrent:latest resulting in v4.6.3-r0-ls306 - bare install is functional.
Configs folder transferred across from old install and:

1. Unable to log in to WebUI with either old password or adminadmin
2. On reload "Unauthorized"
   ->Returning to default config results in same issue, usual fix for "Unauthorized" does work but still unable to log in to WebUI
   ->The usual password fix no longer available as qBtrorrent.inf no longer contains the relevant lines to reset - why? I believe this is a deliberate change and password details are now 'hidden' elsewhere to be loaded on start up.
   sigh
   -> qBitorrent (seemingly) fully uninstalled and then reinstalled from scratch - I'll now have to manually re-enter all my torrents and settings from scratch rather than transfer them across (bug report bump to alpine 3.6 #1)
   -> But, No. The unrecognised adminadmin password 'feature' remains even with a new and hopefully 'clean' install. My old password also not working. (either with fully new Config folder or my old one) I presume the 'hidden' location is not expunged on an uninstall and so the issue will now forever remain unless I a) know where this (IMO unnecessary and frustrating) change has been hidden or I fully reinstall the OS! (bug report exec format error #2)
   For now I'll try with an earlier (IMO non-broken) version, take care not to 'upgrade', and see how that goes.

All the best.

Expected Behavior

see above

Steps To Reproduce

see aove

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

see above

Container logs

see aove

[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.

[github-actions]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

[Roxedus]

https://github.com/linuxserver/docker-qbittorrent#application-setup

[geebru]

@Roxedus Replying to that link since I'm having a relevant but slightly different setup issue:

I'm running this image via Container Manager in my Synology DS220+. For about a month, the setup was fine, my login worked and things were great. Starting this weekend, I had an issue where my saved credentials wouldn't work, but neither would the temporary ones from the logs. Yesterday I updated to the latest version of the image in hopes it would fix it but no luck.

If I do a full re-build and reset I can use the logged temp to re-log in, change my account, and use that. But after a period of inactivity, it seems to slide back into invalid credentials. I know nothing truly happens randomly but I'm at a loss to figure out why qB suddenly seems to be losing the credentials information.

I also see this was marked invalid due to not following the template but wanted to chime in that I've done the setup a few times now per the docs and it still resets or loses my credentials.

[will-molloy]

Same here, can't login with the default password given.

[xilmen]

Hi,

Have you tried using another browser or clearing the cache/cookies/session?

[shareit]

It is reproducing also on my side. I'm not able to login in a browser (also in incognito) with the generated password from the terminal.
Do you know what is the stable version without this issue? I was using in the past qbittorrent (with :latest tag) in docker and it was great.

[j0nnymoe]

If we don't get any logs or compose snippets, it's hard for us to look into. The original post was marked invalid because not enough information was provided, if people container just to say same here without providing the missing info, we can't attempt to move this forward.

[atomass]

I would like to report the "same" issue: after an upgrade (docker compose pull) my old password did not work anymore and I couldn't see any temporary one in the logs.
So, what I did in order to solve the issue was

1. backup the config folder: mv config config_backup
2. delete the qbittorrent image: docker image rm lscr.io/linuxserver/qbittorrent:latest
3. start the docker docker compose up -d --remove-orphans
4. check the logs for the temporary password: docker compose logs (it was there this time!)
5. change the password in the WebUI settings
6. stop the container docker compose down
7. copy the WebUI\Password_PBKDF2=.... line from the new config/qBittorrent/qBittorrent.conf to the backup one
8. revert backup the backup config
9. profit

While this is an hacky workaround, I think that the update process of this docker has a "bug".

[yorktownting]

Same "Unauthorized" when I use a docker-compose to up the container in Windows' docker desktop. I am unable to change the default random password 💔

[carlos-garcia]

I am having the same issue and after finding the default password on the logs, all my torrents are gone!.. even worse, if i put a new password on the UI, after restarting the container, the configuration is gone and there a new default password again.

[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.