Reverse Proxy Configuration for Traefik with Docker Compose #393
louisprp
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My StremThru + Traefik Setup (Direct-Link Only, Fully Locked Down)
I wanted to share a configuration I’ve been using to run StremThru behind Traefik with everything locked down by default. I intentionally block all public access and only expose the exact paths StremThru needs, and only when valid user data is provided. Since I’m relying on an upstream Torrentio instance configured with a Real-Debrid API token, all streams come through as direct links with cached RD sources. That means StremThru essentially works as a small multi-user password-protected proxy. It may be a bit overkill, but it’s been working very well.
One thing I’m not completely certain about is whether there are edge cases where StremThru might still accept requests with missing or empty userData, depending on how the decoding behaves internally.
If anyone (especially the project author) sees anything wrong, has improvements, or knows a more lightweight approach, I’d love to hear it. Maybe there’s a cleaner way to achieve the same limited-exposure setup.
Traefik (docker-compose.yml)
Notes
Traefik exposes nothing by default, and I selectively allow only the StremThru endpoints that are actually needed for streaming. Since I’m only serving direct links, I don’t want anything else reachable from the outside.
StremThru (docker-compose.yml)
Notes
Each allowed endpoint is explicitly defined. Everything else remains inaccessible. This ensures users can stream, but nothing can be probed or browsed externally.
StremThru Environment (.env)
Notes
I use a single admin + proxy user for now. Torrentio + RD is configured upstream, so StremThru just receives direct RD links and proxies them cleanly.
The initial setup can be made without the full lockdown. After you can also simply base64-encode whatever you need for userData and verify that streaming works. Make sure that the upstream Torrentio addon includes the RD token, otherwise no direct links will be returned. From there, you can tighten things down like I did if you want the network perimeter locked from the start.
Beta Was this translation helpful? Give feedback.
All reactions