Reverse proxy bandwidth slows after a bit

1. The problem I’m having:

Running a simple proxy through the Windows 11 or git bash, using it for jellyfish streaming. Bandwidth is fine once the proxy is first ran on a fresh config but after several minutes it slows down to maybe max 4mbps. I have no config just the simple reverse proxy command in my caddy file as shown below. Everything connects fine it just tanks the network usage for some reason when streaming video. To get it working properly again for a bit before it tanks I run caddy stop then caddy reload several times.

My only other set up is ports 443 and 80 forwarded and cloud flare DNS without cloud flare proxy, just dns. My hostname loads fine just usage tanks when streaming.

Should I be doing this in docker? Does this have to do with websocket buffering ? Is it a WSL bandwidth thing? Anyone have any suggestions for what it could be or if I’m missing something?

2. Error messages and/or full log output:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

3. Caddy version:

4. How I installed and ran Caddy:

a. System environment:

b. Command:

caddy run

c. Service/unit/compose file:


d. My complete Caddy config:

Jellyfin.example.com
{
 reverse proxy localhost:8096
}

5. Links to relevant resources:

I don’t have any performance problems running Caddy directly on Windows, proxying to Jellyfin.

That’s great to hear, so my config seems alright then? Could it be my ISP throttling something related to the reverse proxy? Perhaps a router setting? Or even a Windows setting of some kind?

Yeah, I think there could be a lot of things going on. It’s very situation dependent. You’d have to dive into your various technology/system/network stacks to find out.

1 Like