[Bug]: Fail to save MCP configuration as API key is too long

[ddwong1984]

What happened?

Fail to save MCP configuration as it return API key is too long

Version Information

v0.8.7

Steps to Reproduce

1. Click create new MCP in the WebUI
2. Select API Key in Authentication
3. Insert a long API Key
4. Click Create

What browsers are you seeing the problem on?

No response

Relevant log output

2026-08-07 03:22:47 error: [ServerConfigsDB.encryptConfig] Failed to encrypt apiKey.key Invalid key length {"userId":"6a743afa96222d8c96288e07"}
2026-08-07 03:22:47 error: [updateMCPServer] Failed to encrypt MCP server configuration {"userId":"6a743afa96222d8c96288e07"}

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[lidonius1122]

Hi @ddwong1984 — this isn't caused by the length of your API key. The Invalid key length in the log refers to your server's CREDS_KEY environment variable (the encryption key), which doesn't seem to be a valid 64-character hex string.

Fix: generate a proper key with openssl rand -hex 32 (or the creds generator), set it as CREDS_KEY in your .env, and restart. Heads-up: changing CREDS_KEY invalidates any previously encrypted credentials.

Same error signature as #4276, which turned out to be the same misconfiguration.