mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 11:19:36 +03:00
Upgrading bookstack and bookstack_db from v22.10.2 (SQLSTATE[HY000] [1045] Access denied for user 'bookstack'@'bookstack.bookstack_default) #3741
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AlfaJackal on GitHub (Apr 13, 2023).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
After executing
docker-compose pulldocker-compose up -d --remove-orphansdocker image pruneI then upgraded the database with
mariadb-upgrade -u root -p. No errors.Bookstack won't fire back up. Neither per domain (nginx) nor directly per ip:6875.
It has some issues accessing the db.
This is my docker-compose.yaml:
Exact BookStack Version
v23.02.3
Log Content
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
using keys found in /config/keys
App Key found - setting variable for seds
Running config - DB_HOST set
Waiting for DB to be available
Illuminate\Database\QueryException
SQLSTATE[HY000] [1045] Access denied for user 'bookstack'@'bookstack.bookstack_default' (using password: YES) (SQL: select * from information_schema.tables where table_schema = bookstackapp and table_name = migrations and table_type = 'BASE TABLE')
at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:760
756▕ // If an exception occurs when attempting to run a query, we'll format the error
757▕ // message to include the bindings with SQL, which will make this exception a
758▕ // lot more helpful to the developer instead of just the database's errors.
759▕ catch (Exception $e) {
➜ 760▕ throw new QueryException(
761▕ $query, $this->prepareBindings($bindings), $e
762▕ );
763▕ }
764▕ }
+36 vendor frames
37 /app/www/artisan:37
Illuminate\Foundation\Console\Kernel::handle()
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│ old date │ new date │ path │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ │ 2022-08-16 │ /config/nginx/nginx.conf │
│ 2018-03-06 │ 2022-10-04 │ /config/nginx/site-confs/default.conf │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
PHP Version
No response
Hosting Environment
Proxmox with Ubuntu 22.10
@AlfaJackal commented on GitHub (Apr 13, 2023):
I am stupid: Don't know why but password was different - I couldn't see the forest for the trees.