github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Production NitroJS auth methods not working with Prisma #297

New Issue
Closed
opened 2026-03-13 07:41:10 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 07:41:10 -05:00
Owner
Copy Link

Originally created by @BayBreezy on GitHub (Nov 28, 2024).

Describe the bug
After building my project and running it in production mode, I keep getting the error below:

Invalid prisma.verification.create() invocation:

The table main.verification does not exist in the current database.

[Better Auth]  ERROR   If you are seeing this error, it is likely that you need to run the migrations for the database or you need to update your database schema. If you recently updated the package, make sure to run the migrations.

AND

Better Auth
Invalid prisma.user.findFirst() invocation:

The table main.user does not exist in the current database.

[Better Auth]  ERROR   If you are seeing this error, it is likely that you need to run the migrations for the database or you need to update your database schema. If you recently updated the package, make sure to run the migrations.

I tried performing the actions in the error

  • run the generate command: npx @better-auth/cli generate --config ./server/utils/auth.ts
  • run the generate for prisma: npx prisma generate
  • sync prisma: npx prisma db push

The issue is that this error does not happen during development. only after I run the build command and run it in production mode.

Expected behavior
I expect the auth endpoints to behave the same way in production as they do in dev mode

Screenshots
N/A

Desktop (please complete the following information):

  • OS: MacBook Pro
  • Chip: Apple M3 Pro
  • Browser: Arc
  • Version: 15.1.1

Smartphone (please complete the following information):
N/A

Additional context

Everything works fine during dev. The production version is where the issue is

Originally created by @BayBreezy on GitHub (Nov 28, 2024). **Describe the bug** After building my project and running it in production mode, I keep getting the error below: ```sh Invalid prisma.verification.create() invocation: The table main.verification does not exist in the current database. [Better Auth] ERROR If you are seeing this error, it is likely that you need to run the migrations for the database or you need to update your database schema. If you recently updated the package, make sure to run the migrations. ``` AND ```sh Better Auth Invalid prisma.user.findFirst() invocation: The table main.user does not exist in the current database. [Better Auth] ERROR If you are seeing this error, it is likely that you need to run the migrations for the database or you need to update your database schema. If you recently updated the package, make sure to run the migrations. ``` I tried performing the actions in the error - run the generate command: `npx @better-auth/cli generate --config ./server/utils/auth.ts` - run the generate for prisma: `npx prisma generate` - sync prisma: `npx prisma db push` The issue is that this error does not happen during development. only after I run the build command and run it in production mode. **Expected behavior** I expect the auth endpoints to behave the same way in production as they do in dev mode **Screenshots** N/A **Desktop (please complete the following information):** - OS: MacBook Pro - Chip: Apple M3 Pro - Browser: Arc - Version: 15.1.1 **Smartphone (please complete the following information):** N/A **Additional context** Everything works fine during dev. The production version is where the issue is
GiteaMirror commented 2026-03-13 07:41:11 -05:00
Author
Owner
Copy Link

@BayBreezy commented on GitHub (Nov 28, 2024):

So after a little more digging. I realised that the issue is with the sqlite type DB.

After I changed to mysql, the production build worked.

@BayBreezy commented on GitHub (Nov 28, 2024): So after a little more digging. I realised that the issue is with the `sqlite` type DB. After I changed to `mysql`, the production build worked.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#297
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?