After upgrading to version 3.6 from 3.5 login through GitHub is not working
I have only login through GitHub enabled on my self-hosted Typebot. After upgrading to version 3.6 from 3.5, I am not able to login any longer. The moment I click the Continue with GitHub button I see a Try signing with a different account message under the button and I am not redirected to GitHub for the sign-in. I can see the following errors displayed in my Docker logs:
2025-04-19T09:21:34.214718141Z The column
User.preferredLanguage does not exist in the current database.
2025-04-19T09:21:34.214721151Z at In.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6854)
2025-04-19T09:21:34.214724181Z at In.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6188)
2025-04-19T09:21:34.214727161Z at In.request (/app/node_modules/@prisma/client/runtime/library.js:122:5896)
2025-04-19T09:21:34.214730111Z at async l (/app/node_modules/@prisma/client/runtime/library.js:127:11167)
2025-04-19T09:21:34.214733041Z at async getUserByAccount (/app/apps/builder/.next/server/chunks/256.js:1:4019) {
2025-04-19T09:21:34.214736021Z name: 'GetUserByAccountError',
2025-04-19T09:21:34.214738961Z code: 'P2022'
2025-04-19T09:21:34.214748391Z }
Any help with this matter will be greatly appreciated.2 Replies
After restarting the Typebot container once again I can see the following logs:
2025-04-19T15:05:42.364694140Z Prisma schema loaded from packages/prisma/postgresql/schema.prisma
2025-04-19T15:05:42.404052419Z Datasource "db": PostgreSQL database "tsltypebotdb", schema "public" at "srv-captain--db"
2025-04-19T15:05:42.617907113Z
2025-04-19T15:05:42.618310247Z 74 migrations found in prisma/migrations
2025-04-19T15:05:42.621062522Z
2025-04-19T15:05:42.675714474Z Error: P3009
2025-04-19T15:05:42.675728783Z
2025-04-19T15:05:42.675732353Z migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
2025-04-19T15:05:42.675735673Z The
20250303175555_add_preferred_language migration started at 2025-04-19 09:16:09.231088 UTC failed
2025-04-19T15:05:42.675738743Z
2025-04-19T15:05:42.675741573Z
2025-04-19T15:05:43.539854041Z ▲ Next.js 14.2.13
2025-04-19T15:05:43.540495820Z - Local: http://localhost:3000
2025-04-19T15:05:43.540673227Z - Network: http://0.0.0.0:3000
2025-04-19T15:05:43.540885823Z
2025-04-19T15:05:43.541208638Z ✓ Starting...
2025-04-19T15:05:46.119327196Z ✓ Ready in 2.6s
I hope the above gives more clarity.Patching & hotfixing | Prisma Documentation
How to reconcile the migration history after applying a hotfix or patch to a production environment.
I was able to resolve this issue and am putting the solution here just in case someone else is in the same situation. In my case the Postgres database is a shared one and the user specified in the database connection string for Typebot did not have the rights to alter tables. I fixed this issue, rolled back the earlier Prisma migration and on restarting the container the migration succeeded. I am now able to sign-in successfully.