I’m kind of bummed there has been no reply from @drzoidberg33 since his first and only comment on this thread. I have no idea if this is even being looked at, although it is a clear and documented problem with the latest versions of PMS.
Not yet. I rolled back and its glorious. Cant wait until they fix it.
I am having the same issue, but I am having trouble downgrading the Plex version. Did anyone successfully do this in Unraid? (More of a question to an Unraid forum)
I’m also dissappointed that this issue is not getting more attention.
Any news on this from the Plex staff? ![]()
This is the typical plex Support. The wont respond on this issue because they are not fixing stuff.
This! I also noticed this one lately… Hopefully, this is fixed in a new version…
Bump, any updates on this one ? ![]()
Same issue here as well, Bump!
@drzoidberg33 any movement on this one from the Plex team?
Appreciate your responses to-date and that Plex Meta Manager is perhaps not using the most “optimal” API call methods such as batch-editing labels; but as we’ve seen across multiple reports, the exact same run is taking significantly longer between PMS versions when the same configuration of PMM is used, indicating further that the issue is relating to how Plex is responding to the API requests - regardless if they are “optimal” or not.
Any update appreciated as we are seeing a lot of complaints on this issue in Discord.
Im also waiting on the upgrade of plex until this is fixed. @drzoidberg33 please use some resources on this.
Yep unfortunately I can’t update my Plex server until this is resolved.
Same experience here - bump
Having the same issue with version 1.32.7.7571-13cdc68dc. Bunch of Internal Server Errors
@HTMLN00B I would open a separate thread for that - if you use PMM then we are ware of this and have some ideas as to the “what” but not the “why”, and are seeing if we can put in a workaround.
TLDR from very early checks, when the API does certain searches that used to return 0 results (i.e. searching for items with a specific label) it now gives a 500 error rather than replying with 0 results
Great explanation thanks! I’ve reverted back to 1.29.2.6364-6d72b0cf6 and PMM no longer has any errors. I’ll stay on this one for now. Thanks again
Running 1.32.7.7571 and unfortunately cannot revert back, please advise, @drzoidberg33 .
We have the same problem and can support the statement of version containment.
Can anyone at Plex give an update as to whether this is even going to be looked at? A lot of users are stuck on old versions of the server software because of this, something that will almost certainly cause problems in the not too distant future.
@ChuckPa perhaps you could advise if there’s been any movement internally on this one?
I think it’s safe to say that based on the comment history that this is a wide-reaching issue that multiple people are experiencing, we are willing to assist with any investigation to get this resolved.