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

[GH-ISSUE #364] LibsqlDialect doesn't work with encryptionKey option #16867

New Issue
Closed
opened 2026-04-15 14:51:20 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-15 14:51:20 -05:00
Owner
Copy Link

Originally created by @MurkyTheMurloc on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/364

Describe the bug
When using better-auth with LibsqlDialect and enabling the encryptionKey option, an SQLITE_NOTADB error occurs. Disabling the encryptionKey option resolves the issue, but this disables encryption, which may be necessary in some use cases.

To Reproduce
Steps to reproduce the behavior:

  1. Configure better-auth to use a SQLite database.
  2. Set up LibsqlDialect with the following configuration: 
    const dialect = new LibsqlDialect({
    url: "file:./auth/auth.db",
    syncUrl: process.env.TURSO_DATABASE_URL,
    authToken: process.env.TURSO_AUTH_TOKEN,
    syncInterval: 60,
    encryptionKey: process.env.ENCRYPTION_KEY,  // Enable encryption key
});
  3. Attempt to call auth.api.signUpEmail()
  4. See error: 
    {
  "code": "SQLITE_NOTADB",
  "rawCode": 26,
  "name": "LibsqlError"
}

Expected behavior
The database should be accessed without errors when encryptionKey is specified.

Screenshots
N/A

Desktop (please complete the following information):

  • OS: macOS
  • Node.js version: 22.6.0
  • better-auth version: 0.6.2
  • SQLite version: latest

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

Additional context
The issue may relate to how better-auth interacts with SQLite encryption, or it may stem from a misconfiguration. Documentation or clarification on supported encryption setups would be helpful.

Originally created by @MurkyTheMurloc on GitHub (Oct 29, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/364 **Describe the bug** When using `better-auth` with `LibsqlDialect` and enabling the `encryptionKey` option, an `SQLITE_NOTADB` error occurs. Disabling the `encryptionKey` option resolves the issue, but this disables encryption, which may be necessary in some use cases. **To Reproduce** Steps to reproduce the behavior: 1. Configure `better-auth` to use a SQLite database. 2. Set up `LibsqlDialect` with the following configuration: ```javascript const dialect = new LibsqlDialect({ url: "file:./auth/auth.db", syncUrl: process.env.TURSO_DATABASE_URL, authToken: process.env.TURSO_AUTH_TOKEN, syncInterval: 60, encryptionKey: process.env.ENCRYPTION_KEY, // Enable encryption key }); 3. Attempt to call `auth.api.signUpEmail()` 4. See error: ```json { "code": "SQLITE_NOTADB", "rawCode": 26, "name": "LibsqlError" } **Expected behavior** The database should be accessed without errors when `encryptionKey` is specified. **Screenshots** N/A **Desktop (please complete the following information):** - OS: macOS - Node.js version: 22.6.0 - better-auth version: 0.6.2 - SQLite version: latest **Smartphone (please complete the following information):** N/A **Additional context** The issue may relate to how `better-auth` interacts with SQLite encryption, or it may stem from a misconfiguration. Documentation or clarification on supported encryption setups would be helpful.
GiteaMirror added the lockedbug labels 2026-04-15 14:51:20 -05:00
GiteaMirror commented 2026-04-15 14:51:21 -05:00
Author
Owner
Copy Link

@MurkyTheMurloc commented on GitHub (Oct 29, 2024):

const auth = betterAuth({
  emailAndPassword: {
    enabled: true,
  },
  database: {
    dialect: dialect,
    type: "sqlite",
  },
  plugins: [
    admin(),
    organization({
      ac: ac,
      roles: {
        member,
      },
    }),
  ],
});```
<!-- gh-comment-id:2444310121 --> @MurkyTheMurloc commented on GitHub (Oct 29, 2024): ```javascript const auth = betterAuth({ emailAndPassword: { enabled: true, }, database: { dialect: dialect, type: "sqlite", }, plugins: [ admin(), organization({ ac: ac, roles: { member, }, }), ], });```
GiteaMirror commented 2026-04-15 14:51:21 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 17, 2024):

We don’t have direct interaction with the underlying implementation of the LibSQL dialect for Kysely. I’m not sure if encryption requires a different configuration with Kysely, but if it does, feel free to open another issue mentioning that. But, this seems like a problem with the Kysely dialect itself rather than Better Auth. If the issue is due to misconfiguration on our end, feel free to open another issue.

<!-- gh-comment-id:2547837625 --> @Bekacru commented on GitHub (Dec 17, 2024): We don’t have direct interaction with the underlying implementation of the LibSQL dialect for Kysely. I’m not sure if encryption requires a different configuration with Kysely, but if it does, feel free to open another issue mentioning that. But, this seems like a problem with the Kysely dialect itself rather than Better Auth. If the issue is due to misconfiguration on our end, feel free to open another issue.
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 bug locked
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#16867
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?