So, used it a bit last night, watched some stuff while I got ready this morning and was just watching a movie remotely from my office and not one bit of buffering on 4973.
So the best that I can see, something went screwy in the next version on, but I would think that there would be a lot more people having issues and reporting it so there is that.
So far so good! Have THREE streams running with no buffering. Same files, same clients, and same location
I just tried 4973 and I am still seeing the same issue 
What steps did you take to install/uninstall? All I did was run dpkg -r plexmediaserver and then I reinstalled 4973 with gdebi. Am I missing something? I thought I understood that purging wasnāt required? If I do I will lose all my server prefs and metadata right?
Ughā¦ same! It was fine for a few hours this morning and now itās back to the same issue. So frustrating. Iām lost now.
I just ran dpkg -i 1.12.3.4973-215c28d86_amd64.deb without doing dpkg -r plexmediaserver beforehand.
FWIW, Iāve been having all kinds of buffering issues lately as well, and Iām only streaming on my local lan. I was on the most recent release and just downgraded to 4973. I see that some are still having issues with 4973, but Iām hoping Iāll be the exception? Iām on 16.04.1-Ubuntu and a very moderate piece of hardware that has worked well for me so far. You all are WAY more technical than me so Iāll just stand back and observe the thread. Iām only speaking up to let you know other people are having the issue too.
2 Likes
Here are my iperf3 results over the Internet:
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-900.00 sec 6.61 GBytes 63.0 Mbits/sec 8 sender
[ 4] 0.00-900.00 sec 6.60 GBytes 63.0 Mbits/sec receiver
That is single threaded to emulate bandwidth available for a single Plex stream.
I downgraded to 1.12.3.4973 after completely rebuilding my server, and still had an issue within a minute or two. Iāve gone down to 1.11.3.4803 and that seems to have resolved it. FWIW, I also made a tweak thinking it might be related to the remote network throttling mechanism within Plex. I added the network 0.0.0.0/0 to the Local LAN network setting on the server. Either the previous version or making that change fixed it for me.
My reasoning behind that change is that my clients that are working were detecting the server on the local LAN because it was going through a VPN tunnel to my server. I verified that through my firewallās connection logs. However, the client that were not working were going direct to the Internet. Iād be curious to know if some change was made in the last few version to the throttling code.
Plex Media Server Logs_2018-07-25_14-21-26.zip (6.8 MB)
2 Likes
I have had good luck since dropping down to 4973. Let us know how that is working out for you.
You mentioned you did multiple rounds of testing, did you find it required to completely rebuild your server from scratch by doing a --purge and deleting all the info on the server?
I did the purge and made sure to delete /var/lib/plexmediaserver each time just to ensure that there was nothing lingering from the previous install. @ChuckPa said that there is nothing in there that would affect the software (or that is how I read it). He has a LOT more experience with this than I could pretend to.
You could try it, but be aware that it will be a fresh install, meaning that you will have to setup everything from scratch (adding/scanning libraries, setting up local users, and removing the old shared server from friends that you have shared them with and sharing the new server).
I completely rebuilt the Ubuntu VM from scratch. New VM, reinstalled US 16.04, fully updated, then install the 1.12 build and had the same issue. Went down to 1.11 and put in the 0.0.0.0/0 LAN network like I said and havenāt had an issue since. I did have to setup everything all over again. Took 12 hours to scan my library, but oh well.
Can you guys try the LAN network thing?
Ok thanks for the update, I will have to try using the purge option though I doubt it will work. I tried installing 1.11 without a full purge and it didnāt work. Also it might be worth noting that I only have had issues with remote playback so far, LAN seems to be fine
To help you all understand how things work in Linux,
/var/lib/plexmediaserver is user plexās home directory (yeah, I know and I want to change it , but ā¦)
To make life simple for testing, Library is the functional root worry about.
If you rename Library to Library.any-other-name-here-you-want, so long as Library doesnāt exist, PMS will think itās a fresh start.
This allows you to actually try different things as different instances then compare from instance to instance.
1 Like
@ChuckPa having a setting to manually set the home dir would be nice, but not relevant to this so I will shut up lol.
@sirianthe3rd 12 hours?! That is extreme.
What is the 0.0.0.0/0 for?
I have a large library 
0.0.0.0/0 basically sets all IPs as Local LAN
How big is that thing that it is taking 12hrs? Seems a bit excessive.
Excessive on time or excessive on library? You can never have too much media.
I think itās sitting on about 7.25TB right now. Just under 20k files. It was 12 hours including metadata population.
Time, I am sitting at about 12TB and it took mine about 2 hours
Sorry, not trying to derail the thread.
Just chiming in that Iām having the same issue and Iām at a loss for an answer. Everything was working fine, and all that changed was server updates, though I canāt pin the time I updated to the time the issues started.
It showed up a few weeks ago for remote users using Roku 3ās to stream. I havenāt noticed any issue locally on my network, but I use the web cilent with chrome at home.
I have 50Mbps upload, that I tested multiple times with various, remote, speed testers which all confirm that Iām getting that speed. Iām not using Comcast (Rogers in Canada).
I disable Plex Relay on the server so users can never end up using the 2Mbps backup connection Plex provides.
Even with 1 user streaming at the lowest transcoding rate possible, buffering still occurs at random intervals (usually within the first 10 minutes).
Iām running Ubuntu 16.04 on an Intel Xeon server class box, and itās not being pushed on IO or CPU during the stuttering periods.
Iāll try backing down to 4973 tonight to see if it helps any.
Try setting your Local LAN network to 0.0.0.0/0. Iām just curious.
2 Likes
