goblin7024•13mo ago

Langfuse on Cloud Run

Had someone tried deploy langfuse on Google cloud run yet? I faced a problem on deploying it to cloud run. It shows error like this below.

TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11576:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
Open in Logs Explorer
{
severity: "ERROR"
textPayload: "TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections

TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11576:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
Open in Logs Explorer
{
severity: "ERROR"
textPayload: "TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections

Any thought on this?

19 Replies

goblin7024•13mo ago

Max•13mo ago

We have never seen this issue. Which host did you configure for the langchain SDK?

Harden君•13mo ago

We were mainly following this https://langfuse.com/docs/deployment/self-host Was there a place to configure host for langchain SDK?

Self-Hosting Instructions - Langfuse

Langfuse is open source and can be self-hosted in your own infrastructure via Docker

Harden君•13mo ago

DATABASE_URL=postgresql://postgres:{pass}@{db-ip}:5432/postgres
NEXTAUTH_SECRET={secret}
NEXTAUTH_URL=http://localhost:3000

DATABASE_URL=postgresql://postgres:{pass}@{db-ip}:5432/postgres
NEXTAUTH_SECRET={secret}
NEXTAUTH_URL=http://localhost:3000

We are using this env on cloud run btw

Max•13mo ago

The SDKs have their own configs for hosts: JS (https://langfuse.com/docs/integrations/sdk/typescript#options) and Python (https://langfuse.com/docs/integrations/sdk/python#options)

Python SDK - Langfuse

Fully async and typed Python SDK. Uses Pydantic objects for data verification.

JS/TS SDK - Langfuse

Fully async and typed SDK, runs in Node.js, edge, Deno

Max•13mo ago

Sorry i misunderstood you. These are logs from the Langfuse container?

Harden君•13mo ago

These are logs from Cloud Run

Harden君•13mo ago

Although we do see one message from Langfuse container

Max•13mo ago

Does the error occurr immediately on startup or when you do something like loading the page, logging in, sending events via the SDK?

Harden君•13mo ago

This is a final error message after the startup fails.

Marc•13mo ago

Can you try to pull the latest container? I published an update a couple of hours ago The update could fix this

Harden君•13mo ago

Still same error

Marc•13mo ago

I'll give it a try later Do you have any more data that helps to reproduce the problem?

goblin7024•13mo ago

One more thing is we are using cloud sql to serve as a postgresql.

Marc•13mo ago

Created an issue for this: https://github.com/langfuse/langfuse/issues/195

GitHub

[LFC-188] bug: Container failed to start and listen on Port 3000 (G...

Describe the bug To reproduce Run langfuse container on Google Cloud Run Additional information Optional: Add cloud run instructions to docs LFC-188