Bug: API Key creation fails: "configId does not exist in apikey Drizzle schema" (better-auth api-key@1.5.4)

[Mheaus]

To Reproduce

1. install last version
2. create api key

Current vs. Expected behavior

Creating an api key should work

Provide environment information

Operating System:

• OS: Ubuntu 24.04 LTS
• Arch: amd64

Dokploy version: 0.28.7

VPS Provider: Scaleway

What applications/services are you trying to deploy? — N/A

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Both

Additional context

Bug

When trying to create an API key via Settings → API Keys, the following error is returned:

The field "configId" does not exist in the "apikey" Drizzle schema.
Please update your drizzle schema or re-generate using "npx auth@latest generate".

Root cause

@better-auth/api-key@1.5.4 (added in #3969) requires a configId column
in the apikey table, but the Dokploy Drizzle schema (packages/server/src/db/schema/account.ts)
was not updated to include this field.

The drizzle adapter validates all fields it tries to insert against the Drizzle
schema at runtime, and throws if a field is missing.

Fix

Add configId: text("configId") to the apikey table definition + matching migration.

Will you send a PR to fix it?

Yes

[dosubot]

Hi @Mheaus! I'm Dosu and I’m helping the dokploy team.

This is a known issue affecting Dokploy 0.28.7. Your root cause analysis is correct — PR #3969 upgraded better-auth to v1.5.4 but didn't include the database migration for the new configId column that the library now expects.

The current apikey table schema is indeed missing this field.

Workaround for affected users is to roll back to v0.28.6:

export DOKPLOY_VERSION=v0.28.6 && curl -sSL https://dokploy.com/install.sh | sh -s update

Looking forward to your PR with the fix!

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.