Closed synergy1990 closed 1 hour ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
The app key and database information should already have been present in the .env file in your /config/www directory. By nuking everything you've removed that and will need to ensure it matches the readme as some of the DB envs have been renamed to match the upstream values.
The APP_KEY needs to be copied as-is from what is generated, yours is missing the start and will not load correctly even once you've fixed the DB auth issues.
Holy! I didn't see, these changes. To clearify it for others: USER and PASS were changed to USERNAME and PASSWORD.
Added the "base64:" to the string - now everything is working (again) as It should! Thank you so much and have a nice weekend! :)
Is there an existing issue for this?
Current Behavior
Access denied for user 'database_username'@'bookstack.bookstack_default' I guess there is something wrong in the init script and especially with the connection to the database. It might work, when everything was setup correctly with a previous version already and it's just the container being updated, but it definitely fails on an initial setup.
It fails with most recent image: lscr.io/linuxserver/bookstack:latest But WORKS with this one: lscr.io/linuxserver/bookstack:24.10.20241009
Expected Behavior
It should rather work - as it did in the image: lscr.io/linuxserver/bookstack:24.10.20241009
Also I dislike that the API_KEY-creation is not part of the init-script anymore!
Steps To Reproduce
I completely removed the stack (as it is called in Portainer), the containers, the volumes and did a system prune -a. It works for the 20241009-image. It always fails with the current one.
Environment
CPU architecture
x86-64
Docker creation
Container logs