Local network treated as remote network (throttling quality)

Plex Media Server
,
1

Server Version#: 1.25.2.5319

I have two home networks. 192.168.0.0/24 and 192.168.2.0/24; my Plex server is on the former indirectly via docker.

Any clients on 192.168.2.0/24 are automatically throttled to 2 Mbps, clients on 192.168.0.0/24 are not throttled. In the Plex server configuration, under network settings, and “LAN Networks”, I specifically have listed: “192.168.0.0/24,192.168.2.0/24” (w/o quotes). Which should prevent clients on 192.168.2.0/24 from being throttled, but this is not the case.

The server is running as a docker container, and the interesting networking that docker uses may be part of the issue. The docker network is 172.20.0.0/24.

I have restarted, rebooted Plex. Tried restarting the clients. But no luck. I assume I’m missing something else.

Anyone know what I may be doing wrong and where to look?

Thanks!

EDIT: fixed typos

2

In the client itself, Remote Quality defaults to 2 Mbps.

Try bumping that up to whatever you’d like.

1 Like
3

afaik Docker needs to be bridged to the local network. but what chuck said is more likely it.

4

Thanks, but that’s a workaround per client. Not a solution. I’m looking for the correct, server-side solution here.

5

I’m not sure I understand. The docker is bridged to the local network, otherwise I wouldn’t be able to reach it from anything but the docker host. Perhaps I’m missing your meaning here.

6

Sorry I misunderstood what you were asking. That setting It prevents those clients from being throttled by server if you have bandwidth limits set on server, but it does not change what the client can request. The server can’t force a client to request a higher quality from the server.

7

Recommendation.

Use this as a guide:

  1. Docker runs on the host, using the host’s LAN IP; no bridging.
  2. You still have PMS contained and managed in docker.
sudo docker run \
-d \
--name plex \
--network=host \
-e TZ="EST" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=1000 \
-e PLEX_GID=1000 \
-e PUID=1000 \
-e PGID=1000 \
-h dockerplex \
-v /sata/dockerplex:/config \
-v /sata/dockerplex/tmp:/tmp \
-v /sata/dockerplex/transcode:/transcode \
-v /vie:/data \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass

Note: /sata/dockperplex is the SSD where this container runs on the host. '/vie` is the nas.

8

I’ve done a bit of fiddling and discovered a couple things. See my reply to ChuckPa below.

9

What I’ve found after fiddling:

As I mentioned I have 172.20.0.0/24, 192.168.0.0/24 and 192.168.2.0/24 defined as local networks. The docker running PMS is bridged from a 172.20.0.0/24 address to a 192.168.0.0/24 address. Clients on the 192.168.0.0/24 network are not throttled, clients on the 192.168.2.0/24 network are throttled. No other difference than the subnet (I’ve moved the clients back and forth on the network).

Changing my docker container to use the host network instead of bridging (the recommendation) appears to resolve the issue as far as the throttling goes; it behaves as you’d expect, both 192.168.0.0/24 and 192.168.2.0/24 are not throttled.

This leaves me with some other network challenges regarding the other docker containers on the 172,20.0.0/24 subnet reaching the PMS. But I’m fairly sure I can work through those.

Although it’d be nice if the network bridging didn’t confuse PMS a bit in this situation, the recommendation appears to be the correct and acceptable solution.

Thank you!

10

Do you have any server log entries referencing allowedNetworks, such as “Error parsing allowedNetworks”? The parser is opinionated.

Or LanNetworksBandwidth?

What do the server logs say when a client request arrives from 192.168.0.0/24 vs. 192.168.2.0/24?

Allowed Network (WAN)
Allowed Network (Subnet)
(WAN)

Something else?

How is traffic routed (or translated) between the 192.168.0.0/24 and 192.168.2.0/24 networks?

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.