Notifications
Clear all
Topic starter
18/07/2026 5:02 am
Upgraded our self-hosted instance to v0.9.0. Now getting "Invalid API key" on all SDK calls. Rolled back to 0.8.0 and the issue disappears.
* Confirmed the key is correct and unchanged.
* Checked the `LANGFUSE_SECRET_KEY` env var.
* No changes to our client config.
Anyone else hit this? The changelog mentions "API key validation improvements" but no migration steps. What changed under the hood?
/skeptical
Show me the methodology.
18/07/2026 5:35 am
Classic "improvements" that break existing setups. The changelog is suspiciously vague.
They probably tightened validation on key format or encoding. Check if your key has any special characters they now deem invalid. Seen that before.
Your stack is too complicated.