Did Plex just silently Kill Legacy Content forcing Fresh Libraries as Price Doubles? (Probably NOT)

UPDATE from OP: Probably NOT. Am I leaving this post here? Yes for four reasons I will start here, and add more blow.

  1. Honesty and Transparency. Was it what I first thought? No. When I say I’m happy to be wrong, I mean what I say. And I can’t set the record straight if the record is hidden. Turns out, it’s more complicated than that.
  2. If it happened to me, it has happened to others, It may be helpful to someone else.
  3. Because I DO 100% believe there is a bug that I caught, and it’s just really bad timing, and I hope this is a nudge to re-think how valuable preventing this type of issue from happening can really be.
  4. To anyone who is using this or similar topics to simply complain about a price hike for no reason other than it being a price increase needs to just stop. I was never upset about a price hike, Of course the price has to go up over time. I was only mad about what what I perceived as deceptive behavior.

Server Version#:1.41.5.9522-a96edc606
Player Version#: ALL

Every single player, on any platform, had a wide range of issues all coming down to a single solution, even when the player could recognize the media…

All media legacy libraries are now permanently broken, you must create a new library.

I have plenty of first hand knowledge of how expensive it is to create, maintain, let alone innovate in todays markets. You had a well written press release too.

And then you pull a shady deal like this? I don’t have to see the actual code base to know just enough to now with a little extra engineering effort in front of doubling your prices you could have kept your word and integrity to the intent of the press release.

Be better

They did for me.

What?
How so?

If you talk about legacy agents… Plex has announced for >1 year that those will go away at some point, offering a migration route (and being more insisting about it, by pushing notifications/warnings into users faces). Though, from what I’ve seen, they haven’t yet pulled the plug on those “legacy libraries”. I’m assuming that’s what you’re talking about… but it’s hard to guess.

And as soon as anyone does the solution, they must rebuild their media library even in place right next to the existing one, it is no longer legacy. It’s new.. that means the features promised to the legacy uses go up in smoke? I hope I am wrong, but they just forced me to update all of my content aka non legacy.

What solution?

What was promised? The legacy agents have been deprecated for quite some time with a very clear message that they’ll be removed at some point.

Plex made statements about plans for a future official API to create new custom agents / use cases… but that’s not linked to the legacy ones.

I don’t mean to be rude. I’m having a hard time getting what you’re trying say.

2 Likes

I gotcha.. easy to get them flipped cause many of don’t deal with pricing, but we do the agents, and “Legacy” is a word well known, as you have stated, for quite a while when it comes to the agents.

I’m speaking to legacy libraries, and the impact that will have going forward on paid subscriptions. Here is a link to the official press release from Plex.

https://www.plex.tv/blog/important-2025-plex-updates/

What is this single solution?

Please explain what you mean by a “legacy library.”

How are they broken?

Specifically, which features?

Please explain the impact on a Plex Pass or Plex Remote Watch Pass.


Please provide specific examples.

I have read this thread multiple times. I do not understand the point you are trying to make.

1 Like

I too am pretty confused by the OP’s “issue”. I read the link he provided about the Plex blog post and I don’t see ANY mention of losing access to legacy libraries or any libraries. I assume he means our own content when he says legacy libraries but who knows.

Everything seems like it will work as normal if you are already a plex pass subscriber. The only change is remote viewing for non Plex pass owners. But that has nothing to do with legacy libraries or whatever that is.

I don’t know what just happened. i do know things are different. i gotta dig in and see whats going on.

@jodut

I am looking at your account from Plex.tv

I see three active instances of a server named (abbreviations) J. P. S. running on Debian/bookworm.

Is this what you’re referring to?

You also have other server instances

Are your server’s becoming unclaimed ?

@MorrWorm8

I see one server, in Docker, on ARMv8. (PMS 1.32.8)

Is this correct ?

While I believe reasonable people can disagree on the same information, I will attempt to more tightly couple the points, from start to finish.

The use of the word issue in this context in my opinion was accurate choice, it is an in imprecise word as well, let’s break it down into three levels.

Issue-Minimums = The inability to play a video. I did mention more than one, but to focus, one specific issue is the inability to play a video. Here are four screen shots taken shortly before I write this post, not the clock down in the corner is UTC, so no as to avoid time nonsense, and local time shroud never be used in debugging or showing evidence of a problem being explained. Since am not familiar with how this forum will render the photos, I’ll just describe them an hope they end up lined out as intended visually.

For context I have been watching this same show for accouple of hours now, I just paused the video opened the webplayer, changed the time to UTC for screenshots, re-sized and moved the window to make it easier to visually capture the key elements. Also I chose to use the webplayer again because it provided the best visual context for a simple example.

  1. NewLibraryBeingRebuilt movie had been playing, now paused.
  • Note the spinner in the upper right as the optional features such as detecting credits is going on in the background
  • Second look at the time bar under the episode and it’s approximate position
  • Third, the library named on the left
  1. OldLibaryWontPlay As above, we will get too the won’t play in a moment.
  • Look at the approximate length of time this episode is
  • Screen shots taken less than a minute apart
  1. OldLibaryWontPlayMetadataPresentAndUpdated
  • Primarily context between the two screenshots
  • Details on time episode expected to re-start at or begin again
  1. OldLibaryWontPlayExampleErrorMessage
  • Webplayer error message presented to user
  • Video will not play

This is a single example that is what I referenced in my first paragraph when I said “Every single player, on any platform, had a wide range of issues” The details change slightly player to player, but in the end, to sum it all up for a forum post, not a full developer but report, this effectively captures what “Issue-Minimums” is.

Second id “Issue=Minors” This one is implied but to state more clearly, it is the requirement that the library must be rebuilt. This issue will not impact everyone, as the specific problem is the library must be rebuilt. Player is fine.

As there are many servers out there, I am using a dedicated Debia VM, using the standalone version of Plex. In this install it is hard to get the version, but here is the quey I or anyone can run to identify their version of Plex Meidia Server when installed onto a Debian like OS

/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Version
OR
strings /usr/lib/plexmediaserver/Plex\ Media\ Server | grep -Eo '[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+-[a-z0-9]+'

plexmediaserver 1.41.5.9522

The data in what I have labeled “TV Shows - OLD” is present. It’s being updated. that is why I pointed out that I paused the video, then took the screenshots with old vs new. I have been playing this show for multiple episodes, hours, and as you can see the metadata on the library labeled ‘old’ is being updated. It has stored and can update effectively to know what I’m watching, where I’m at, etc. The only way that can happen is if the player is able to update the metadata on the episode. Do I have sync across all devices on? Yes, but not the point, because key here is the media server controls the metadata, and the media server. It has to read from and write to disk. But hit play? error, can’t play.

That was “Issue=Minors”.

I now realize at the end I forgot to take a picture of it actually playing. Ime stamp will be wayyyy off of the ohters, but to be complete, "YesItActuallyWorks". And yes, a well and precise manual test case example takes time.

Now to “Issue-Majors” I will; quote @jasonmcroy “I don’t see ANY mention of losing access to legacy libraries”

If this had happened after the price hike, this library would be a legacy library. It would not a have the promises made in that press release that they promised to them.

The next is a guess, cause I don’t know, but pretend scenario A it’s an oversight. People can appeal get the features back, still not OK. Too many will fil to ask, not fight hard enough, or… who know. Point is, this type of a bug, at this time, is WAYHYYYYA not OK. I fit is a bug, well I can speak from experience this is better than 90% of manually submitted reports.

If it is a business decision? even worse.

However, bug or intentional, the optics is bad here. I like it when a company is honest. I like to be personally held accountable to my actions, so I will give them every opportunity to do the right thing somehow.





Assuming the "issue’ deserved sarcastic quote mark? Not a fan, but that’s OK. If this saved someone else hours of debugging and what not, and if it makes sure they keep their promises? I will call that more than could have asked for.

@ChuckPa Thank you for taking a look! I was typing and didn’t see your question, but perhaps they are answered in my post below? (edit: above)

I will let the business aspects of your post for those better qualified to address them.

As for the technical points, I would like to get direct to the point.

Can you please do the following for me?

  1. Settings - server - General - Show Advanced
    – Make certain DEBUG logging is checked
    – Make certain VERBOSE logging is not checked
    – SAVE if any changes made

  2. Please recreate this playback issue (File does not exist / is accessible)

  1. Now download the server logs ZIP file
    – Settings - server - Troubleshooting - Download Logs

  2. Attach (Upload) the ZIP file it gives you here. I will look at what’s happening.
    – I should also be able to see the previous failures / problems.

After we resolve playback, I will also try to resolve the ongoing server activity from the logs you provide

I can fully respect that. one moment and get them your way

Plex Media Server Logs_2025-04-06_21-08-16.zip (2.7 MB)
I cleared the loggs, clicked to exact same place inthe screen shot, clicked three or 4 time to start, then navigated back, eventually found the download, an uploaded.

(small asides logging was moved into ‘console’ I guess??

@ChuckPa And because I don’t know what context matters and what is not helpful… Debian is guest on Proxmox host, no changes to networking or otherwise.

Only recent change was I blacklisted the audio drivers from the host on the GPU, but continued ot work after that.

Let me know if you need more. Thank you for looking.

Thanks for the logs.

First problem identifed.

FAT FINGERS

LOL :rofl:

Apr 06, 2025 21:08:16.003 [139803170212664] ERROR - Error parsing allowedNetworks entry '192..168.1.0\0024': Invalid argument [system:22]
Apr 06, 2025 21:08:16.003 [139803170212664] ERROR - Error parsing allowedNetworks entry '192..168.1.0\0024': Invalid argument [system:22]
Apr 06, 2025 21:08:16.003 [139803170212664] ERROR - Error parsing allowedNetworks entry '192..168.1.0\0024': Invalid argument [system:22]

192.168.1.0/255.255.255.0 is always safe notation

I roollled my eye the SECOND i saw you post that.

Also, did you know that you can’t aaply a change to MSSQL DB?

Ye… that was 5 hours of my life that just flashed before my eyes

It’s not a MySQL or MSSQL DB.
It’s SQLite3 with additional libraries added to it.

You shouldn’t be poking in there unless you fully understand the schema & interrelationships between main & blobs DBs

I ONLY edit the DBs when PMS is shut down AND I’m fixing a single item.
( I know the schema )

Sorry, conversational reference I had when it took me HOURS to find that damn a years and years ago at work. I am not touching this DB. The one DB i am using is for an unrelated project using MariaDB