Unable to create/edit libraries

I am having the same issues; the Meta data agents have disappeared and I cannot create new or edit existing libraries. BUT, it is only with the FreeBSD/TrueNAS Core version of PMS. The Linux version of PMS works as it should.

I found that this issue cropped up in the freeBSD PMS ver 1.40.0. I reverted to 1.38.2 and everything is functioning normally.

These issues are deff caused by software bugs and do need to be addressed and corrected.

@OttoKerner I tried to turn off the antivirus software and the problem still persists.

@phoneguyinpgh Do you know where 1.38.2 is available to download? I typically just download and install right from the browser…would I have to uninstall the current version to be able to install a previous version? Wouldn’t that delete the libraries (not the contents of the libraries, but the libraries themselves)?

Try to use a different DNS server. You can set that either in your router’s settings (preferred) or in the network adapter properties of your server machine.
You can use either 1.1.1.1 or 8.8.8.8 as known-working DNS server addresses.
After making this change, reboot the server and try again to claim it.

@OttoKerner As a reminder, I have 2 computers on the same network that both have the Plex server on them. Computer 1 has the majority of libraries but I cannot edit or add libraries (the problem). Computer 2 can edit and add libraries of computer 2, but not computer 1. I don’t think changing something higher up the chain in the network will solve anything for computer 1, as computer 2 is working the way it should.
Also, if others are having the same issue (and @phoneguyinpgh has confirmed), I don’t think my specific router would be the culprit.
I will, however, attempt to see if this can be done. My ISP installed the router, so I’m not positive I can get into it’s settings.

My recommendation still stands.

See if they offer some kind of “clean internet” filter on their side. Which is usually just a DNS server which refuses to resolve certain addresses. If you can, disable that for a while.

@OttoKerner Took a while, but was able to change to both 1.1.1.1 and 8.8.8.8. Still no change. By the way, I had an incident several years back where I thought my ISP was blocking something (a streaming TV service) and they emphatically said that they don’t do that.
Also, I did just upgrade the Plex server, as there was an update today…still no change.

I tried 1.41.0 today & it still has the same bugs, but only with the FreeBSD/TrueNAS version. My Linux PMS works fine.

Tim_Manock77; I am not using windows as the OS for any of my PMS. But I found this…

Still having this issue. Nothing has resolved it. Just didn’t want this problem to get lost in the mix of all the other problems out there.
The bummer part is I can’t add new libraries anymore because of this. So, I’m stuck. I fear that if I wipe the Plex server off my computer that’s having the issue, I can’t get my libraries back, and worse, won’t be able to create them again.

@Tim_Manock77; Here is Otto’s quick process for rolling back PMS in Windows. I would check the update directory for an old version that worked for you before uninstalling.

OttoKernerPlex Ninja (Moderator)

Apr 2018

Rolling back on Windows works as follows:

  1. note down your current Plex Server software version
  2. Stop Plex Server using its tray icon.
  3. uninstall Plex Server with the regular ‘Apps’ control panel of Windows. Do not use 3rd party ‘uninstaller’ software like Revo etc. Do not use Registry cleaners/optimizers.
  4. go to your Plex data folder .
    There is a subfolder in there, named Updates which will contain previous versions of the installer .exe
  5. execute the installer for the previous software version
  6. reboot Windows (just a safety measure, it may work without rebooting as well)

If you don’t have the old .exe file here is an archive list.

Thanks for the suggestion. The last time I successfully added/edited a library was a little over two years ago. I believe only the last three updates are kept locally. Unless there’s a place somewhere where I can download a version from two years ago, I don’t think this will work.

version 1.32.8 is from either early this year or this time last year… I’m still running it on my TrueNAS boxes. Go to the archives and download 1.32.8 before uninstalling.

Is there a place online for these archives? The locally stored updates on my computer only have 3 updates: 1.40.5.8921-836b34c27 (8/29/24), 1.14.0.8992-8463ad060 (9/12/2024), and 1.41.0.8994-f2c27da23 (9/26/2024).

The GitHUB link above has the URL’s to the old files. Honestly you probably have a corrupted database, posting logs would go a long way to figure out what is the problem.

Great news! The latest update today solved my issue! I can now edit existing libraries and add new ones! Woohoo!!

1 Like

Hi Tim, I’m happy to read that the latest update fixed your issue. Did you do any prep work before you updated, or was it just an in-place upgrade?
I am on 1.41.1.9057 and have the same issue.
I’m debating rerunning the update or downgrading to an older version first.

I decided first to try running the plex server app as an admin. That worked. I can now edit Libraries.

Unfortunate decision.
Not only will you now have to run Plex server always as admin.
But in the event that there may be at soem time a security bug in Plex, you are now more vulnerable because a process that runs in the admin context has more rights and thus can create more havoc if exploited.

Yes, it is indeed unfortunate. How do we go about fixing the bug, Otto?

To be able to go back running as a regular user, you need to reset the access permissions of the plex data folder. Of every folder, subfolder, and all files therein to default.
Here is a tool which makes this a bit easier than the default Windows tools: Resetting NTFS files permission in Windows – Graphical Utility – lallous' lab
(do it while plex server is shut down!)

Now to fix the other issue, you may need to perform this: You need to reclaim your server, but don't dare to touch the Windows Registry

Be aware of this afterwards: New Claiming Requirement for Windows