API Keys not working and unbale to generate new ones after Upgrade to 0.28.7

[Morgan-SL-PUP]

To Reproduce

1. Try to use an existing API Key
2. Returns 401 Unauthorized
3. Trying to generate new API Key even as Owner
4. Returns "Failed to generate API Key"

Current vs. Expected behavior

Current Behaviour:

API Keys not working and unable to generate new ones

Expected Behaviour:

API Keys should continue to work

Provide environment information

Dokploy Version: 0.28.7

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

Application

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

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

[dosubot]

This issue is likely related to the better-auth update in PR #3969 which made significant changes to API Key handling, including updating dependencies and refactoring to use a separate @better-auth/api-key package. This could cause existing API Keys to fail validation.

Quick fix to try first: Make sure you're using the correct header format. The API requires x-api-key (not Authorization: Bearer):

curl -X 'GET' 'https://your-domain/api/project.all' \
  -H 'accept: application/json' \
  -H 'x-api-key: your_api_key'

This header issue has caused 401 errors for other users across multiple versions.

If that doesn't resolve your issue, the "Failed to generate API Key" error combined with the better-auth dependency changes suggests there may be a regression introduced in 0.28.7. Could you share any error logs from the Dokploy container that might help identify the root cause?

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Morgan-SL-PUP]

@dosu

The Header is correct.

There are no Error Logs from the Container.
The only Message you get in the UI is "Failed to Generate API Key"
Is there any other way to get extended Logs ?

[dosubot]

There are a few ways to get more detailed information:

1. Check Browser Developer Console (Most helpful here)

Since the error is showing in the UI with no backend logs, open your browser's Developer Tools (F12) and check:

• Network tab: Look for the failed request when clicking Generate API Key (should be a POST to /api/trpc/user.createApiKey). Check the response body for error details.
• Console tab: Look for any JavaScript errors

2. Enable Debug Logging

Dokploy's auth logging is disabled in production by default. To enable it:

docker service update dokploy --env-add NODE_ENV=development
docker service scale dokploy=0
docker service scale dokploy=1

Then check logs with:

docker service logs dokploy --follow

3. Check Database Container

The issue might be database-related. Check the PostgreSQL logs:

docker service logs dokploy-postgres

The Network tab response is probably the quickest way to identify what's actually failing—can you share what error it returns?

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Morgan-SL-PUP]

@dosu

1. The Browser shows a Post Request to /api/trpc/user.createApiKey?batch=1, but it returns an 500 Error Code.

2. The Dokploy Service is not starting anymore after adding the Env Variable so I cant get Information from there

3. The Database Container doesnt show errors

[dosubot]

A 500 error indicates a server-side issue—this is helpful for narrowing down the problem.

First, fix the service startup issue by removing the environment variable:

docker service update --env-rm NODE_ENV dokploy

The service will restart automatically after this.

Then check the logs for the actual error causing the 500:

docker service logs dokploy --tail 100

Also, can you check the response body of that 500 error in your browser's Network tab? Click on the failed request and look at the "Response" or "Preview" tab—there's often an error message there that would help identify whether this is a database issue, a better-auth library error, or something else.

This 500 on API key creation after the 0.28.7 upgrade combined with the better-auth changes in that release suggests there may be a regression that needs to be reported upstream once we can identify the specific error.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Morgan-SL-PUP]

@dosu

The 500 Request Respond contains the following as the Body:

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

[dosubot]

This confirms the issue! The error is caused by an incomplete database migration in version 0.28.7.

PR #3969 updated the better-auth library to version 1.5.4 which expects a configId field in the apikey table, but the actual database schema doesn't include this field—it still uses the old userId-based structure.

This is a regression bug in 0.28.7. The better-auth dependency was updated but the corresponding database migration wasn't included, so API key creation is broken for everyone on this version.

Unfortunately, there's no user-side workaround for this since it requires a code fix. The maintainers will need to either:

1. Add the missing database migration for configId, or
2. Revert/adjust the better-auth configuration to match the existing schema

This issue is well-documented here now—hopefully a fix can be released soon. In the meantime, if you need API access urgently, you might consider rolling back to 0.28.6 if that's feasible for your setup.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[ogroendal]

I also just installed the newest version of dokploy and ran into this exact issue with the same error in the http response: [{"error":{"json":{"message":"The field "configId" does not exist in the "apikey" Drizzle schema. Please update your drizzle schema or re-generate using "npx auth@latest generate".","code":-32603,"data":{"code":"INTERNAL_SERVER_ERROR","httpStatus":500,"path":"user.createApiKey","zodError":null}}}}]

Maybe - it would make sense to roll back the latest stable release to the previous one, so that the install script dont serve this issue to people?

[Pop478]

I had to rollback to the previous version to restore functionality:

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

After downgrade:
API keys work again