[aloer]

Just the other day I was setting up Jellyfin and tailscale on an n100.

It worked fine locally but sharing via tailscale with a family member across the world somehow broke things. It took about a minute for the stream to start despite a fast enough upload speed. Might be ping related?

I will give this a try

[napkin]

I had this problem too! Jellyfin behind a reverse proxy over Wireguard. For intercontinental visitors (high latency), there would be an initial burst of reasonable transfer speed, but within seconds, slow to an unusable crawl. It took a long time to identify the problem as relating to packet congestion.

Try changing Linux's default congestion control (net.ipv4.tcp_congestion_control) on your Jellyfin & reverse proxy servers to 'bbr'. I don't understand the details- there might be negative consequences [1]- there might be better congestion algos- but for me, this completely solved the issue. Before, connections would stall out to <10%, sometimes even 1% line rate. In quiet/optimal network conditions.

Also, Caddy enables HTTP/3 by default. I force it to HTTP/2.

I should probably investigate using later versions of bbr, though.

[1] https://news.ycombinator.com/item?id=37408406

[cchance]

My issue ended up being the auto-bandwidth negotiation being sorta shitty in jellyfin, i set my remote over headscale web browser to 10mbit and the tv shows play very quick though could maybe be a bit faster.

[overbytecode]

Curious, what was your process debugging/diagnosing this? How did you reach the conclusion that it was packet congestion?