Langfuse not working

[hkrpydev-hkr]

Describe your question

With reference to this thread - Security vulnerability in Langfuse docker images with Node related packages · langfuse · Discussion… , we upgraded the self hosted Langfuse web and worker images to 3.143.0 and we have below versions in associated DB
clickhouse - 8.0.5
valkey - 2.2.4
postgres - 16.4.9

But we are seeing error in this upgraded Langfuse stack, which is given below. How do we address this error and get the Langfuse stack working as expected?

Raw query failed. Code: 42703. Message: column di.valid_from does not exist │
│ 2026-01-30T14:40:49.670Z error middleware intercepted error with code INTERNAL_SERVER_ERROR │
│ 2026-01-30T14:40:49.671Z error tRPC route failed on datasets.datasetItemsBasedOnTraceOrObservation: Internal error. Please check error logs in your self-hosted deployment. Internal │
│ TRPCError: Internal error. Please check error logs in your self-hosted deployment. │
│ at /app/web/.next/server/chunks/9739.js:1:13232 │
│ at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-DGaJyg8t.mjs:256:18) │
│ at async file:///app/node_modules/.pnpm/@baselime+trpc-opentelemetry-middleware@0.1.2_@opentelemetry+api@1.9.0_@trpc+server@11.8.0_typescript@5.9.2_/node_modules/@baselime/trpc-ope │
│ at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-DGaJyg8t.mjs:256:18) │
│ at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-DGaJyg8t.mjs:256:18) │
│ at async procedure (file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-DGaJyg8t.mjs:281:18) │
│ at async file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/resolveResponse-D7zvnoIM.mjs:1948:18 │
│ at async resolveResponse (file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/resolveResponse-D7zvnoIM.mjs:1973:28) │
│ at async file:///app/node_modules/.pnpm/@trpc+server@11.8.0_typescript@5.9.2/node_modules/@trpc/server/dist/node-http-Cd7-CwtL.mjs:201:22 │
│ 2026-01-30T14:40:53.747Z error prisma:error │
│ Invalid prisma.$queryRaw() invocation:

Langfuse Cloud or Self-Hosted?

Self-Hosted

If Self-Hosted

3.143.0

If Langfuse Cloud

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[inkeep-ai-assistant[bot]]

The error column di.valid_from does not exist indicates a database migration issue. This typically occurs when the ClickHouse schema is not properly synchronized with the application version you're running.

Based on the error pattern and your upgrade scenario, here are the steps to address this:

1. Verify Database Migrations Completed Successfully

Check if all background migrations have completed. The valid_from column is part of ClickHouse schema updates that should be applied during migration.

2. Check Migration Status

Examine your Langfuse logs during startup to confirm all database migrations (both PostgreSQL and ClickHouse) completed without errors. Look for migration-related log entries.

3. Review ClickHouse Version Compatibility

You're running ClickHouse 8.0.5, which is significantly newer than typical deployment versions. While this shouldn't cause issues, verify that your ClickHouse instance is accessible and properly configured.(1)

4. Common Resolution Steps

• Ensure the worker container has completed all background migrations before the web container attempts to query data
• Check that LANGFUSE_AUTO_POSTGRES_MIGRATION_DISABLED is not set to true (unless you're manually managing migrations)(1)
• Verify your DATABASE_URL and ClickHouse connection strings are correctly configured(1)

5. Migration Troubleshooting

If migrations appear stuck or failed, check the troubleshooting resources for handling failed ClickHouse migrations.(2)

For additional support with this specific migration issue, I recommend posting in the Langfuse GitHub Discussions with your full error logs and migration status, as this appears to be a schema synchronization issue specific to your upgrade path.

📚 Sources:

1. Deployment Guide (v2)
2. Troubleshooting & FAQ

---

Have another question? Just tag @inkeep.

[jannikmaierhoefer]

Hi @hkrpydev-hkr, was inkeep able to help you here?