Ah, glad I discovered this. I really was confused when I saw this message with no streams running and 150Mbit available upload rate…
@owtlaw333 said:
I’m getting bandwidth limiting issues when playing LOCALLY and it’s driving nuts. I have to remove the limit altogether to solve the problem.
In looking at your logs, I see requests from 172.17.0.3 and then several from the 212.232.x subnet. I take it the 172… is from the docker networking. Perhaps you need to set the LAN Networks pref to match your configuration: https://support.plex.tv/hc/en-us/articles/227715247-Server-Settings-Bandwidth-and-Transcoding-Limits
@gbooker02 said:
@owtlaw333 said:I’m getting bandwidth limiting issues when playing LOCALLY and it’s driving nuts. I have to remove the limit altogether to solve the problem.
In looking at your logs, I see requests from
172.17.0.3and then several from the212.232.xsubnet. I take it the 172… is from the docker networking. Perhaps you need to set the LAN Networks pref to match your configuration: https://support.plex.tv/hc/en-us/articles/227715247-Server-Settings-Bandwidth-and-Transcoding-Limits
Are you implying that the docker is fowling itself? Because it doesn’t appear that much data is moving from the 172… address and only information pulls (I do have PlexPy running as well); unless I’m reading the logs incorrectly.
Just to add to the above - your local subnet appears to be 212.232.3.xx which is a WAN IP Address range
Any reason for not using a Private Network IP range.?
@sa2000 said:
Just to add to the above - your local subnet appears to be212.232.3.xxwhich is a WAN IP Address range
Any reason for not using a Private Network IP range.?
There was reason years and years ago… no reason exists now other than it’s what I’ve used for so long and have never had a need or urge to reconfigure.
@owtlaw333 said:
Are you implying that the docker is fowling itself?
No, I’m just guessing at your network setup, so if I have it wrong, please elaborate. If you have PMS running inside docker, it’ll see it’s subnet as that 172.17.0.x range. Now your players are on the 212.232.3.x which is not in the same subnet as 172.17.0.x. By default, PMS assumes the LAN network is its subnet for bandwidth purposes. That preference overrides this behavior to the networks you specify, so they are treated as the LAN for bandwidth purposes.
Essentially PMS tries to guess what your LAN is and in the case of running inside of docker, it can get this wrong. This preference exists to correct this situation.
@sa2000 said:
@ms3ars said:
@sa2000 - where can I report problems with installing this latest version (1.2.3)?The installation on my PC completed successfully, but the Plex Media Server.exe file is missing. I’ve tried to run a repair but then I get the error in the attached image.
At first, I thought it was my fault, by installing when the Plex server & PlexPy was still running. But I went back to an earlier restore point and when I re-installed I got the same result again… a missing Plex Media Server executable
I did notice the following in the attached log file - the 2 backslashes in the path before the executable
[1C6C:1C64][2016-10-26T00:08:16]i410: Variable: LaunchTarget = C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
Could this be the cause of the problem?
@jeramie@idghelp.us said:
sadly i’m having the same issue, before and after the update to 1.2.3.2914If you are using AVG - it has been found that it is quarantining the exe file because of the new certificate in 1.2.3 which has not had much exposure yet. AVG is being contacted to get the product certificate accepted
See this post from development team https://forums.plex.tv/discussion/comment/1286985/#Comment_1286985
and my instruction on how to whitelist Plex Media Server binaries in AVG
https://forums.plex.tv/discussion/comment/1287031/#Comment_1287031
Thanks @sa2000 - I’ve just got round to doing another install of version 1.2.3 and was going to follow the steps for AVG but ikt seems AVG must’ve whitelisted the file now because Plex launched successfully after the install.
@gbooker02 said:
@owtlaw333 said:
Are you implying that the docker is fowling itself?No, I’m just guessing at your network setup, so if I have it wrong, please elaborate. If you have PMS running inside docker, it’ll see it’s subnet as that
172.17.0.xrange. Now your players are on the212.232.3.xwhich is not in the same subnet as172.17.0.x. By default, PMS assumes the LAN network is its subnet for bandwidth purposes. That preference overrides this behavior to the networks you specify, so they are treated as the LAN for bandwidth purposes.Essentially PMS tries to guess what your LAN is and in the case of running inside of docker, it can get this wrong. This preference exists to correct this situation.
Plex server is definitely sitting in the same subnet (at least according to the Remote Access menu) so I wouldn’t think that would be the issue. (Maybe there’s a handoff issue within the docker? Seems unlikely to me, but I’m no expert, lol) But again, I’ll enter it in to see if it fixes the issue. Is there a way to add an entire subnet to that list or range of IPs, or do I have to enter specific addresses as the menu implies?
@ms3ars said:
@sa2000 said:
@ms3ars said:
@sa2000 - where can I report problems with installing this latest version (1.2.3)?The installation on my PC completed successfully, but the Plex Media Server.exe file is missing. I’ve tried to run a repair but then I get the error in the attached image.
At first, I thought it was my fault, by installing when the Plex server & PlexPy was still running. But I went back to an earlier restore point and when I re-installed I got the same result again… a missing Plex Media Server executable
I did notice the following in the attached log file - the 2 backslashes in the path before the executable
[1C6C:1C64][2016-10-26T00:08:16]i410: Variable: LaunchTarget = C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
Could this be the cause of the problem?
@jeramie@idghelp.us said:
sadly i’m having the same issue, before and after the update to 1.2.3.2914If you are using AVG - it has been found that it is quarantining the exe file because of the new certificate in 1.2.3 which has not had much exposure yet. AVG is being contacted to get the product certificate accepted
See this post from development team https://forums.plex.tv/discussion/comment/1286985/#Comment_1286985
and my instruction on how to whitelist Plex Media Server binaries in AVG
https://forums.plex.tv/discussion/comment/1287031/#Comment_1287031Thanks @sa2000 - I’ve just got round to doing another install of version 1.2.3 and was going to follow the steps for AVG but ikt seems AVG must’ve whitelisted the file now because Plex launched successfully after the install.
Yes they appear to have started to trust the new certificate / I will update the forum threads
@owtlaw333 said:
@gbooker02 said:
@owtlaw333 said:
Are you implying that the docker is fowling itself?No, I’m just guessing at your network setup, so if I have it wrong, please elaborate. If you have PMS running inside docker, it’ll see it’s subnet as that
172.17.0.xrange. Now your players are on the212.232.3.xwhich is not in the same subnet as172.17.0.x. By default, PMS assumes the LAN network is its subnet for bandwidth purposes. That preference overrides this behavior to the networks you specify, so they are treated as the LAN for bandwidth purposes.Essentially PMS tries to guess what your LAN is and in the case of running inside of docker, it can get this wrong. This preference exists to correct this situation.
Plex server is definitely sitting in the same subnet (at least according to the Remote Access menu) so I wouldn’t think that would be the issue. (Maybe there’s a handoff issue within the docker? Seems unlikely to me, but I’m no expert, lol) But again, I’ll enter it in to see if it fixes the issue. Is there a way to add an entire subnet to that list or range of IPs, or do I have to enter specific addresses as the menu implies?
212.232.3.1/255.255.255.0
Or
212.232.3.1/24
@owtlaw333 said:
Plex server is definitely sitting in the same subnet
Unless you’ve explicitly set it up differently that the default, anything running in a container is on a separate network that’s created inside the host running docker explicitly for containers. Then, it proxies the specified ports through to the container. This means that devices on the same subnet as the host can contact the container using the host’s IP address, but services running inside docker sees network traffic coming from the device’s IP address. That device’s IP address is not within the private docker network created inside the host, so it is not on the service’s network.
Again, I’m guessing somewhat from your description on how you have things set up.
Is there a way to add an entire subnet to that list or range of IPs, or do I have to enter specific addresses as the menu implies?
Assuming your network is 212.232.3.x, then you want 212.232.3.0/24
@sa200 @gbooker02
Thanks guys! I’ll set this up and try to report back.
On a somewhat related note… when I got the error on the FireTV it said nothing of the bandwidth limitation and it wasn’t until I tried on the iOS app that it was clarified where the issue was. Any work being done on each platform to give more specific error messages? (In this case, the FireTV)
@owtlaw333 said:
On a somewhat related note… when I got the error on the FireTV it said nothing of the bandwidth limitation and it wasn’t until I tried on the iOS app that it was clarified where the issue was. Any work being done on each platform to give more specific error messages? (In this case, the FireTV)
I would expect Plex Client Apps to give the extra error text - may be need to catch up. What version is it ? Do you have any logs?
@sa2000 said:
@owtlaw333 said:
On a somewhat related note… when I got the error on the FireTV it said nothing of the bandwidth limitation and it wasn’t until I tried on the iOS app that it was clarified where the issue was. Any work being done on each platform to give more specific error messages? (In this case, the FireTV)I would expect Plex Client Apps to give the extra error text - may be need to catch up. What version is it ? Do you have any logs?
They would be in those logs I posted… unless you mean off of the app, in which case I do not. The FireTV app said it was updated yesterday (I checked last night after I received the error) however I do not have a version number off hand. I will have to check later.
@owtlaw333 said:
@sa2000 said:
@owtlaw333 said:
On a somewhat related note… when I got the error on the FireTV it said nothing of the bandwidth limitation and it wasn’t until I tried on the iOS app that it was clarified where the issue was. Any work being done on each platform to give more specific error messages? (In this case, the FireTV)I would expect Plex Client Apps to give the extra error text - may be need to catch up. What version is it ? Do you have any logs?
They would be in those logs I posted… unless you mean off of the app, in which case I do not. The FireTV app said it was updated yesterday (I checked last night after I received the error) however I do not have a version number off hand. I will have to check later.
Thanks - I have flagged to the Fire TV App team - if you find the version number of the Plex app on the fire tv i will add that info
Im on server version 1.2.4.2949 for Windows and just got this error. Temp fix is to remove the upload speed. But guess that the problem isnt fixed for mobile devices?
@Alxz said:
Im on server version 1.2.4.2949 for Windows and just got this error. Temp fix is to remove the upload speed. But guess that the problem isnt fixed for mobile devices?
The last discussion in this thread was about the text being generic on the Fire TV and that is the issue that has been referred to the developers.
If you have an actual issue where the bandwidth error is being given when you believe it should not, then please reproduce the problem with debug logging enabled on the server and restart the server to get fresh log files created and when you get the error take a screen capture andn attach together with the server log files zip
See
https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Error is still there for a server running 1.2.7 on Nvidia Shield. I’ll try to collect debug logs tomorrow.
I too am getting this error, only started tonight. Getting it on any device not inside my LAN.
@nickswitz said:
I too am getting this error, only started tonight. Getting it on any device not inside my LAN.
Please restart the server and get the zipped server logs when it happens
See link earlier in this thread (few posts above) for support page on log files
