Server Version#: 1.31.1.6716
Player Version#: Both Web v 4.101.1 and PLEX v1.64.2.3546-5107ec40. Also had the same issue starting with the last versions of both, IIRC.
Very recently, for the first time in my decade of using Plex I got this “Your changes could not be saved” error. I get it if I try to edit the folders contained in a library. I get it if try to enable or disable library settings etc.
I found a couple threads that might be relevant:
I have restarted the Plex server AND physical Windows10 server multiple times. Didn’t fix it.
This post is almost 3 years old and it involved doing some DB surgery. I don’t know if this is still relevant or not, but before I go down this road I want to find out if there is something simple I’m overlooking.
I am experiencing the same issue. I moved several TB of content from one set of drive to another and trying to change the drive letter on the library has failed with the “Your changes could not be saved.” message.
I am running 3 servers. I was able to change on server 1 just fine (1.31.1.6716).
Server 2 (1.31.0.6654) allowed me to change 0 libraries, server 3 (1.31.0.6654 > 1.31.1.6716) allowed 1 library only after the patch.
I just installed a fresh copy of Windows 10 and the latest Plex software and I too cannot add folders to my library. This is a major issue and I see at least one other person reported it 3 days ago and nobody has responded.
I don’t know what any of this means to be honest. I do have a UniFi network, but that’s not new. I’ve had it a few years, but have never seen this issue before.
I’ve also been having this problem in recent days. Is this just something that will go away after a few days or the next update? I’ve done all the restart and other troubleshooting suggestions with no success.
I found that if I change the SCANNER from Plex Movie Scanner to Plex Movie, I am allowed to save. I did update the other bug post with this same information.
OK update from my side: I changed nothing, but was able to apply the changes i wanted to make yesterday. so i am out of here thank you all anyways!! best regards, tom
I’ve just performed a server update (to Version 1.31.3.6868) and this seems to have fixed my problem. I generally keep the server software up to date and the problem existed on at least the previous 2 versions, I think more but can’t say for sure.
Maybe this is good new that the Plex team have resolved the bug. Fingers crossed for everybody else who’s been suffering from this.