Not able to add Libaries to new installtion

Plex Media Server
1

Server Version#: 1.31.1.6733
Player Version#: n/a

I’m preparing a new installation of my plex server. Platform is Ununtu 22.04 and made a fresh install using the latest version 1.31.1.6733. Installaion went flawless. However when I did the base setup I was able to select a folder containing media files, but was not able to add the library with the message “Your changes could not be saved”

I checked all the permissions and all the other stuff, but was not able to find anything. I then started from scratch and tried to a slighty older version 1.30.2.6563 and everything works perfectly.

Is this already known? Not sure how to report that to Plex.

2

Its come up a few times on the forum. For whatever reason restarting your server AFTER the initial install and setup but BEFORE you add/create any libraries is now needed. I guess some setting is not getting saved/loaded correctly which results in this error.

Regardless, restart your plex server and you should be good to then save your library.

3

Thanks dokuro. This did the trick and I was able to add the library. Somtimes the solution is closer than you think :wink:

4

If I may add here?

There is a timing issue in the server setup which Engineering is already working on.

The agents aren’t fully initialized before allowing library creation right after initial load.

If you waited longer or just restart it then it’s ok.

5

Thanks. Are Engineering also aware that with build plexmediaserver_1.31.2.6739 upon a fresh clean install that you end up A problem has been detected with a core component of Plex Media Server ?

The only workaround I could find was to install plexmediaserver_1.31.1.6733 and then once setup was complete and server claimed then to upgrade to plexmediaserver_1.31.2.6739.

Version 1.31.2 seems rather buggy :frowning:

6

YEP. that’s one of those that happens EVERY time you try to access the server before internal initialization is complete.

It’s the Plex/web client being overly demanding and not recognizing the server is still in its Initial startup state.

Once the DB is ready and running, Plex/web will magically succeed

EDIT: Forgot to also mention that this is extremely common on slow NAS boxes (insufficient CPU to get things done quick enough)

1 Like
7

Sure, for context my server has a Intel i7-9750H (12) @ 4.500GHz, so certainly not under powered for plex :slight_smile:

I’ve also never experienced this before and I’ve setup more plex servers over the years than I can count !

8

Did you

  1. Install
  2. Immediately open Plex/web

If so, slow down. :roll_eyes: :rofl:

  1. Directories need to be created
  2. Compressed DB needs unzipping
  3. DB migrations / final setup needs completing
  4. Agents need to be downloaded
  5. Base codecs needs to be downloaded.
  6. HW tone mapping drivers need to be downloaded

That little 90 MB install file doesn’t contain everything LOL

It takes about 1 minute (for me with my 1400 Mbps service) to ready a new server but I do have a lowly xeon

9

Nope, Install - waited 2 minutes - then opened plex/web :slight_smile: I’m not a rookie :face_with_peeking_eye:

I’ve also 1GB fiber broadband and plex is running on a SSD. As I say, its always been very speedy and consistent but maybe whatever engineering are doing is slowing the whole process down.

10

I’d love to see the logs ZIP of one of your fresh servers.

I’ll find out what’s happening.

11

Will try and get you something tomorrow am (my time) – my server is now busy with family watching stuff :slight_smile:

12

I had the same issue with version 1.31.2.6739. I’m running plex as a VM on a ESXi with an Intel(R) Xeon(R) D-2146NT CPU @ 2.30GHz

1 Like
13

@anon5074910

In some other threads, I see references to various methods / workarounds

Rather than all that, Known “Beta” might be flawed (which can happen), what happens with the Public release?

If this issue can be isolated to those two builds, the number of variables involved shrinks tremendously.

1 Like
14

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