QoS

[jellyfin-archive]

QoS

[hayer]

What would a proper way be? What router OS?

[derritter88]

@hayer : I am using Sophos XG & Mikrotik - So far I have priorized the ports which I mentioned earlier as source & destination ports to my VM server which runs Jellyfin.

[hayer]

What exact user experience are you looking for? Not that in to QoS but IIRC QoS lets you prioritize;

• Packet loss
• Latency
• Throughput

What do you want Jellyfin to do? Doesn't the packet inspection tool have to be able to categorize the packets?

Edit: Did some googling and took a quick look at the Sophos configuration. Are you looking to guarantee delivery or limit data? Either way it seems that the rules have to be defined in the Sophos configuration.

[derritter88]

I have two sites - connected via VPN. As there might be a lot of traffic (HTTP, SMB, ...) I would like to have the Jellyfin streams to be priorized.
So far I was able to do this on my Sophos firewalls - I was just looking for some possible manuals if there is a "right way" or if just simple port QoS is doing the thing I am looking for.

[JustAMan]

This should be discussed on main, server repo as it doesn't have anything to do with Web UI I think.

[hayer]

@JustAMan It doesn't have anything to do with the server either in my opinion. My vote is for this to be closed. The process is different between Sophos XG and pfSense, and opnSense, and so on. And this has to be setup on the network equipment, not in Jellyfin.

[JustAMan]

So maybe we should move it to https://github.com/jellyfin/jellyfin-docs/ and discuss as a documentation issue?

[derritter88]

@hayer : I agree if there are any updates in the documentation which ports to priorize this ticket can be closed.

[hayer]

Still doesn't feel like this belongs in any of the Jellyfin repositories at all. What do you want the documentation to say? HTTP data is sent in the ports you put in the configuration?

And setting ports for QoS fails if UPnP?

I'm still a bit confused about what the docs should say.

---

Networking

Quality of Service, QOS

The ports are the same listed in your configuration. If your running UPnP this will probably not work. It all depends on your gear.

[derritter88]

I would more think like a non-IT-guy:
Networking
Quality of Service, QoS
For a better streaming "experience" (could be a different word) we recommend you to set up Quality of Service (QoS) on your router.
Please consult your router manual how to do that.

If you have not modified any ports please priorize the following one:

1234 TCP // HTTP
4321 TCP // HTTPS
1111 UDP // Broadcast for new devices
2222 UDP // Android TV stream
.... and so on.

[hayer]

Well that is my point "non-IT-guy" looking for information about QoS? Why should we educate him? My fear is that people think "QoS will solve my problem" then start asking questions about getting QoS set up.

How does QoS affect reverse proxies? Should that also be documented?

Port list can be found here for the one that wants to write a PR.

[derritter88]

Why not?
From my point of view a good documenation is essential - also for non-IT-people.
More and more are moving to open source software but with limited knowledge how to do a proper setup.

I moved from Plex to Jellyfin last week but for Plex there are some useful tips on (Reddit ).
Would it make sense for you to just display a default QoS setup and ask the people to post their related QoS questions to Reddit or something similar?

[hayer]

Good documentation is important. To create good documentation the bits have to be relevant to the product. I'm having a hard time justifying that QoS is related to Jellyfin.

For instance, the reverse proxy is there because it is used very often, people often have problems with it, and there are specific Jellyfin settings.

QoS is used very seldom, not very related other than ports and UPnP - which you should already know if you are setting it up. This information is easily obtainable within 5 minutes of googling.

But I'll leave this for now for someone else to comment on.

[heyhippari]

The issue I see is that QoS is incredibly generic, and shouldn't be done by users who know nothing about how QoS works or is.

All you basically need is the list of ports, which are already in the documentation (and some you can infer like 80/tcp and 443/tcp for the web client).

The rest is heavily dependent on what you want to do, your networking hardware and topology, your configuration, etc.

There's really no "one size fits all" for this, pretty much like for reverse proxies (and there's been a bit of discussions about reworking the reverse proxies pages recently due to that).

Imho, it's outside of the scope of Jellyfin to provide a step by step on what QoS is and how to implement it. The documentation needs to stay relevant to Jellyfin and I see nothing directly related to Jellyfin for this topic, aside from a ports list (which is already documented).

[derritter88]

Okay so let's leave it as it is currently.