So, just to be clear, this does not affect anyone on an older 1.41.3 version? This only affects anyone who updated to the new PMS version even if they have the previous version’s codecs downloaded already?
Glad I waited to upgrade.
So, just to be clear, this does not affect anyone on an older 1.41.3 version? This only affects anyone who updated to the new PMS version even if they have the previous version’s codecs downloaded already?
Glad I waited to upgrade.
CORRECT,
Older, non-upgraded, versions of PMS are not impacted.
There is ONE CAVEAT.
You need to either invoke the scanner or play something for it to populate the directory. (Codecs-on-demand)
I am so glad finding this thread/annoucement. I was so frustrated and about to nuke my whole instance.
Host: Unraid 7.0.0
Docker container: linuxserver.io 1.41.4.9463-630c9f557-ls255
Hi just upgraded to Version 1.41.4.9463 running on a linux server (ubuntu if that matters) and can confirm the issues others are seeing. Before I found myself here i tried to remove my codec folder and have plex recreate it. folders and permissions are all fine. Previous to the delete I was getting the SHA1 error. Now i’m getting the failed to download xml error. Can post logs if they will help!
My bad for not making it clear., but yes I have been trying to play something after every troubleshooting step.
I’m currently getting the error message: “Conversion failed. The transcoder exited due to an error.”
Hmm, it actually is downloading codecs now. I have h264_decoder.dll and libx264_encoder.dll added to the Codecs folder now on the PMS computer. However, I am still getting the same playback error on the client.
If you’re still getting the codec error then there’s nothing to do.
For Synology, if you have 1.41.3, revert to it
The error you see, XML -vs- SHA1 is the where the breakage occured.
They are out of sync with each other.
Hopefully when folks wake up (kinda expect this soon), it will get resolved.
So restarting PMS did not fix the issue, but restarting my PMS computer fixed something interestingly enough.
Web and iOS client playback are working now. However, the Windows client I am using plays the video, but shows only a gray screen with only audio coming through. No idea what is going on, as I’ve never had this happen until now.
I unfortunately don’t know anything about Windows (except to wash or break -haha) . I am 100% Linux here.
This type of failure has never happened to Plex before.
Based on the conversations during diagnosing it, I know they’re going to make certain it never happens again either
Sounds good. Figured at this point y’all had what you needed but would share what i’m seeing to see if it helped/repeated whats been submitted already. I’ll just wait for the fix then! Thanks
If you find the download links for the codecs that are failing the checksum you can pull the download grab the file and put it in the codec’s folder directly. That seems to solve the issue for now for me. Or you can just wait until they have this all fixed!
Is there a link where the codecs can be downloaded manually? I don’t have the downloads folder because I just downloaded the desktop client for the first time after the website started having this issue, so I can’t roll back the desktop app.
You cannot download anything manually.
PMS needs to validate the file(s).
It will look at Plex.tv for the info it needs.
When the info it needs doesn’t match the info it gets from the local file (manually or PMS downloaded) , it flags as error.
You must wait. Sorry
( Servers, not players, are the most impacted here )
Worked perfectly!! Rolling back a version was the temporary solution indeed!! Thanks!!
Chuck, sorry if asking the obvious, but where can we find the older version to download?
Thanks!
On my Windows installation there is an updates folder where i have three versions to install, including the latest.
C:\Users[USERNAME]\AppData\Local\Plex Media Server\Updates
I had removed the codecs folder yesterday, but that didn’t seem to fix my issue. Tried it again this morning and it seemed to solved it. Have to test on other devices. I’ll report back later.
I don’t know if it’s fixed, or still work in progress, but now it’s working properly. Tested with clean codecs folder and PMS restart.
Btw - shouldn’t there be some kind of “Crap, we need to go back, something is wrong with the new update” mechanism that would allow Devs to fallback to last working state in something like two clicks?
Tested my other devices and it all seems to work again. Deleting the codec folder has helped this time, it didn’t yesterday ![]()