Server Version#:1.25 and above
Happens on any browser. Tried Chrome, Firefox and Edge.
Any Plex server version 1.25 and above has this issue. The only fix is to downgrade the server to 1.24.5.
Once downgraded, the issue no longer happens.
14 Likes
This appears to be happening to me as well. Iām going to try downgrading my install and see if that solves it as well.
same situation
I was having the same issue on server version 1.25.2.5319 on multiple browsers/operating systems.
I rolled back my docker container to server version 1.24.5.5173 and the webapp works without issue again. It looks like there a problem with the webapp on 1.25 and above.
Hope a fix is coming soon.
I have also had the same issue on 3 different laptops using the Web Player running server version 1.25.0 and above. Playing TV a series, different episodes will stop and the status will show ābufferingā, it is not transcoding, it is able to direct play both video and audo, but the server network traffic drops and CPU drops.
Skipping back a few mins will play up to the point it stopped, skipping forwards a few mins will play for maybe 5 - 7 mins and then stop again.
I have rolled back from the latest container and tested on each version back to server 1.24.5.5173 / web player 4.63.0, and agree with @dmordan & @ccris, after rolling back it is able to play the same episodes without issue again.
Iām currently running 2 plex containers one version 1.24.5.5173 the other on the latest version with a separate copy the of the database, so I can check if / when its fixed.
Can attach logs if needed
1 Like
Same issue with 1.25.x. Similarly, rolled back to 1.24.5.5173 and all is well. Guess Iāll keep an eye on the release notes for a plex web fix. This is such a breaking change that needs to be fixed ASAP.
1 Like
Same issue here. 1minute 29seconds it freezes on every recent blu-ray rip I have made. Older rips seem ok. Web Browsers only, even Safari.
Setting the video to āConvert Automaticallyā fixes the issue, but will try rolling back to 1.24.5.5173 as suggested here. Thanks!
1 Like
Confirming the issue on 1.25.2.5319 and the failure to buffer seems to be happening to an increasing number of titles at an alarming rate. It seems to have gone from ārarelyā when I noticed it a few weeks ago to āregularlyā as of today.
I followed the process at r/PleX/comments/decbkz/psa_heres_how_to_roll_back_to_a_prior_version_of/ to roll back to 1.24.5173 as suggested and so far it seems to be a solution to the problem.
1 Like
I have the same issue. It seems to only happen at original video quality. If there is any transcoding then the same movie will play fine.
Can confirm downgrading worked for me also.
How do you submit a bug? Never done it before. Will Plex people be aware of this on the forums?
Same issue here, noticed it a couple weeks ago in firefox web client and server version 1.25+
Plays fine for a few minutes then stops saying buffering, but there is no buffering occuring.
I will do as others here have suggested and downgrade to 1.24 and see if it helps.
This is definitely a problem and is affecting many of my users.
There is inherently a problem with browsers and Original quality.
Itās not a new problem.
Browsers canāt handle high bit rates. They never could.
Firefox is a commonly used browser. Iāve noticed a trend. Itās getting harder and harder to use it for day-to-day.
Chrome is, well, you know ā , Chrome.
The recommendation I have is not the best but absolutely works.
- Settings - Web - Quality - 20 Mbps/1080p
Before telling me you have a nice big 4K monitor and want to use it ,
- WHY are you using a web browser?
1 Like
Understood, but does this constitute high bit rate?
Also, works fine with rolled back to PMS 1.24.5.5173.
As the previous user said if it was as simple as that and always been that way, why does it work fine for all of us when we roll back to version 1.24.x?
This is a reliably reproduceable issue on v1.25.x. I personally have had no issues with firefox and original quality, until v1.25 came out.
The other possibly common thing I have noticed with people posting the same problem is that we are all using linux as our server OS. This may be incorrect though, other users feel free to chime in here with your server OS.
1 Like
Thanks for pointing that out. I had forgotten to mention.
In 1.25.2, we go the updated version of Plex/web.
Yes, they made changes to the defaults for Playback and how itās handled.
Since you all are having problems, can you help me create this?
I have 1.25.2.5319 on my QA server here.
Iāve not yet reproduced this until I ācrank upā the bitrate above what my i7 can process in Chrome (about 60 Mbps)
I have a full suite of test files here from https://jell.yfish.us/
(these are a nice set of the same 1-minute video at increasing bit rates)
Would you mind downloading a set of them (up to about 100 Mbps HEVC and H.264) , place them in their own directory, and create a āOther Videosā type library āJellyfishā.
Then , in Plex/web, start playback at the lowest and work your way up until it fails.
Please let me know that result.
If everything passes then weāll advance to something more complex for Plex/web
1 Like
Thanks for this. Iāll look into trying this tomorrow. Iāll make a copy of my current server and upgrade it to 1.25.
Only other thing I can say, is that on the videos I had ripped myself, it ALWAYS stopped at 1minute 29 seconds. Iām willing to accept if Iām using an odd setting when ripping these from the blu-rays. I just donāt know what that is.
But Iām wondering, these are 30 second clips, so will I see the same result if my server always seems to freeze at 1min 29seconds?
Same issue on my phone and the web player, TV seems fine.
The reason for the 30 second clip at the high rates is to rule out overloading of the browserās playback buffer.
If it can play 30 seconds worth of video at 200 Mbps then it can do just about anything production releases need.
