Just Updated to the latest version and now i get this error when trying to connect:
2026-01-24T05:12:50+00:00 [error]: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | Stack: SqliteError: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin | at BetterSQLiteSession.prepareQuery (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:23:30)
pangolin | at BetterSQLiteSession.prepareOneTimeQuery (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:141:17)
pangolin | at SQLiteSelectBase._prepare (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:615:88)
pangolin | at SQLiteSelectBase.all (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:641:17)
pangolin | at SQLiteSelectBase.execute (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:650:17)
pangolin | at SQLiteSelectBase.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {"code":"SQLITE_ERROR"}
Environment
OS Type & Version: Win 25H2 / Pangolin Server is Debian 12 LXC
Pangolin Version: 1.15.0
Gerbil Version: 1.3.0
Traefik Version: 3.6.7
Newt Version: 1.9.0 and one old 1.8.1
Olm Version: /
To Reproduce
Updated to the latest Version after the RC Update.
Trying to connect a Client fails with those logs.
Expected Behavior
Client should connect, populate the new Security Fields.
Originally created by @Sebuschka on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2313
### Describe the Bug
Just Updated to the latest version and now i get this error when trying to connect:
2026-01-24T05:12:50+00:00 [error]: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | Stack: SqliteError: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin | at BetterSQLiteSession.prepareQuery (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:23:30)
pangolin | at BetterSQLiteSession.prepareOneTimeQuery (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:141:17)
pangolin | at SQLiteSelectBase._prepare (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:615:88)
pangolin | at SQLiteSelectBase.all (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:641:17)
pangolin | at SQLiteSelectBase.execute (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:650:17)
pangolin | at SQLiteSelectBase.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {"code":"SQLITE_ERROR"}
### Environment
- OS Type & Version: Win 25H2 / Pangolin Server is Debian 12 LXC
- Pangolin Version: 1.15.0
- Gerbil Version: 1.3.0
- Traefik Version: 3.6.7
- Newt Version: 1.9.0 and one old 1.8.1
- Olm Version: /
### To Reproduce
Updated to the latest Version after the RC Update.
Trying to connect a Client fails with those logs.
### Expected Behavior
Client should connect, populate the new Security Fields.
@oschwartz10612 commented on GitHub (Jan 24, 2026):
Unfortunately we do not support migrating from a RC to a normal release.
You will need to go back to 1.14 and then upgrade to 1.15. I am sorry!
<!-- gh-comment-id:3795382719 -->
@oschwartz10612 commented on GitHub (Jan 24, 2026):
Unfortunately we do not support migrating from a RC to a normal release.
You will need to go back to 1.14 and then upgrade to 1.15. I am sorry!
Hi thanks for the response. I restoed the db from the Backup before RC. Did a docker restart and it did the migration without a problem. Devices are online again. Thanks for the help :)
<!-- gh-comment-id:3795527911 -->
@Sebuschka commented on GitHub (Jan 24, 2026):
Hi thanks for the response. I restoed the db from the Backup before RC. Did a docker restart and it did the migration without a problem. Devices are online again. Thanks for the help :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Sebuschka on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2313
Describe the Bug
Just Updated to the latest version and now i get this error when trying to connect:
2026-01-24T05:12:50+00:00 [error]: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | Stack: SqliteError: no such column: currentFingerprint.windowsAntivirusEnabled
pangolin | at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin | at BetterSQLiteSession.prepareQuery (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:23:30)
pangolin | at BetterSQLiteSession.prepareOneTimeQuery (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:141:17)
pangolin | at SQLiteSelectBase._prepare (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:615:88)
pangolin | at SQLiteSelectBase.all (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:641:17)
pangolin | at SQLiteSelectBase.execute (file:///app/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:650:17)
pangolin | at SQLiteSelectBase.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {"code":"SQLITE_ERROR"}
Environment
To Reproduce
Updated to the latest Version after the RC Update.
Trying to connect a Client fails with those logs.
Expected Behavior
Client should connect, populate the new Security Fields.
@oschwartz10612 commented on GitHub (Jan 24, 2026):
Unfortunately we do not support migrating from a RC to a normal release.
You will need to go back to 1.14 and then upgrade to 1.15. I am sorry!
@Sebuschka commented on GitHub (Jan 24, 2026):
Hi thanks for the response. I restoed the db from the Backup before RC. Did a docker restart and it did the migration without a problem. Devices are online again. Thanks for the help :)