p5 Comments - Langfuse

Thanks for fixing that! We've upgraded to v1.3.0 and re-enabled telemetry. Everything seems to be working again 🎉 (Side note: Love the database migration system btw. We don't even need to know something's changing)

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

No worries at all. If you let us know when there's a fix, we'd be happy to re-enable telemetry on our instance

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

Ah, so the telemetry sends information about the usage (e.g. number of resources) to Posthog so the Langfuse team can look at how many people are using it. It's not essential for running Langfuse, but helps the maintainers.

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

Great! That does seem to have fixed it! The container has been running for 8 minutes now without issues! :rubber_duck: Would still like to know this though:

If we disable the telemetry, how will it affect the functionality of the service?

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

Looking into the codebase, the most likely thing to be causing this is the telemetry. The container will not be reachable by it's internal IP. Trying to disable this. If we disable this, how will this affect the functionality of the service?

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

Port 3000 is being exposed to the load balancer, and we are accessing the load balancer on 443 - this is working fine.
Just the errors in the log is causing the task to constantly fail and be recreated

21 replies

LLangfuse

•Created by p5 on 11/19/2023 in #self-host-discussion

Hope someone can help us out here. We'

Error:

2023-11-19T14:50:38.432+00:00    Prisma schema loaded from prisma/schema.prisma
2023-11-19T14:50:38.539+00:00    Datasource "db": PostgreSQL database "langfuse", schema "public" at "langfuse.testing.<REDACTED>:5432"
2023-11-19T14:50:39.041+00:00    65 migrations found in prisma/migrations
2023-11-19T14:50:39.244+00:00    No pending migrations to apply.
2023-11-19T14:50:43.548+00:00    ▲ Next.js 13.5.6
2023-11-19T14:50:43.549+00:00    - Local: http://ip-10-64-101-126.eu-west-1.compute.internal:3000
2023-11-19T14:50:43.549+00:00    - Network: http://10.64.101.126:3000
2023-11-19T14:50:43.549+00:00    ✓ Ready in 2s
2023-11-19T14:55:00.233+00:00    TypeError: fetch failed
2023-11-19T14:55:00.233+00:00    at Object.fetch (node:internal/deps/undici/undici:11372:11)
2023-11-19T14:55:00.233+00:00    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
2023-11-19T14:55:00.233+00:00    cause: Error: connect ECONNREFUSED 169.254.172.2:3000
2023-11-19T14:55:00.233+00:00    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
2023-11-19T14:55:00.233+00:00    errno: -111,
2023-11-19T14:55:00.233+00:00    code: 'ECONNREFUSED',
2023-11-19T14:55:00.233+00:00    syscall: 'connect',
2023-11-19T14:55:00.233+00:00    address: '169.254.172.2',
2023-11-19T14:55:00.233+00:00    port: 3000
2023-11-19T14:55:00.233+00:00    }
2023-11-19T14:55:00.233+00:00    }

2023-11-19T14:50:38.432+00:00    Prisma schema loaded from prisma/schema.prisma
2023-11-19T14:50:38.539+00:00    Datasource "db": PostgreSQL database "langfuse", schema "public" at "langfuse.testing.<REDACTED>:5432"
2023-11-19T14:50:39.041+00:00    65 migrations found in prisma/migrations
2023-11-19T14:50:39.244+00:00    No pending migrations to apply.
2023-11-19T14:50:43.548+00:00    ▲ Next.js 13.5.6
2023-11-19T14:50:43.549+00:00    - Local: http://ip-10-64-101-126.eu-west-1.compute.internal:3000
2023-11-19T14:50:43.549+00:00    - Network: http://10.64.101.126:3000
2023-11-19T14:50:43.549+00:00    ✓ Ready in 2s
2023-11-19T14:55:00.233+00:00    TypeError: fetch failed
2023-11-19T14:55:00.233+00:00    at Object.fetch (node:internal/deps/undici/undici:11372:11)
2023-11-19T14:55:00.233+00:00    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
2023-11-19T14:55:00.233+00:00    cause: Error: connect ECONNREFUSED 169.254.172.2:3000
2023-11-19T14:55:00.233+00:00    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
2023-11-19T14:55:00.233+00:00    errno: -111,
2023-11-19T14:55:00.233+00:00    code: 'ECONNREFUSED',
2023-11-19T14:55:00.233+00:00    syscall: 'connect',
2023-11-19T14:55:00.233+00:00    address: '169.254.172.2',
2023-11-19T14:55:00.233+00:00    port: 3000
2023-11-19T14:55:00.233+00:00    }
2023-11-19T14:55:00.233+00:00    }

And some environment variables that may help:

NEXTAUTH_URL = https://<public-dns-of-application-load-balancer>
AUTH_DOMAINS_WITH_SSO_ENFORCEMENT = <domain-of-emails>
AUTH_GOOGLE_CLIENT_ID = <REDACTED>
AUTH_GOOGLE_CLIENT_SECRET = <REDACTED>
SALT = <REDACTED>
NEXTAUTH_SECRET = <REDACTED>
DATABASE_URL = <REDACTED>

NEXTAUTH_URL = https://<public-dns-of-application-load-balancer>
AUTH_DOMAINS_WITH_SSO_ENFORCEMENT = <domain-of-emails>
AUTH_GOOGLE_CLIENT_ID = <REDACTED>
AUTH_GOOGLE_CLIENT_SECRET = <REDACTED>
SALT = <REDACTED>
NEXTAUTH_SECRET = <REDACTED>
DATABASE_URL = <REDACTED>

21 replies

LLangfuse

•Created by p5 on 11/16/2023 in #self-host-discussion

SSO-only mode

Will try and rework it to use the AUTH_ALLOWED_SSO_DOMAINS_ONLY suggestion

10 replies

LLangfuse

•Created by p5 on 11/16/2023 in #self-host-discussion

SSO-only mode

That looks like exactly what we need. I attempted something in this PR, but I may need guidance to validate everything is working as expected, and if I have done the right thing to begin with. https://github.com/langfuse/langfuse/pull/510

10 replies

LLangfuse

•Created by p5 on 11/16/2023 in #self-host-discussion

SSO-only mode

Thanks for the guidance. Will try enforcing SSO for my domain, and maybe later on implementing the SSO-only feature flag.

10 replies