Can't create table bitwarden_rs.sends (errno: 150 "foreign key constraint is incorrectly formed") [v 1.20] #998

New Issue

Closed

opened 2025-11-07 06:54:50 -06:00 by GiteaMirror · 6 comments

GiteaMirror commented 2025-11-07 06:54:50 -06:00

Owner

Copy Link

Copy Source

Originally created by @FuzzyMistborn on GitHub (Mar 29, 2021).

Subject of the issue

When updating to the latest v 1.20 docker image, I get the below error and the container will not load.

Deployment environment

Your environment (Generated via diagnostics page)

• Bitwarden_rs version: v1.19.0
• Web-vault version: v2.18.1
• Running within Docker: true
• Internet access: true
• Uses a proxy: false
• DNS Check: true
• Time Check: true
• Domain Configuration Check: true
• HTTPS Check: true
• Database type: MySQL
• Database version: [PLEASE PROVIDE DATABASE VERSION]
• Clients used:
• Reverse proxy and version:
• Other relevant information:

Config (Generated via diagnostics page)

{
  "_duo_akey": null,
  "_enable_duo": false,
  "_enable_email_2fa": true,
  "_enable_smtp": true,
  "_enable_yubico": true,
  "_ip_header_enabled": true,
  "admin_token": "***",
  "allowed_iframe_ancestors": "",
  "attachments_folder": "data/attachments",
  "authenticator_disable_time_drift": false,
  "data_folder": "data",
  "database_max_conns": 10,
  "database_url": "*****://*********:**********.*********.*********@***.***.**.**:****/************",
  "db_connection_retries": 15,
  "disable_2fa_remember": false,
  "disable_admin_token": false,
  "disable_icon_download": false,
  "domain": "*****://*********.****.****",
  "domain_origin": "*****://*********.****.****",
  "domain_path": "",
  "domain_set": true,
  "duo_host": null,
  "duo_ikey": null,
  "duo_skey": null,
  "email_attempts_limit": 3,
  "email_expiration_time": 600,
  "email_token_size": 6,
  "enable_db_wal": false,
  "extended_logging": true,
  "helo_name": null,
  "hibp_api_key": null,
  "icon_blacklist_non_global_ips": true,
  "icon_blacklist_regex": null,
  "icon_cache_folder": "data/icon_cache",
  "icon_cache_negttl": 259200,
  "icon_cache_ttl": 2592000,
  "icon_download_timeout": 10,
  "invitation_org_name": "XXXXXX",
  "invitations_allowed": true,
  "ip_header": "X-Real-IP",
  "log_file": "/data/bitwarden.log",
  "log_level": "Info",
  "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f",
  "org_attachment_limit": null,
  "org_creation_users": "",
  "password_iterations": 100000,
  "reload_templates": false,
  "require_device_email": false,
  "rsa_key_filename": "data/rsa_key",
  "show_password_hint": true,
  "signups_allowed": false,
  "signups_domains_whitelist": "",
  "signups_verify": false,
  "signups_verify_resend_limit": 6,
  "signups_verify_resend_time": 3600,
  "smtp_accept_invalid_certs": false,
  "smtp_accept_invalid_hostnames": false,
  "smtp_auth_mechanism": null,
  "smtp_debug": false,
  "smtp_explicit_tls": false,
  "smtp_from": "*********@****.****",
  "smtp_from_name": "Bitwarden",
  "smtp_host": "**-**.*******.***",
  "smtp_password": "***",
  "smtp_port": 587,
  "smtp_ssl": true,
  "smtp_timeout": 15,
  "smtp_username": "********************************",
  "templates_folder": "data/templates",
  "use_syslog": false,
  "user_attachment_limit": null,
  "web_vault_enabled": true,
  "web_vault_folder": "web-vault/",
  "websocket_address": "0.0.0.0",
  "websocket_enabled": true,
  "websocket_port": 3012,
  "yubico_client_id": "47172",
  "yubico_secret_key": "***",
  "yubico_server": null
}

Docker, here's the below information based on my 1.19 install

• bitwarden_rs version: 1.20

• Install method: Docker image

• Clients used: N/A

• Reverse proxy and version: N/A

• MySQL/MariaDB or PostgreSQL version: 10.5.9

• Other relevant details:

Steps to reproduce

Just updated the container from current install

Expected behaviour

Container will load

Actual behaviour

I get the below error in the log and it just loops the error/fails to complete the load

Troubleshooting data

Log:

/--------------------------------------------------------------------\

|                       Starting Bitwarden_RS                        |

|                           Version 1.20.0                           |

|--------------------------------------------------------------------|

| This is an *unofficial* Bitwarden implementation, DO NOT use the   |

| official channels to report bugs/features, regardless of client.   |

| Send usage/configuration questions or feature requests to:         |

|   https://bitwardenrs.discourse.group/                             |

| Report suspected bugs/issues in the software itself at:            |

|   https://github.com/dani-garcia/bitwarden_rs/issues/new           |

\--------------------------------------------------------------------/


FO] No .env file found.


[WARNING] The following environment variables are being overriden by the config file,

[WARNING] please use the admin panel to make changes to them:

[WARNING] SIGNUPS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD


Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:53.936][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:54.947][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:55.958][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:56.968][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:57.978][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:58.988][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:34:59.999][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:35:01.009][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:35:02.020][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:35:03.030][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:35:04.039][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Running migration 20210311190243

Executing migration script 20210311190243/up.sql

[2021-03-29 12:35:05.049][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.

[CAUSE] QueryError(

    DatabaseError(

        __Unknown,

        "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")",

    ),

)

Originally created by @FuzzyMistborn on GitHub (Mar 29, 2021). <!-- # ### NOTE: Please update to the latest version of bitwarden_rs before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/bitwarden_rs/issues/1180 * https://github.com/dani-garcia/bitwarden_rs/wiki/Updating-the-bitwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> When updating to the latest v 1.20 docker image, I get the below error and the container will not load. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> ### Your environment (Generated via diagnostics page) * Bitwarden_rs version: v1.19.0 * Web-vault version: v2.18.1 * Running within Docker: true * Internet access: true * Uses a proxy: false * DNS Check: true * Time Check: true * Domain Configuration Check: true * HTTPS Check: true * Database type: MySQL * Database version: [PLEASE PROVIDE DATABASE VERSION] * Clients used: * Reverse proxy and version: * Other relevant information: ### Config (Generated via diagnostics page) ```json { "_duo_akey": null, "_enable_duo": false, "_enable_email_2fa": true, "_enable_smtp": true, "_enable_yubico": true, "_ip_header_enabled": true, "admin_token": "***", "allowed_iframe_ancestors": "", "attachments_folder": "data/attachments", "authenticator_disable_time_drift": false, "data_folder": "data", "database_max_conns": 10, "database_url": "*****://*********:**********.*********.*********@***.***.**.**:****/************", "db_connection_retries": 15, "disable_2fa_remember": false, "disable_admin_token": false, "disable_icon_download": false, "domain": "*****://*********.****.****", "domain_origin": "*****://*********.****.****", "domain_path": "", "domain_set": true, "duo_host": null, "duo_ikey": null, "duo_skey": null, "email_attempts_limit": 3, "email_expiration_time": 600, "email_token_size": 6, "enable_db_wal": false, "extended_logging": true, "helo_name": null, "hibp_api_key": null, "icon_blacklist_non_global_ips": true, "icon_blacklist_regex": null, "icon_cache_folder": "data/icon_cache", "icon_cache_negttl": 259200, "icon_cache_ttl": 2592000, "icon_download_timeout": 10, "invitation_org_name": "XXXXXX", "invitations_allowed": true, "ip_header": "X-Real-IP", "log_file": "/data/bitwarden.log", "log_level": "Info", "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f", "org_attachment_limit": null, "org_creation_users": "", "password_iterations": 100000, "reload_templates": false, "require_device_email": false, "rsa_key_filename": "data/rsa_key", "show_password_hint": true, "signups_allowed": false, "signups_domains_whitelist": "", "signups_verify": false, "signups_verify_resend_limit": 6, "signups_verify_resend_time": 3600, "smtp_accept_invalid_certs": false, "smtp_accept_invalid_hostnames": false, "smtp_auth_mechanism": null, "smtp_debug": false, "smtp_explicit_tls": false, "smtp_from": "*********@****.****", "smtp_from_name": "Bitwarden", "smtp_host": "**-**.*******.***", "smtp_password": "***", "smtp_port": 587, "smtp_ssl": true, "smtp_timeout": 15, "smtp_username": "********************************", "templates_folder": "data/templates", "use_syslog": false, "user_attachment_limit": null, "web_vault_enabled": true, "web_vault_folder": "web-vault/", "websocket_address": "0.0.0.0", "websocket_enabled": true, "websocket_port": 3012, "yubico_client_id": "47172", "yubico_secret_key": "***", "yubico_server": null } ``` Docker, here's the below information based on my 1.19 install <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from bitwarden_rs --> <!-- Remember to check if your issue exists on the latest version first! --> * bitwarden_rs version: 1.20 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> N/A * Reverse proxy and version: <!-- if applicable --> N/A * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> 10.5.9 * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> Just updated the container from current install ### Expected behaviour <!-- Tell us what you expected to happen --> Container will load ### Actual behaviour <!-- Tell us what actually happened --> I get the below error in the log and it just loops the error/fails to complete the load ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> Log: ``` /--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.20.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://bitwardenrs.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/bitwarden_rs/issues/new | \--------------------------------------------------------------------/ FO] No .env file found. [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:53.936][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:54.947][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:55.958][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:56.968][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:57.978][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:58.988][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:34:59.999][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:35:01.009][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:35:02.020][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:35:03.030][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:35:04.039][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) Running migration 20210311190243 Executing migration script 20210311190243/up.sql [2021-03-29 12:35:05.049][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. [CAUSE] QueryError( DatabaseError( __Unknown, "Can\'t create table `bitwarden_rs`.`sends` (errno: 150 \"Foreign key constraint is incorrectly formed\")", ), ) ```

GiteaMirror closed this issue 2025-11-07 06:54:50 -06:00

GiteaMirror commented 2025-11-07 06:54:50 -06:00

Author

Owner

Copy Link

Copy Source

@BlackDex commented on GitHub (Mar 29, 2021):

During migrations foreign key checks are disabled. So this probably looks like some collation issue.

Please see: https://github.com/dani-garcia/bitwarden_rs/discussions/1492

There are some tips on how to solve this.

@BlackDex commented on GitHub (Mar 29, 2021): During migrations foreign key checks are disabled. So this probably looks like some collation issue. Please see: https://github.com/dani-garcia/bitwarden_rs/discussions/1492 There are some tips on how to solve this.

GiteaMirror commented 2025-11-07 06:54:50 -06:00

Author

Owner

Copy Link

Copy Source

@FuzzyMistborn commented on GitHub (Mar 29, 2021):

Thanks, that does seem like my issue but I've tried resetting the db character set to both utf8 and utf8mb4 without luck. Here are the commands I'm running in the DB, am I missing something?

ALTER DATABASE bitwarden_rs CHARACTER SET utf8 COLLATE utf8_general_ci;

ALTER DATABASE bitwarden_rs CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

@FuzzyMistborn commented on GitHub (Mar 29, 2021): Thanks, that does seem like my issue but I've tried resetting the db character set to both utf8 and utf8mb4 without luck. Here are the commands I'm running in the DB, am I missing something? `ALTER DATABASE bitwarden_rs CHARACTER SET utf8 COLLATE utf8_general_ci;` `ALTER DATABASE bitwarden_rs CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;`

GiteaMirror commented 2025-11-07 06:54:51 -06:00

Author

Owner

Copy Link

Copy Source

@BlackDex commented on GitHub (Mar 29, 2021):

DId you also checked the tables them self?

@BlackDex commented on GitHub (Mar 29, 2021): DId you also checked the tables them self?

GiteaMirror commented 2025-11-07 06:54:51 -06:00

Author

Owner

Copy Link

Copy Source

@FuzzyMistborn commented on GitHub (Mar 29, 2021):

Sorry I'm not really proficient in mariadb. How would I check that?

@FuzzyMistborn commented on GitHub (Mar 29, 2021): Sorry I'm not really proficient in mariadb. How would I check that?

GiteaMirror commented 2025-11-07 06:54:51 -06:00

Author

Owner

Copy Link

Copy Source

@FuzzyMistborn commented on GitHub (Mar 29, 2021):

Ah nevermind, figured it out. SHOW TABLE STATUS;. Looks like mine is still latin1_swedish_ci so I'll keep digging.

@FuzzyMistborn commented on GitHub (Mar 29, 2021): Ah nevermind, figured it out. `SHOW TABLE STATUS;`. Looks like mine is still `latin1_swedish_ci` so I'll keep digging.

GiteaMirror commented 2025-11-07 06:54:51 -06:00

Author

Owner

Copy Link

Copy Source

@BlackDex commented on GitHub (Mar 29, 2021):

So best way to fix this i think is this:

ALTER DATABASE `bitwarden_rs` CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

After that convert all the tables.
Execute the following, and copy the output.

SELECT CONCAT('ALTER TABLE `', TABLE_NAME,'` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;') AS CharSetConvert
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_SCHEMA="bitwarden_rs"
AND TABLE_TYPE="BASE TABLE";

Copy/Paste the output from above between the following lines:

SET foreign_key_checks = 0;
-- Copy/Paste the output from above here
SET foreign_key_checks = 1;

Now, since all databases should be the same here is a sample with my output:

SET foreign_key_checks = 0;
ALTER TABLE `folders` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `invitations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `__diesel_schema_migrations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `users_collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `devices` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `twofactor` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `sends` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `users` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `users_organizations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `favorites` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `attachments` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `org_policies` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `ciphers` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `folders_ciphers` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `organizations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE `ciphers_collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
SET foreign_key_checks = 1;

@BlackDex commented on GitHub (Mar 29, 2021): So best way to fix this i think is this: ```mysql ALTER DATABASE `bitwarden_rs` CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ``` After that convert all the tables. Execute the following, and copy the output. ```mysql SELECT CONCAT('ALTER TABLE `', TABLE_NAME,'` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;') AS CharSetConvert FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA="bitwarden_rs" AND TABLE_TYPE="BASE TABLE"; ``` Copy/Paste the output from above between the following lines: ```mysql SET foreign_key_checks = 0; -- Copy/Paste the output from above here SET foreign_key_checks = 1; ``` Now, since all databases should be the same here is a sample with my output: ```mysql SET foreign_key_checks = 0; ALTER TABLE `folders` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `invitations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `__diesel_schema_migrations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `users_collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `devices` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `twofactor` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `sends` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `users` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `users_organizations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `favorites` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `attachments` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `org_policies` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `ciphers` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `folders_ciphers` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `organizations` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ALTER TABLE `ciphers_collections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; SET foreign_key_checks = 1; ```

GiteaMirror referenced this issue 2025-11-07 07:52:58 -06:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #2713

GiteaMirror referenced this issue 2026-03-07 20:59:52 -06:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #6490

GiteaMirror referenced this issue 2026-04-16 12:06:40 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #7790

GiteaMirror referenced this issue 2026-04-20 15:16:09 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #11716

GiteaMirror referenced this issue 2026-04-23 07:28:13 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #15696

GiteaMirror referenced this issue 2026-04-25 22:08:07 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #19683

GiteaMirror referenced this issue 2026-04-30 07:34:41 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #21050

GiteaMirror referenced this issue 2026-05-16 05:19:16 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #22378

GiteaMirror referenced this issue 2026-05-22 00:37:57 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #23719

GiteaMirror referenced this issue 2026-05-29 04:16:33 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #25063

GiteaMirror referenced this issue 2026-06-15 13:55:40 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #26413

GiteaMirror referenced this issue 2026-06-17 10:22:21 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #30459

GiteaMirror referenced this issue 2026-06-20 18:47:56 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #31872

GiteaMirror referenced this issue 2026-07-13 20:42:58 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #35939

GiteaMirror referenced this issue 2026-07-17 22:57:24 -05:00

[PR #998] [MERGED] Fixing bad width in 2FA email template #40236

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

v2-registration

revert-7033-patch-1

cached-config-operations

test_dylint

1.37.2

1.37.1

1.37.0

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#998