Closed jakaerc closed 1 month ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Looks like at some point upstream changed the default user so that it doesn't actually insert the user into the database unless you...set the default user to the default value. Linked PR should fix it.
I'm new to this. How do I implement the fix? Thank you.
Just wait until we've merged the PR and then pull the latest image.
This now works but with every reset it readds the demo@demo.demo user again and you can't delete it.
Well that's not great design. I'll have a look and see if I can find a way to not reinsert the user on subsequent runs, otherwise I'll have to change the setup process to work around it.
@jakaerc please can you test ghcr.io/linuxserver/lspipepr-planka:v1.22.0-pkg-07fc2934-dev-51c866446b5244a1d8c6fc29e6bfffb3b32f4896-pr-6
Please note you now need to set these envs (to whatever you want)
- DEFAULT_ADMIN_EMAIL=demo@demo.demo
- DEFAULT_ADMIN_PASSWORD=demo
- DEFAULT_ADMIN_NAME=Demo User
- DEFAULT_ADMIN_USERNAME=demo
They can be removed after the first run if you choose.
This seems to be working now as I was able to delete the demo user but not sure if I would know where to input the envs on fresh install as I'm doing it over unraid. Would there be an input field in the unraid template?
There will be once the PR is merged and the templates update
Is there an existing issue for this?
Current Behavior
When frst time on login page after install I can't login with demo@demo.demo.
Expected Behavior
I should login with user: demo@demo.demo and pass: demo
Steps To Reproduce
/
Environment
CPU architecture
x86-64
Docker creation
Container logs