Brijesh
Brijesh
PostsComments
LLangfuse
Created by Brijesh on 1/17/2024 in #self-host-discussion
Hi,
The issue was with the networks the containers were in. Once I created a new network and added both containers to same network, it started working. Thanks for your help @Bryan .
9 replies
LLangfuse
Created by Brijesh on 1/17/2024 in #self-host-discussion
Hi,
My password and username also don't contain any special characters, which was apparently an issue with prisma for some people.
9 replies
LLangfuse
Created by Brijesh on 1/17/2024 in #self-host-discussion
Hi,
Replacing it with my postgres image name (postgresdb) did not help, I got the same issue. I just ran the original postgres-alpine image with the below config, as such I didn't have to write a docker compose file. 
docker run -d   --name postgresdb   \
-e POSTGRES_USER=<username>   \
-e POSTGRES_PASSWORD=<password>   \
-e POSTGRES_DB=langfuse   \
-v langfuse-db:/var/lib/postgresql/data   \
-p 5432:5432   postgres:13.8-alpine
docker run -d   --name postgresdb   \
-e POSTGRES_USER=<username>   \
-e POSTGRES_PASSWORD=<password>   \
-e POSTGRES_DB=langfuse   \
-v langfuse-db:/var/lib/postgresql/data   \
-p 5432:5432   postgres:13.8-alpine
After running the postgres db, I ran the following command to get langfuse up. 
docker run --name langfuse \
-e DATABASE_URL=postgresql://<username>:<password>@postgresdb:5432/langfuse \
-e NEXTAUTH_URL=<url> \
-e NEXTAUTH_SECRET=<secret> \
-e SALT=<secret-2> \
-p 80:3000 \
-a STDOUT \
ghcr.io/langfuse/langfuse:latest
docker run --name langfuse \
-e DATABASE_URL=postgresql://<username>:<password>@postgresdb:5432/langfuse \
-e NEXTAUTH_URL=<url> \
-e NEXTAUTH_SECRET=<secret> \
-e SALT=<secret-2> \
-p 80:3000 \
-a STDOUT \
ghcr.io/langfuse/langfuse:latest
This is my VM architecture info: Linux office-ml-training 6.1.0-17-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
9 replies
LLangfuse
Created by Brijesh on 1/17/2024 in #self-host-discussion
Hi,
Yes, I'm running it on a single VM.
9 replies