Server Version#: Version 1.24.2.4973-1-01
Player Version#: Various Players from Web, Roku, Android
After I update the server to the version after 1.24.2.4973-1-01 just broke it all. I could not play trailers anymore. I was getting Playback errors on media I just watched. My shared users could not watch anything anymore. I was getting errors saying my CPU was not strong enough to transcode the media. So I rolled back to 1.24.2.4973-1-01 and all was good again. In all the years I have used Plex (pretty much since conception) I have never had an issue like this with an upgrade. I routinely upgrade to improve the Plex experience. Now I am hesitant on even upgrading now since it was a disaster and took a lot of researching to figure out the answer.
Plex please fix what ever you broke and let the forum know they can upgrade safely after that. I have never complained about any minor issues that have occurred but this one messed everything up.
I rolled back to that version which fixed everything. All versions forward of that one just made it worse. The number version is how it was displayed in the rollback achieve which had that 1-01 on it. As for tags I tested this first on UnRAID docker which worked. Then did it to a Windows version with same results. So it would be in both tags. As for players the newer server update would not work on any that I tried it on. All seems to function right on server version 1.24.4973.
ChuckPa I was not 100% sure where to put this to cover the spectrum of servers it caused issues for. I had seen this on many different threads for all type of servers.
you didn’t provide the server log files of the failed state. If you could have done this, we’d have an idea of the problem.
There has been a lot of breakage with Remote Access due to the Let’s Encrypt certificate expiring on Sept 30th.
I wonder if your problem is more the certificate than anything else because I can site a lot of users who have been running all the versions from 1.24.2.4973 and above without issue — UNTIL the certificates broke.
When their certificates were reset , all was working again.
Since you’re discussing Windows and Unraid, I’ll tag for those.
Linux is both a known and resolved entity.
If you want to work deeper.
Please do remember to include the full and proper version, e.g. Version.Build-hash 1.24.4.5081-e362dc1ee
There are like over forty posts on the forum with logs talking about the same issue with no real answers. What good would more posting of logs do if the solution is to rollback to the working version? Just do a search for “can’t transcode error, tailers failing, cpu not powerful enough” with in the last four months. I have posted several times with log files and no answers were given. Well delete this post then at least mine is working now and others will just have figure it out. I just wanted to bring it to light that there is an issue and a lot of people have been talking about it. No solution has been given but one person on the NAS group suggested to roll back to the 1.24.2.4873 version to make it work again. So not being a Plex coder I decided to test it on a Linux system and a Windows system server an what do you know it all works again. So as a Plex Pass customer I would say it’s the update the f’d it up and that a Plex coder should look into it is all I was saying. But if we want to waste four more months talking about log files and stuff great you do you and I will just enjoy my Plex working fine. I was just making an observation but then get beat up for it because I didn’t add log file from a week ago when it was broke. How about Plex reading all the other postings about it.
Yes I had posted them on another thread but could not find it so I am posting a zip file of all the logs from the server at the time I rolled back.
No Let’s Encrypt being used for Remote Access.
From all the forums I have read this is not a certificate issue. Redit, Plex, and various other forums.
No rolling back to the 1.24.2.4973-2b1b51db9 from 1.24.3.5033-757abe6b4-ls75 fixed all the problems. Now I did try to go up to the latest version without getting anything solved. I had to end up rolling back to 4973 to make it all work again.
These log files are from the 26th of Sept right before I did the rollback. I had to scrub names and emails off of some of them, so date may be different.
Generally the docker is just a virtual machine that runs as a host on UnRAID. So UnRAID is the holder of the machine that runs the Plex server. It builds a Plex server just like it would if you put it on Linux or Windows with same folders, files, and directories. What allows the updates is listing the docker to periodically look for the Latest server version. Once it sees it then it pulls it. You can turn off auto update too. To rollback you just have to change the pull repository from Latest to the version number you want and it will roll back. I looked through the logs but I do not see errors for playback. It would give different errors depending on if you use Auto Playback or Forced. Now sometimes if you used Forced it would play the media file MP4, MKV, etc. And something it would show an error that it just can’t play it when I just watched it before the update. Then somes you get an error that you CPU is not strong enough to transcode. Honestly, I have no clue what the issue is just that it worked on one version and not on the others.
Yes you are correct I was simplifying it some with VM. Yes it is a container that uses that same hardware as it’s host system. So instead of bridging the NIC it directly accesses it. Same with graphics card, CPU, and drive space. A system within a system of sorts.
