last, not latest
My issues are local and remote. I think that the OPās are also.
Local fiber ISP here
Whatās the difference?
My issue is only with one āsiteā. The āsiteā that doesnāt has no issues that I can tell, but I have a lot newer hardware. I wonder if there were any client updates within the last 2-5 weeks? This seemed to happen very suddenly.
Both sires are remote in my case, although the good one is going over a VPN tunnel the other is not.
Latest meaning latest released or current version.
Last meaning the one before the latest released (current)
Iām running Ubuntu 16.04 LTS x64, Plex Version 1.13.4.5271 Across a Frontier FIOS 30/30 Mbps connection and also experiencing this buffering issue with two Comcast Xfinity connected Roku player sites. None of us noticed problems until about 2 weeks ago.
I just installed iperf3 on my system, now need another site with non-proxied iperf3 to test against.
I just ran mtr against one of the Comcast Xfinity IPās and got this report:
pluto (50.47.131.202) Tue Jul 24 18:07:27 2018
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 50.35.80.1 0.0% 121 0.6 0.9 0.3 19.8 2.2
2. ae8---0.car01.evrt.wa.frontiernet.net 0.0% 121 1.3 2.0 1.1 35.4 3.2
3. ae3---0.cor02.sttl.wa.frontiernet.net 0.0% 121 2.4 2.6 2.1 9.1 0.8
4. ae1---0.cbr01.sttl.wa.frontiernet.net 0.0% 121 2.1 2.3 1.9 12.9 1.3
5. 12.246.35.17 0.0% 121 3.2 2.9 2.7 3.4 0.0
6. 12.122.85.222 0.0% 121 5.5 5.6 3.5 7.6 1.0
7. 12.122.111.109 0.0% 121 8.3 7.4 3.4 11.5 2.2
8. cr2.ptdor.ip.att.net 0.0% 121 4.2 5.0 3.1 7.1 1.0
9. be-206-pe02.seattle.wa.ibone.comcast.net 0.0% 120 4.2 4.0 3.7 4.8 0.0
10. be-10847-cr01.seattle.wa.ibone.comcast.net 0.0% 120 4.1 4.4 3.3 5.9 0.4
11. be-7922-ar01.seattle.wa.seattle.comcast.net 0.0% 120 3.6 3.5 3.2 4.0 0.0
12. po-1-rur202.bellevue.wa.seattle.comcast.net 0.0% 120 4.0 4.0 3.8 4.6 0.0
13. po-2-1-cbr20.bellevue.wa.seattle.comcast.net 0.0% 120 4.1 4.1 3.9 4.5 0.0
14. c-98-237-240-123.hsd1.wa.comcast.net 0.0% 120 15.8 18.7 13.5 85.1 8.7
I donāt think we have bandwidth or latency issues. When I was visiting one remote site the other night we tried to watch a movie, it would play a couple minutes, then spend the next 2-5 minutes ābufferingā. I finally decided to download the movie which took about 30 minutes to download from my Plex server over the same connection. The movie is over 2 hours long. Bandwidth doesnāt appear to be the issue.
Like I read others here say, I had Plex Server bandwidth limits off because up until a few weeks ago they werenāt needed. Everything played fine in nice clear 1080p (and 4K 2160p) with some media being 17Mbps. I am running QoS and have Plex just behind my VoIP telephone service in data stream priority. So Plex has almost all my connection bandwidth available if it needs it, no matter what else is occurring on my connection. Everything except voice traffic will be behind Plex.
So I thought rolling Plex back to Version 1.13.0.5023 May 10 might help. No change, buffering problems are still there.
About 2 weeks ago everything came to a screeching halt. Plex Update? Comcast ISP experimenting with QoS and ātraffic lanesā messing up port 32400? Frontier FIOS doing something funky? As a prior Comcast customer having experienced Comcast āprofit motiveā (Golden Turd winner 2 years running), Iām inclined to point at Comcast. But I want data to show this, not just rub my gut and guess.
Iām running a direct connection to the Internet, no routers except whatās on the other end of my FIOS connection at Frontier. Anyone else setup similarly for an iperf3 test? Contact me and lets collect some data. phone call preferred to speed things up. If itās long distance for you, I can call you, even if you arenāt in the US.
Previous version download https://downloads.plex.tv/plex-media-server/1.13.2.5154-fd05be322/plexmediaserver_1.13.2.5154-fd05be322_amd64.deb
I <3 you
Thanks!
Here are all the Plex versions Iāve run since initial setup. This issue started about the same time as the last two of these were released, maybe slightly beforeā¦ maybe.
-rwxrwxr--+ 1 craig users 108830880 Feb 19 19:26 plexmediaserver_1.11.3.4803-c40bba82e_amd64.deb*
-rwxrwxr--+ 1 craig users 108949344 Mar 7 10:44 plexmediaserver_1.12.0.4829-6de959918_amd64.deb*
-rwxrwxr--+ 1 craig users 109238814 Mar 23 01:58 plexmediaserver_1.12.1.4885-1046ba85f_amd64.deb*
-rwxrwxr--+ 1 craig users 109234474 Apr 13 21:53 plexmediaserver_1.12.2.4929-29f6d1796_amd64.deb*
-rwxrwxr--+ 1 craig users 109277946 Apr 20 22:17 plexmediaserver_1.12.3.4973-215c28d86_amd64.deb*
-rwxrwxr--+ 1 craig users 110778652 May 10 11:04 plexmediaserver_1.13.0.5023-31d3c0c65_amd64.deb*
-rwxrwxr--+ 1 craig users 111093662 Jun 17 10:15 plexmediaserver_1.13.2.5154-fd05be322_amd64.deb*
-rwxrwxr--+ 1 craig users 111449174 Jul 17 09:18 plexmediaserver_1.13.4.5251-2e6e8f841_amd64.deb*
-rwxr--r-- 1 craig users 111421136 Jul 22 00:07 plexmediaserver_1.13.4.5271-200287a06_amd64.deb*
And my QoS setup, coming into my server:
class plex commit 20%
match udp port 1900
match tcp port 3005
match udp port 5353
match tcp port 8324
match port 32400
match udp port 32410
match udp port 32412
match udp port 32413
match udp port 32414
match tcp port 32469
and serving up Plex to the outside world:
class plex commit 48%
match udp port 1900
match tcp port 3005
match udp port 5353
match tcp port 8324
match udp port 32410
match udp port 32412
match udp port 32413
match udp port 32414
match tcp port 32469
You can test against my California non-proxied iperf3 server and/or my Netherlands one.
California is 100/100Mbps and Netherlands is 1000/1000Mbps
Send a PM and Iāll give you the IPs to check
Did you download those on their release dates? I might have missed a few releases. I know that I last updated a few months ago
See, this is what Iām worried about. Iām not sure what version will revert back the issues Iām having.
I thought 5154 would be safe; is that what youāve tried?
1 Like
yeahā¦ takes a bit of time to setupā¦ Donāt want to go one version back and then find out it was before then lol
I am seeing a bunch of stuff on the forums about issue with the latest and not the previousā¦ I am going to go with the previous and see if that fixes the issues
I rolled back to 5023, I wasnāt sure about 5154. Check your messaging, I sent phone and name info.
Keep us updated
Those downloads are close to release dates. When Plex notifies me, I upgrade, usually almost immediately.
1 Like
oh, well I guess I donāt have to set it all up again YAY.
Well, that was quick. It didnāt fix the issue on 5154.
