Langfuse self hosting issue in Internet facing

[abhayjain09]

We’ve hosted our Langfuse application on AWS ECS behind an Application Load Balancer (ALB). The setup works perfectly when the Application Load Balancer (ALB) is configured as internal (private), but when we switch it to an internet-facing ALB, the application becomes inaccessible from the browser — even though DNS resolution and CLI connectivity are working fine.

Could you please confirm if there are any specific environment variables, configuration settings, or network parameters required for Langfuse to operate correctly behind a public-facing ALB?

Appreciate your guidance on this.

[Steffen911]

Hey @abhayjain09,
No, the Langfuse deployment should be fully agnostic w.r.t to your networking setup and the ALB configuration. Can you call the Langfuse instance via cURL? And what issues do you observe when trying to open the URL from a browser?

Typical things would be:

• Certificate management
• Problematic security groups
• Route tables between public and private subnets.