You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
services: bookstack: image: lscr.io/linuxserver/bookstack:latest container_name: bookstack environment: - PUID=1000 - PGID=1000 - TZ=Europe/Berlin - APP_URL=http://192.168.144.31:6875 - APP_KEY=WsuTl38ldEY2B14c8FL5hhWlu1v35mTwIXr5Oz+Zitc= - DB_HOST=bookstack_db - DB_PORT=3306 - DB_USER=bookstack - DB_PASS=mybookstack - DB_DATABASE=bookstackapp volumes: - bookstack:/config ports: - 6875:80 restart: unless-stopped depends_on: - bookstack_db bookstack_db: image: lscr.io/linuxserver/mariadb container_name: bookstack_db environment: - PUID=1000 - PGID=1000 - TZ=Europe/Berlin - MYSQL_ROOT_PASSWORD=mybookstackrootpw - MYSQL_DATABASE=bookstackapp - MYSQL_USER=bookstack - MYSQL_PASSWORD=mybookstack volumes: - bookstackdb:/config restart: unless-stopped volumes: bookstack: bookstackdb: Afterwards I run `docker run -it --rm --entrypoint /bin/bash lscr.io/linuxserver/bookstack:latest appkey` and pasted the output to the environmental variable API_KEY= and restarted the container.
Container logs
The text was updated successfully, but these errors were encountered: