-
Describe your questionI'm using the helm chart to deploy langfuse along with ClickHouse this way: And a YAML template file containing: However
I'm a bit puzzled as to why, as I'm using the helm chart to deploy ClickHouse and declare environment variables in Langfuse's containers, in which I can see that the following are set:
I tried with adding a ClickHouse debug container next to langfuse-web, and was able to connect to the server using What could be wrong in Langfuse or my way to achieve this ? Thank you Langfuse Cloud or Self-Hosted?Self-Hosted If Self-Hosted3.147.0 If Langfuse CloudNo response SDK and integration versionsNo response Pre-Submission Checklist
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
The authentication error you're experiencing is likely due to a mismatch between the ClickHouse user credentials configured in your Helm deployment and what Langfuse expects.(1) According to the documentation, the ClickHouse user specified in GRANT INSERT ON default.* TO 'user';
GRANT SELECT ON default.* TO 'user';
GRANT ALTER UPDATE, ALTER DELETE ON default.* TO 'user';
GRANT CREATE ON default.* TO 'user';
GRANT DROP TABLE ON default.* TO 'user';The issue is that you're setting For a minimum production setup with the Bitnami ClickHouse Helm chart, the documentation recommends:(1) clickhouse:
deploy: true
shards: 1 # Fixed: Langfuse does not support multi-shard clusters
replicaCount: 3
resourcesPreset: large # or more
persistence:
size: 100Gi
auth:
username: default
password: changemeChange your Helm configuration to use Additionally, verify that your Langfuse environment variables match:(1) 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
I removed username in the template, it recreated the ClickHouse cluster but now: |
Beta Was this translation helpful? Give feedback.
-
|
Wow ok, the problem is the password. "plus" sign not url encoded I suppose 🤷 |
Beta Was this translation helpful? Give feedback.

Wow ok, the problem is the password. "plus" sign not url encoded I suppose 🤷
Changed this and it worked.