"Your changes could not be saved" message

FWIW,

I did one show at a time to gain confidence.

Once I saw it was doing as I wanted, I gave it 5-10 shows at a time.

Did the same with Movies.

Took me less than an hour to get it all done

That’s impressive.

I have 1955 movies but I need to prune some.

Similar here

[chuck@lizum ~.2000]$ cd /nas/media
[chuck@lizum media.2001]$ find animated movies movies2 uhd -type f -print | wc -l
2054
[chuck@lizum media.2002]$ find ./tv* -type f -print | wc -l
13499
[chuck@lizum media.2003]$ 

Same issue here, except I can’t save any changes, anywhere.

Therefore I can’t enable debug logging to see what the culprit might be. After using firefox developer tools I do see ‘CORS Missing Allow Origin’ as a potential problem.

Thoughts?

@tod9f0bs1kcdw

You can:

  1. stop Plex
  2. Using the QNAP Text Editor from File Station ( right-click Preferences → Open with Text Editor (their app)
  3. Add the logDebug="True" before the closing /> on the last line.
    – If you are comfortable with the SSH shell command line, you can also use vi text editor to add that same preference
  4. Save the file
  5. Start PMS

Sound good?

I did some additional digging on this today and the culprit seems to be firefox and app.plex.tv (remote access), even with default browser settings. When testing via local network everything works fine.

Has something changed with plex web with remote access? This was working months ago (I haven’t had to make a change in 5 months, great!) and now its broken. I just disabled remote access for now and will do all changes locally. Streaming still works remotely as I have the url defined in the network settings.

ChuckPa solved my problem, I had been doing the incorrect procedure for quite some time.

He has good knowledge.

I stand corrected, its back to its broken state.

I only have one directory unlike your issue.

@ChuckPa - I’ve enabled debug logging and have been tailing the logs while trying to submit changes and no log comes up.

Note that I’m using docker on Linux and not specifically QNAP.

I’m not attaching my server logs here. Do I need to reinstall the server? Nothing has changed except auto updating the plex container. Downgrading does nothing.

I’m really starting to think this company is more about serving ads than actually creating working servers and clients.

@tod9f0bs1kcdw

I am looking at your account.

  1. Your server is not published. (Remote Access not enabled & active)
  2. You’re using your domain name to access it but it’s not going to be reliable

I have a few questions

  1. In Container Station, is the container setup with HOST or BRIDGE networking?
  2. How do you access it ? Your “Redacted”.YourFQDN.xxx" ?

Given you’re using a container, you’ll have to jump through some port mapping hoops

  • If “HOST” networking, you’ll only need to port forward from the WAN port (your modem router) to QNAP port 32400 (which will go directly into the container)
  • If BRIDGE networking,
    – Port forward from the WAN port (your modem router) to the Container’s port which is then redirected to port 32400 inside the container. (double redirect)
  1. Regardless which method, you’ll need to Manually Specify Port in PMS to tell it which WAN port your modem/router is listening on.

Regarding the logs

  1. Are you in the container → Logs directory` ? ( or in the real host directory)
  2. Did you type tail -F "Plex Media Server.log" so it continues to follow as the log rolls over ?
  1. I removed remote access today, but happy to add that back if needed seeing that the issue has been determined to not be remote only.
  2. Domain name access is fine.
  3. Bridge
  4. I have ADVERTISE_IP defined in docker which defines the host:port for access
  5. N/A
  6. I’m using a nginx poxy here, so its a bit more involved than a standard plex setup, and has been this way for years.
  7. Yes, I’m viewing the correct logs and tailing them as I’m clicking save buttons, which states ‘Your changes could not be saved’

I’ve already gone through the db restoration process if it were corrupted, but that did nothing as well.

Another relevant post.

@tod9f0bs1kcdw

Check your PM