Issues with self-hosted setup #16437
Describe your questionI follow https://langfuse.com/self-hosting/deployment/docker-compose exactly, I wanted until everything was ready and locahost:3000 returns a 404 Langfuse Cloud or Self-Hosted?Self-Hosted If Self-HostedIf Langfuse CloudNo response SDK and integration versionsNo response Pre-Submission Checklist
|
Replies: 1 comment
|
A few things to check with the Docker Compose setup. First, make sure the startup actually completed. After Second, confirm you started from a clean clone and the standard compose file: Third, if you set a base path in your environment, that would change where the UI is served from. You can also verify the server itself is responding independently of the UI route: A If you want to start over cleanly, stop everything (adding Also worth confirming the host has enough disk space, as that has been a source of failures in compose deployments.(1)(3) I don't have enough detail in the available sources to diagnose your specific log output. If this persists, the maintainers on GitHub Discussions are the right place, and the Troubleshooting & FAQ page covers additional self-hosting issues.(1) Let me know if you'd like me to walk through a general debugging approach instead. 📚 Sources:
Have another question? Just tag @inkeep. |
A few things to check with the Docker Compose setup.
First, make sure the startup actually completed. After
docker compose up, it takes about 2-3 minutes before thelangfuse-web-1container logs "Ready" — only at that point is the UI available athttp://localhost:3000.(1)Second, confirm you started from a clean clone and the standard compose file:
(1)
(1)
Third, if you set a base path in your environment, that would change where the UI is served from.
NEXT_PUBLIC_BASE_PATHsets the base path for the application, which is used when deploying Langfuse on a subpath.(2)You can also verify the server itself is…