Vaultwarden fails to start after update – DB migration error (SSO)
-
Can you check the encoding of the database and also the tables?
In the web terminal, first get the database name:
echo $CLOUDRON_MYSQL_DATABASEThen, click the mysql button above and press enter. Replace DB_NAME_HERE . You should get utf8mb4
mysql> SELECT SCHEMA_NAME, DEFAULT_CHARACTER_SET_NAME, DEFAULT_COLLATION_NAME FROM information_schema.SCHEMATA WHERE SCHEMA_NAME = 'DB_NAME_HERE'; +------------------+----------------------------+------------------------+ | SCHEMA_NAME | DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME | +------------------+----------------------------+------------------------+ | fb30d5a9f5fd3620 | utf8mb4 | utf8mb4_unicode_ci | +------------------+----------------------------+------------------------+Then, check all the tables.
mysql> SELECT TABLE_NAME, TABLE_TYPE, ENGINE, TABLE_COLLATION FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'fb30d5a9f5fd3620' ORDER BY TABLE_NAME; +----------------------------+------------+--------+--------------------+ | TABLE_NAME | TABLE_TYPE | ENGINE | TABLE_COLLATION | +----------------------------+------------+--------+--------------------+ | __diesel_schema_migrations | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | archives | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | attachments | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | auth_requests | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | ciphers | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | ciphers_collections | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | collections | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | collections_groups | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | devices | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | emergency_access | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | event | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | favorites | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | folders | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | folders_ciphers | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | groups | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | groups_users | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | invitations | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | org_policies | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | organization_api_key | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | organizations | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | sends | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | sso_auth | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | sso_users | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | twofactor | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | twofactor_duo_ctx | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | twofactor_incomplete | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | users | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | users_collections | BASE TABLE | InnoDB | utf8mb4_unicode_ci | | users_organizations | BASE TABLE | InnoDB | utf8mb4_unicode_ci | +----------------------------+------------+--------+--------------------+ 29 rows in set (0.01 sec)If the table encoding is not the above, then first take a backup of the app and then follow the instructions at https://github.com/dani-garcia/vaultwarden/wiki/Using-the-MariaDB-(MySQL)-Backend#foreign-key-errors-collation-and-charset
-
This seems to fix the issue indeed - At least from my side, there was a table collection charset mismatch.
The other question is how it came to be. -
Same problem here. Restored to 1.24.4 and stopped automatic updates.
-
I also had a not responding app and have reverted. Guess I need to look at that guide...
-
@jdaviescoates @joseph Thanks for your advice. I followed this guide: https://github.com/dani-garcia/vaultwarden/wiki/Using-the-MariaDB-(MySQL)-Backend#foreign-key-errors-collation-and-charset and problem now is fixed.
thanks a lot
-
The above posted link to the GitHub wiki seems to be the step by step instruction. Which is the part where you don't get forward?
-
Hello @d19dotca @teiluj @ikalou @p44 @jdaviescoates @betabreak @jayonrails
This issue was discussed before, and I did create a handy script to fix the issue.
Please see: https://forum.cloudron.io/topic/14812/vaultwarden-fails-to-start-after-update-db-migration-error-sso/24?_=1778581136537I have also merged this topic into the original topic so there is no duplicate.
-
J james referenced this topic on
-
Hello @d19dotca @teiluj @ikalou @p44 @jdaviescoates @betabreak @jayonrails
This issue was discussed before, and I did create a handy script to fix the issue.
Please see: https://forum.cloudron.io/topic/14812/vaultwarden-fails-to-start-after-update-db-migration-error-sso/24?_=1778581136537I have also merged this topic into the original topic so there is no duplicate.
-
Hello @vaultwarden users
Since users have voiced their concerns about manually editing the database I have created a bash script that does it for you.
Please follow these steps if you have this issue:- create an app backup of your @vaultwarden Cloudron app
- put the erroring @vaultwarden app in recovery mode
- open the File Manager of your @vaultwarden app and create a
fix_db.shfile - copy and paste the following script into the just created
fix_db.shfile:#!/bin/bash echo "=> Checking if DEFAULT_CHARACTER_SET_NAME and DEFAULT_COLLATION_NAME are set to utf8mb4 and utf8mb4_unicode_ci" CURRENT_DEFAULT_CHARACTER_SET_NAME=$(mysql --silent --skip-column-names --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} -e "SELECT DEFAULT_CHARACTER_SET_NAME FROM information_schema.SCHEMATA WHERE SCHEMA_NAME = '${CLOUDRON_MYSQL_DATABASE}';" 2>/dev/null) CURRENT_DEFAULT_COLLATION_NAME=$(mysql --silent --skip-column-names --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} -e "SELECT DEFAULT_COLLATION_NAME FROM information_schema.SCHEMATA WHERE SCHEMA_NAME = '${CLOUDRON_MYSQL_DATABASE}';" 2>/dev/null) FIX_NEEDED=0 if [ "${CURRENT_DEFAULT_CHARACTER_SET_NAME}" != "utf8mb4" ] || [ "${CURRENT_DEFAULT_COLLATION_NAME}" != "utf8mb4_unicode_ci" ]; then echo "=> DEFAULT_CHARACTER_SET_NAME or DEFAULT_COLLATION_NAME is not set to utf8mb4 or utf8mb4_unicode_ci." echo "==> Current values are: DEFAULT_CHARACTER_SET_NAME=${CURRENT_DEFAULT_CHARACTER_SET_NAME}, DEFAULT_COLLATION_NAME=${CURRENT_DEFAULT_COLLATION_NAME}" FIX_NEEDED=1 else echo "=> DEFAULT_CHARACTER_SET_NAME is ${CURRENT_DEFAULT_CHARACTER_SET_NAME} and DEFAULT_COLLATION_NAME is ${CURRENT_DEFAULT_COLLATION_NAME}" echo "=> Nothing to do - quitting." FIX_NEEDED=0 exit 0 fi if [ ${FIX_NEEDED} -eq 1 ]; then read -p "Have you created a backup of your Cloudron Vaultwarden app? (y/N): " yn case $yn in [Yy]* ) echo "=> Setting database character set and collation to utf8mb4 and utf8mb4_unicode_ci." mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} -e "ALTER DATABASE \`${CLOUDRON_MYSQL_DATABASE}\` CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;" 2>/dev/null echo "=> Converting all tables to character set utf8mb4 and collation utf8mb4_unicode_ci." mysql --silent --skip-column-names \ --user="${CLOUDRON_MYSQL_USERNAME}" \ --password="${CLOUDRON_MYSQL_PASSWORD}" \ --host="${CLOUDRON_MYSQL_HOST}" \ "${CLOUDRON_MYSQL_DATABASE}" \ -e "SELECT CONCAT('ALTER TABLE \`', TABLE_NAME,'\` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;') AS CharSetConvert FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA='${CLOUDRON_MYSQL_DATABASE}' AND TABLE_TYPE=\"BASE TABLE\";" 2>/dev/null | while read -r sql_command; do echo "==> Executing: ${sql_command}" mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} -e "SET foreign_key_checks=0; ${sql_command} SET foreign_key_checks=1;" 2>/dev/null done ;; [Nn]* ) echo "=> Please create a backup of your database before proceeding with the fix. Exiting." exit 1 ;; * ) echo "=> Invalid response. Please answer with y or n. Exiting." exit 1 ;; esac fi - open the Web Terminal of your @vaultwarden Cloudron app
- execute the following command:
bash /app/data/fix_db.sh - Execute the following command to start @vaultwarden:
/app/pkg/start.sh - Validate if your @vaultwarden is now working correctly
- If validated working, you can delete the
fix_db.shfile and disable the recovery mode of your @vaultwarden Cloudron app
Note:
If there are issues with the copy and paste from Windows devices apperent by error messages likeline 2: $'\r': command not found, please run the following command to fix the script:sed -i 's/\r$//g' /app/data/fix_db.sh
If you run into any issues, copy the output of the terminal, post it here and restore your app from the backup created.
it works, thanks!Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login