Can not upload media using self-host server

TL;DR

Self-hosted Langfuse (docker compose): media uploads fail with TRPCError: Media not yet uploaded even though MinIO is up and the console is reachable. No media folder appears in the bucket.

Steps

1. Self-hosted Langfuse (docker compose): media uploads fail with TRPCError: Media not yet uploaded even though MinIO is up and the console is reachable.
2. No media folder appears in the bucket.

When to use

You are seeing this: No media folder appears in the bucket. Use this skill when you run into "Can not upload media using self-host server".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Note: images on private IPs still don't render inline due to the site's Content Security Policy (clicking the link works); HTTPS URLs render fine.

In gh:langfuse/langfuse#6188 (https://github.com/langfuse/langfuse/issues/6188), the question was: Self-hosted Langfuse (docker compose): media uploads fail with TRPCError: Media not yet uploaded even though MinIO is up and the console is reachable. No media folder appears in the bucket. The verified resolution: Reporter solved it (reporter, Seraphli) by setting LANGFUSES3MEDIAUPLOADENDPOINT in the langfuse-web container's environment, not just in the SDK app, e.g. setting LANGFUSE_S3_MEDIA_UPLOAD_ENDPOINT to the local MinIO URL (YOUR_HOST, port 9090) for local compose, or the actual LAN IP when the UI is viewed from another machine.