Error when attempting to edit an existing library -> "Your changes could not be saved."

Server Version#: 1.31.2.6739 & 1.31.1.6733
Player Version#: 4.102.1 & 4.100.1 (empty browser cache tested)
OS#: ubuntu 22.04 64bit

Within both the current beta (1.31.2.6739) and public (1.31.1.6733) builds I can no longer save any library settings (movie, tv or music).

Screenshot from 2023-03-05 15-47-45

This is outputted to the logs but full logs can be provided via DM if requested:

Mar 05, 2023 15:27:14.825 [0x7f6abcc9eb38] ERROR - [Req#3c4d1] Errors in PUT request: <html><head><title>Bad Request</title></head><body><h1>400 Bad Request</h1></body></html>'agent' is missing or invalid
'language' is invalid

I’m using English (UK) language. I’m not able to edit any library and change its settings.

BTW… also attempted to use the plex for linux client (Version 1.65.1.3596-7b1f6d97) and the same error happens.

@ChuckPa fyi as requested

Attempting to recreate now on fresh install

Thanks – if your doing a fresh install try 1.31.2.6739 and see if you get the → “A problem has been detected with a core component of Plex Media Server.”

@anon5074910

I just got that bug too.

Reproduced it 3 times just to be certain.

Already written up. #14177

1 Like

Which one :wink:

Can’t save settings or problem detected or both?

I can’t setup a server at all.

The “unable to save settings” is my next trick :slight_smile:

1 Like

Trouble is restarting server is no longer working for this subsequent edit of a library settings.

I restarted the server. Was still unable to create the server

1.31.2 will never work on a fresh install. Roll back to 1.31.1 to create the server and then upgrade once claimed.

Restarting works for me.

Alas, not for me. I’m on linux so that could be a factor …

Can I get your DEBUG logs please?

I’d like to add them

I scrubbed my logs early today and didn’t bother keeping them so what I have now is probably not useful, sorry.

I may have some time tomorrow am so can get you some logs off a test server I have.

If you have it failing on a ‘fresh’ install (where username, group, and /usr/plexm* /var/lib/plex* don’t already exist), that would be great.

That’s what I captured today in 3 different environments with two different browsers

1 Like

Got you some logs which will hopefully help in finding this problem. This is what I done …

ubuntu 22.04 64bit - chrome empty browser cache using local device IP for setup:

  1. clean fresh install of plexmediaserver_1.31.2.6739-a87e876bd_amd64.deb – failed initial setup – logs within folder Logs-plexmediaserver_1.31.2.6739-FAILED of zip.
  2. clean fresh install of plexmediaserver_1.31.1.6733-bc0674160_amd64.deb – success – logs within folder Logs-plexmediaserver_1.31.1.6733-SUCCESS of zip.

Plex was removed and purged between tests sudo apt remove --purge plexmediaserver.

One other thing I noticed doing these tests back to back that was using the bad build 1.31.2.6739 this screen never appeared. Maybe the endpoint which that build is looking for has changed blocking the rest of the setup …

Anyhow, IMO 1.31.2.6739 should be pulled from the beta channel – there are now so many threads with this “A Problem has been detected …” error.

plex-logs-6th-March-2023.zip (254.0 KB)

Version 1.31.2.6757 seems to have fixed both of these problems so closing this thread out. Thanks.

@anon5074910

This is a regression. ( Just finished server team meeting )

Bouncing around between versions causes the broken pieces to fall into place.

It’s not ‘solved’. It is priority 1 for the team and will be put into current PlexPass beta and upcoming release prior to release to PlexPass being pushed to Public.

2 Likes

Thank you!

Recommendation to all -

Use Public release for now.

1 Like