Vaultwarden error after image upgrade: "Referencing column 'user_uuid' and referenced column 'uuid' in foreign key constraint 'archives_ibfk_1' are incompatible."

[joseph]

Mine seems to have updated fine

[joseph]

Same as https://github.com/dani-garcia/vaultwarden/issues/7182 and https://github.com/dani-garcia/vaultwarden/discussions/7183 which points to some charset issues .

[joseph]

Can you check the encoding of the database and also the tables?

In the web terminal, first get the database name:

echo $CLOUDRON_MYSQL_DATABASE

Then, 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

[Teiluj]

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.

[joseph]

@Teiluj this was a bug in vaultwarden a while go (which is why they maintain a wiki article on how to fix it up). https://github.com/search?q=repo%3Adani-garcia%2Fvaultwarden charset&type=issues

[p44]

Same problem here. Restored to 1.24.4 and stopped automatic updates.

[jdaviescoates]

I also had a not responding app and have reverted. Guess I need to look at that guide...

[p44]

@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

[BetaBreak]

Is there a step by step instruction to solve this issue, for me it is unclear how to fix this issue. Thanks!

[jayonrails]

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?

[BetaBreak]

Thanks, when I run the queries I don't get out put..
Should I do it before upgrading, and or in recovery mode?