Library error, your changes could not be saved

Hoping someone can shed some light onto why I’m getting this error when I add a new or edit an existing library even with just around 50 items. I have performed DBRepair (chuck) in case there was corruption but the databases is reported to be fine.

I end up selecting Cancel, and the library is added anyway.

There are plenty of resources available, CPU/RAM/Storage.

Server Version#: 1.41.0.8994
Player Version#: 1.102.0.230-7301ebfb

Screenshot 2024-10-05 at 6.35.19 pm

[Plex Media Server Logs_2024-10-05_08-3854.zip] attachment(upload://z22pwgiABxypAm1VPLOOGu6e4ld.zip) (5.4 MB)

Plex Media Server v1.41.0.8994-f2c27da23 - Debian GNU/Linux PC x86_64 - build: linux-x86_64 debian - GMT 00:00
Linux version: 12 (bookworm), language: en-US
Processor: 14-core 12th Gen Intel(R) Core™ i7-12700H

@triks_melb

See an error in your logs:

  1. Your server updated its Cert on the 4th.
  2. Your logs are showing me 10.0.1.10 gets a not-found.
Oct 05, 2024 08:26:35.013 [127706494675768] DEBUG - [EventSourceClient/mediaserver/10-0-1-10.1c668654f8bf44ab8522cafd97b76185.plex.direct:32400] Failure: 1 - Host not found (authoritative).
Oct 05, 2024 08:26:35.013 [127706494675768] ERROR - [EventSourceClient/mediaserver/10-0-1-10.1c668654f8bf44ab8522cafd97b76185.plex.direct:32400] Retrying in 15 seconds.

What’s this client? It seems to be having network connectivity problems on your home LAN to your server (.12 address)

I’ve finally upgraded Proxmox hardware and also moved to pfsense (thx for the tip :wink: hence a new server (10.0.1.16). The 2 old servers (10.0.1.10 and 10.0.1.12) will slowly be decommissioned, .10 has already been removed from authorised devices.

I won’t hijack the thread – other than to say this: :wink:

You’ll love pfsense. I have wireguard anywhere at full speeds (ipsec/openvpn are stupid slow by comparison) -AND- because I have a full on-demand tunnel, it looks like I’m at home even when I’m at your place having a beer! :slight_smile:

ipsec/openvpn is next on the agenda :wink: :beers:
Thanks for your help as always, the original issue has resolved itself somehow.
Edit: I suspect the Your changes could not be saved issue is due to timeout in the GUI, when a large amount of folders/files are scanned from a slow backend device…

Your changes cannot be saved

-and-

Something went wrong

are both the same error

TIMEOUT between the browser and the server.
(cannot be saved sometimes is also DNS error)

Just to be sure, I ran every DNS test I could find from pfsense, Proxmox server and the plex server container - all seems OK?

lxc container 300 (plex)  10.0.1.16

root@plex:~# cat /etc/resolv.conf 
# --- BEGIN PVE ---
search internal
nameserver 10.0.1.1
# --- END PVE ---

pfsense (10.0.1.1)

[2.7.2-RELEASE][admin@pfsense.internal]/root: nslookup plex.tv
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   plex.tv
Address: 34.252.212.104
Name:   plex.tv
Address: 52.51.140.217

[2.7.2-RELEASE][admin@pfsense.internal]/root: dig plex.tv

; <<>> DiG 9.18.19 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13850
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                50      IN      A       34.252.212.104
plex.tv.                50      IN      A       52.51.140.217

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Mon Oct 07 16:57:40 AEDT 2024
;; MSG SIZE  rcvd: 68

Plex Server - (lxc container)  10.0.1.16

root@plex:~# cat /etc/resolv.conf 
# --- BEGIN PVE ---
search internal
nameserver 10.0.1.1
# --- END PVE ---

pfsense VM (10.0.1.1)

[2.7.2-RELEASE][admin@pfsense.internal]/root: nslookup plex.tv
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   plex.tv
Address: 34.252.212.104
Name:   plex.tv
Address: 52.51.140.217

[2.7.2-RELEASE][admin@pfsense.internal]/root: dig plex.tv

; <<>> DiG 9.18.19 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13850
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                50      IN      A       34.252.212.104
plex.tv.                50      IN      A       52.51.140.217

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Mon Oct 07 16:57:40 AEDT 2024
;; MSG SIZE  rcvd: 68
root@plex:~# nslookup plex.tv
Server:         10.0.1.1
Address:        10.0.1.1#53

Non-authoritative answer:
Name:   plex.tv
Address: 52.51.140.217
Name:   plex.tv
Address: 34.252.212.104


root@plex:~# dig plex.tv

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65432
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                5       IN      A       52.51.140.217
plex.tv.                5       IN      A       34.252.212.104

;; Query time: 0 msec
;; SERVER: 10.0.1.1#53(10.0.1.1) (UDP)
;; WHEN: Mon Oct 07 16:54:11 AEDT 2024
;; MSG SIZE  rcvd: 68

Proxmox Node: (10.0.1.2)

root@pve:~# nslookup google.com
dig google.com
Server:         10.0.1.1
Address:        10.0.1.1#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.167.110
Name:   google.com
Address: 2404:6800:4015:802::200e

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45495
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             168     IN      A       172.217.167.110

;; Query time: 1 msec
;; SERVER: 10.0.1.1#53(10.0.1.1) (UDP)
;; WHEN: Mon Oct 07 16:55:44 AEDT 2024
;; MSG SIZE  rcvd: 55 
Server:         10.0.1.1
Address:        10.0.1.1#53

Non-authoritative answer:
Name:   plex.tv
Address: 52.51.140.217
Name:   plex.tv
Address: 34.252.212.104

root@plex:~# dig plex.tv

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65432
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                5       IN      A       52.51.140.217
plex.tv.                5       IN      A       34.252.212.104

;; Query time: 0 msec
;; SERVER: 10.0.1.1#53(10.0.1.1) (UDP)
;; WHEN: Mon Oct 07 16:54:11 AEDT 2024
;; MSG SIZE  rcvd: 68

Proxmox Node (10.0.1.2)

root@pve:~# nslookup google.com
dig google.com
Server:         10.0.1.1
Address:        10.0.1.1#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.167.110
Name:   google.com
Address: 2404:6800:4015:802::200e


; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45495
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1424
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             168     IN      A       172.217.167.110

;; Query time: 1 msec
;; SERVER: 10.0.1.1#53(10.0.1.1) (UDP)
;; WHEN: Mon Oct 07 16:55:44 AEDT 2024
;; MSG SIZE  rcvd: 55 

So it’s not DNS (that happens with some users – they can’t lookup plex.tv)

Your DEBUG logs , at the time of the “Something went wrong” / “Cannot save” will tell us more.

Yes, if you’re ingesting a lot of media and it’s hammering the DB, those DB locks will prevent your attempt to do something from completing.

You would think a 10 second window for completion is enough ?

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