Issues with bandwidth

Server Version#: 1.41.0.8994
Player Version#: 10.22.1.1607
NAS: Synology DS1520+

Guys, maybe you might have some ideas :slightly_smiling_face:
Latest version of PLEX media server and client running on Android TV - bandwidth isn’t reaching more than 35Mbps (https://youtube.com/shorts/6ho-ypgpNlw) and due to that, video is freezing. As you can see one the video, video is “Direct play”. No buffering even if the buffering is happening in practice :upside_down_face:
With PLEX media server 1.24.5.5173 and PLEX client 8.24.1.28493 (https://youtube.com/shorts/P7kR-8EhWy8) bandwidth is skyrocketing to 210Mbps and there are no issues at all with video freezing and buffering.
Any ideas, what to check/how to fix?
Plex Media Server Logs_2024-10-20_20-34-22.zip (1013.8 KB)
network_logging.txt (4.6 MB)

OOOPS in your network settings.

Oct 20, 2024 19:47:14.701 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.702 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.702 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.702 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.808 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.809 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.809 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.809 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.911 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.911 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.912 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.912 [140630581996344] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.983 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
Oct 20, 2024 19:47:14.984 [140630579886904] ERROR - Error parsing allowedNetworks entry ' 192.168.0.0\0024': Invalid argument [system:22]
  1. There is a leading space – delete it
  2. Synology is Linux, You use 192.168.0.0/24 -or- 192.168.0.0/255.255.255.0 (preferred)

Yes, I’ve noticed that later and changed the value to 192.168.1.0/255.255.255.0,192.168.0.0/255.255.255.0 , but that doesn’t help to solve the issue. Bandwidth is still very very low :roll_eyes:
I’ve attached the logs with changed network value.
Plex Media Server Logs_2024-10-20_22-12-15.zip (1.1 MB)
network_logging2.txt (5.0 MB)

@Etas

When I’m troubleshooting this type thing, the first tool I break out is iperf3.

Speedtest isn’t the right tool. Right idea but not the point-to-point we need.

How to do this:

  1. Download and install the iperf3 server on the syno.
    – Google search: iperf3 server synology and you’ll get links to iperf, and docker, and the how-to’s on YouTube.
    – Set it up to run on the Syno since this is the “home base” we’re interested in.

  2. On your android client, download the iperf3 client app

  3. With iperf3 server running on the Syno, Open the iperf3 client

  4. You’ll point to the IP address of the Syno.

  5. There are two test sets to run : Forward (the default where you send to it) and Reverse (where DSM sends to you – which is what we’re most interested in)

If the client lets you run for more than 10 seconds, run it for 60 seconds so you get a good overview of streaming performance.

What you’re seeing here is the Point-to-Point pure wire speed from Android<->Syno.

If this isn’t cutting it, then we indeed have a networking (WiFi?) problem.

Let me know what you find.

… as example, (please ignore my home LAN – it’s 10Gbps)
Here’s stress testing it in Forward and Reverse modes

[chuck@lizum ~.1999]$ iperf3 -c 192.168.0.20 -t 20
Connecting to host 192.168.0.20, port 5201
[  5] local 192.168.0.13 port 41342 connected to 192.168.0.20 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  1.09 GBytes  9.38 Gbits/sec  220   1.09 MBytes       
[  5]   1.00-2.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.35 MBytes       
[  5]   2.00-3.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.37 MBytes       
[  5]   3.00-4.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.38 MBytes       
[  5]   4.00-5.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.39 MBytes       
[  5]   5.00-6.00   sec  1.09 GBytes  9.38 Gbits/sec  116    831 KBytes       
[  5]   6.00-7.00   sec  1.09 GBytes  9.41 Gbits/sec    0   1.34 MBytes       
[  5]   7.00-8.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.37 MBytes       
[  5]   8.00-9.00   sec  1.10 GBytes  9.42 Gbits/sec    0   1.38 MBytes       
[  5]   9.00-10.00  sec  1.09 GBytes  9.40 Gbits/sec  617    718 KBytes       
[  5]  10.00-11.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.34 MBytes       
[  5]  11.00-12.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.38 MBytes       
[  5]  12.00-13.00  sec  1.09 GBytes  9.41 Gbits/sec    0   1.39 MBytes       
[  5]  13.00-14.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.39 MBytes       
[  5]  14.00-15.00  sec  1.09 GBytes  9.40 Gbits/sec  580    714 KBytes       
[  5]  15.00-16.00  sec  1.09 GBytes  9.38 Gbits/sec  133    962 KBytes       
[  5]  16.00-17.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.34 MBytes       
[  5]  17.00-18.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.38 MBytes       
[  5]  18.00-19.00  sec  1.10 GBytes  9.42 Gbits/sec    0   1.39 MBytes       
[  5]  19.00-20.00  sec  1.09 GBytes  9.39 Gbits/sec  642    716 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-20.00  sec  21.9 GBytes  9.41 Gbits/sec  2308             sender
[  5]   0.00-20.04  sec  21.9 GBytes  9.39 Gbits/sec                  receiver

iperf Done.
[chuck@lizum ~.2000]$ iperf3 -c 192.168.0.20 -t 20 -R
Connecting to host 192.168.0.20, port 5201
Reverse mode, remote host 192.168.0.20 is sending
[  5] local 192.168.0.13 port 46604 connected to 192.168.0.20 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  1.09 GBytes  9.40 Gbits/sec                  
[  5]   1.00-2.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   2.00-3.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   3.00-4.00   sec  1.10 GBytes  9.42 Gbits/sec                  
[  5]   4.00-5.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   5.00-6.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   6.00-7.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   7.00-8.00   sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]   8.00-9.00   sec  1.10 GBytes  9.42 Gbits/sec                  
[  5]   9.00-10.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  10.00-11.00  sec  1.10 GBytes  9.42 Gbits/sec                  
[  5]  11.00-12.00  sec  1.09 GBytes  9.40 Gbits/sec                  
[  5]  12.00-13.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  13.00-14.00  sec  1.10 GBytes  9.42 Gbits/sec                  
[  5]  14.00-15.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  15.00-16.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  16.00-17.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  17.00-18.00  sec  1.10 GBytes  9.41 Gbits/sec                  
[  5]  18.00-19.00  sec  1.10 GBytes  9.42 Gbits/sec                  
[  5]  19.00-20.00  sec  1.10 GBytes  9.41 Gbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-20.04  sec  21.9 GBytes  9.39 Gbits/sec    1             sender
[  5]   0.00-20.00  sec  21.9 GBytes  9.41 Gbits/sec                  receiver

iperf Done.
[chuck@lizum ~.2001]$ 

Testing my Wifi, with iPhone 11,


I was able to make only the test from TV → Synology NAS, because iperf3 server client I’ve installed on TV is too buggy and doesn’t want to work. As a workaround, I used ES file explorer application to transfer the file from Synology NAS → TV by simply copying the file (1,3Gb) over the network. A speed was between 16MBps-18MBps, what converts to 128Mbps-144Mbps.
ChuckPa , can you elaborate a little bit more, why such speed test is needed? By using old PLEX client/server versions, bandwidth results are much higher in comparison with the latest versions, even if network setup is exactly the same. Bandwidth is enough to play all files without any buffering.

RESULTS: TV (Analiti application) → Synology NAS

Data from Synology:

Server listening on 5201 (test #7)

Accepted connection from 192.168.1.99, port 38520
[ 5] local 192.168.1.200 port 5201 connected to 192.168.1.99 port 38521
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 26.5 MBytes 222 Mbits/sec 0 614 KBytes
[ 5] 1.00-2.00 sec 29.0 MBytes 243 Mbits/sec 14 523 KBytes
[ 5] 2.00-3.00 sec 29.2 MBytes 245 Mbits/sec 0 604 KBytes
[ 5] 3.00-4.00 sec 29.5 MBytes 247 Mbits/sec 0 662 KBytes
[ 5] 4.00-5.00 sec 28.8 MBytes 241 Mbits/sec 0 701 KBytes
[ 5] 5.00-6.00 sec 29.1 MBytes 244 Mbits/sec 0 727 KBytes
[ 5] 6.00-7.00 sec 29.5 MBytes 247 Mbits/sec 0 741 KBytes
[ 5] 7.00-8.00 sec 28.4 MBytes 238 Mbits/sec 0 747 KBytes
[ 5] 8.00-9.00 sec 29.1 MBytes 244 Mbits/sec 0 748 KBytes
[ 5] 9.00-10.00 sec 30.0 MBytes 252 Mbits/sec 0 773 KBytes
[ 5] 10.00-10.08 sec 1.62 MBytes 183 Mbits/sec 0 776 KBytes


[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.08 sec 291 MBytes 242 Mbits/sec 14 sender

Server listening on 5201 (test #8)

Accepted connection from 192.168.1.99, port 38545
[ 5] local 192.168.1.200 port 5201 connected to 192.168.1.99 port 38546
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 17.6 MBytes 148 Mbits/sec
[ 5] 1.00-2.00 sec 25.2 MBytes 212 Mbits/sec
[ 5] 2.00-3.00 sec 26.1 MBytes 219 Mbits/sec
[ 5] 3.00-4.00 sec 26.5 MBytes 222 Mbits/sec
[ 5] 4.00-5.00 sec 27.1 MBytes 228 Mbits/sec
[ 5] 5.00-6.00 sec 26.5 MBytes 222 Mbits/sec
[ 5] 6.00-7.00 sec 26.1 MBytes 219 Mbits/sec
[ 5] 7.00-8.00 sec 26.4 MBytes 221 Mbits/sec
[ 5] 8.00-9.00 sec 26.4 MBytes 221 Mbits/sec
[ 5] 9.00-10.00 sec 23.9 MBytes 200 Mbits/sec
[ 5] 10.00-10.10 sec 2.50 MBytes 215 Mbits/sec


[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.10 sec 254 MBytes 211 Mbits/sec receiver

Server listening on 5201 (test #9)

Any ideas?

A lot has happened to PMS and to the client since these versions.
They’ve changed the handling of PMS → player requests and how data is sent.
Also, the player app (Bravia - Android) got a major overhaul.

I’m running the 10.22 Android app on my Shield Pro 2019. It’s SOLID but definitely more CPU load on the Nvidia.

I’ve gone into my player settings and turned OFF a lot of the defaults – SAME with the PMS settings. (I am a simple user with no desire to stream the fancy stuff – OFF it goes)

One thing which did happen between 8.24 → 10.22 , ALL the settings got dropped at one point. I had to / you’ll have to go back in the player and set them up again.

There is a way to pull the TV logs. maybe we’ll see something there ?

Hi,
it’s fully understandable, that the PLEX product development is moving forward :slight_smile: Usually the expected outcome of the development is not only new features, but more stability, more efficiency, bug and security fixing and so on. Or in short - better product in time. However, new versions of PLEX affects the bandwidth and as a user I don’t know which part - server, player or both. That’s why I need someone from PLEX team to be involved into the investigation, because even if I have the logs, the meaning of the values in the log files are known to developers only.
Currently I’ve made three tests and results of these tests are provided in attached log and video formats :slight_smile:

TEST #1: when PLEX server 1.41.0.8994 and PLEX player 10.22.1.1607 are installed. Secure connection setting is “Preferred”. Fields “LAN Networks” and “List of IP addresses and networks that are allowed without auth” have a value “192.168.1.0/255.255.255.0,192.168.0.0/255.255.255.0”. As you can see from the video , movie freezes very often. Log file consist of logs both from server and the client:
New PLEX setup. Secure connections PREFERRED.zip (1.5 MB)

TEST #2: when PLEX server 1.24.5.5173 and PLEX player 8.24.1.28493 are installed (downgraded). Secure connection setting is “Preferred”. Fields “LAN Networks” and “List of IP addresses and networks that are allowed without auth” have a value “192.168.1.0/255.255.255.0,192.168.0.0/255.255.255.0”. As you can see from the video, bandwidth is a bit better, but video is still freezing time to time. Log file consist of logs both from server and the client:
Old PLEX setup. Secure connections PREFERRED.zip (1019.1 KB)

TEST #3: when PLEX server 1.24.5.5173 and PLEX player 8.24.1.28493 are installed (downgraded). Secure connection setting is “DISABLED”. Fields “LAN Networks” and “List of IP addresses and networks that are allowed without auth” have a value “192.168.1.0/255.255.255.0,192.168.0.0/255.255.255.0”. As you can see from the video, video plays flawlessly without any buffering. Log file consist of logs both from server and the client:
Old PLEX setup. Secure connections DISABLED.zip (835.6 KB)

It’s important to mention, no changes in the whole setup has been made between implementation of these three tests, except PLEX client&server downgrading for comparison purposes. It means, that the network throughput is enough to play 4K file with an the old versions of PLEX client+server, but only when Secure connection is “Disabled”.

What else can I check/switch off/turn on/whatever?

@ChuckPa , did you get any chance to look at the logs ?

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