2FA error: Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such column: g.Id'.

[averkiev]

Steps To Reproduce

1. Open BW login page
2. Enter 2FA code
3. Error is shown

Expected Result

Login into the application

Actual Result

Error is shown after entering 2FA code: An error has occurred. An unexpected error has occurred.

logs\identity.log shows the following error.
An unhandled exception was thrown by the application.
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such column: g.Id'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)

Screenshots or Videos

No response

Additional Context

Version 2023.12.0

Githash Version

919d759-dirty

Environment Details

No response

Database Image

No response

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[Krychaz]

Hello there,

Based on other reports this seems to be a new issue. I have passed this to our engineering team.

[brambaars]

As discussed with support via email, I experience the same. Logfiles were shared, in my case it's MySQL, but also no such column: g.Id in identity.log.

[brambaars]

For the time being, reverting to the previous version (tag 2023.12.0-beta) resolved the issue.
(spin up the container with bitwarden/self-host:2023.12.0-beta instead of bitwarden/self-host:beta)

My vault was emptied somewhere in the process though, but luckily I created an export before performing these actions.

[withinfocus]

@brambaars can you pull the latest from main and give this a try? We made a modification to the database migration.

[brambaars]

@withinfocus thanks for working on this!
I spun up bitwarden/self-host:beta again, and am back to 2024.1.0. The latest files were pulled from bitwarden/self-host.
(I'm not sure how else I would perform your exact request, pulling latest from main; I may be in over my head here...)

Now, logging in on the web vault, results in the "unknown error" immediately after entering my password, before entering the 2FA code.

identity.log shows:

An unhandled exception was thrown by the application.
MySqlConnector.MySqlException (0x80004005): Unknown column 'g.Id' in 'field list'

@averkiev 's log mentions Sqlite though, while I'm running from MySql, as you can see in my log.

[averkiev]

@withinfocus , my container has been upgraded to the latest version of bitwarden/self-host:beta. Now I'm seeing the following error in the admin.log

2024-01-13 06:56:26.693 +00:00 [INF] Migrating database. 2024-01-13 06:56:29.019 +00:00 [ERR] Failed executing DbCommand (2ms) [Parameters=[], CommandType='"Text"', CommandTimeout='30'] INSERT INTO "ef_temp_Grant" ("Id", "ClientId", "ConsumedDate", "CreationDate", "Data", "Description", "ExpirationDate", "Key", "SessionId", "SubjectId", "Type") SELECT "Id", IFNULL("ClientId", ''), "ConsumedDate", "CreationDate", IFNULL("Data", ''), "Description", "ExpirationDate", "Key", "SessionId", "SubjectId", IFNULL("Type", '') FROM "Grant";

For the time, I've reverted the container to self-host:2023.12.0-beta. With that version, I'm able to login.

[potrusil]

I also have the unified deployment with SQLite and went through the same loop (upgraded to 2024.1.0-beta and then back to 2023.12.0-beta). Today I tried the latest beta (which I assume is 2024.1.1) and everything works flawlessly. I can log in and edit entries, and there are no errors in the logs!

[averkiev]

Upgrading to 2024.1.1 has fixed the issue for me.

[brambaars]

Glad it's fixed for Sqlite!
I keep getting MySQL errors. I'll try a clean install...