"Your changes could not be saved" when adding/ editing/ deleting library paths

Server Version#: latest stable
Player Version#: n/a
I’ve replaced a file server. It now also hosts plex. Previously the files where on a shared device on the LAN. Basically, plex media server and the media files are on the same PC server,

So, now I need to change the library paths. But, all I get is “Your Changes Could Not Be Saved”, whether adding, deleting or attempting editing of the path strings.

user plex owns the directories and files

user permissions are set with ACL

my user account has rwx permissions

In a measure of desperation I have chmod’d all files and directories to 0777

Nothing is helping and now plex cannot access media.

What to do?

UPDATE:

Desperate times- the new install runs on a cloned image from the previous system What I have done is to symlink the new library paths to mimick the old system. For example, the old system used autofs and the library was at /cifs/fileserver/plexmedia, which is now a symlink to the new location on the plex host.

I secured the file system and plex is now scanning the media files from the symlink.

Not what I had in mind, but will do for now. Nevertheless, a proper solution of plex being able cope with library path changes would be nice.

PMS easily copes with path changes.


Changes cannot be saved:

  1. Check overall path length. Limit is 40K bytes
  2. Make certain DNS and gateway working correctly on the new host.
  3. Directory permissions 755, files 644.
find /media/dir/1 /media/dir/2 -type d -exec chmod 755 {} \;
find /media/dir/1 /media/dir/2 -type f -exec chmod 644 {} \;

You can add as many top-level directories as you need
You can also apply this to the Plex directory (where your server metadata is)

Regarding “Moving your media and keeping the metadata” guidelines, those were followed. I’d been there before and was caught out.

Regarding file system checks, it reports things are as they should be. Maybe I’ll just leave the symlink option as described.

Solved with PlexDBRepair script.

Thanks for letting me know. That’s weird :slight_smile:

The DBRepair result is probably co-incidental; digging around in the server log I see a lot of “transaction held too long. Giving up” error messages. They coincide with whenever I tried to save a library path change. Maybe I should exercise a bit of patience until scanning and other processing on the new server catches up (?).

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.