# Your changes could not be saved **URL:** \ **Category:** Plex Media Server\ **Tags:** server-linux, server-docker\ **Created:** [June 3, 2023, 1:35am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228 "2023-06-03T01:35:57Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 3, 2023, 1:35am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/1 "2023-06-03T01:35:57Z")
Server Version#: 1.32.3.7089 For some unusual reason, currently, whenever I try to make a change within the server, I get: “Your changes could not be saved.” ![image](https://global.discourse-cdn.com/plex/original/4X/7/f/3/7f32d3b1ca46d44885345771a71d1ff3e6f8b1bf.png) I can’t see any issues with permissions. Currently running in Docker, on an Ubuntu 22.04 host. ```yaml ######## ##Plex## ######## #Plex - Media Centre plex: image: plexinc/pms-docker:plexpass # image: plexinc/pms-docker:public #change to this if beta is ■■■■■■ - https://hub.docker.com/r/plexinc/pms-docker/tags/ # image: linuxserver/plex container_name: Plex hostname: LexPlex environment: - TZ=$TZ - PLEX_UID=$PUID - PLEX_GID=$PGID # - PUID=$PUID # LSIO # - PGID=$PGID # LSIO - VERSION=plexpass # - VERSION=latest # LSIO - ADVERTISE_IP=http://$SERVER_IP:$PLEX_PORT,https://plex.$DOMAINNAME # - ALLOWED_NETWORKS=$NETWORK_NETMASK,$DOCKER_NETMASK #- PLEX_CLAIM=$PLEX_CLAIM #https://plex.tv/claim - NVIDIA_VISIBLE_DEVICES=0 - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility runtime: nvidia devices: - /dev/dri:/dev/dri logging: driver: "local" options: max-size: 10m max-file: "3" # deploy: # resources: # reservations: # devices: # - driver: nvidia # capabilities: [compute,video,utility] # device_ids: ["0"] security_opt: # - no-new-privileges:true - seccomp:unconfined #optional volumes: - $PLEXDIR:/config - $RAMDRIVETDARR:/transcode - $MEDIADIR:/Media - $PLEXBACKUPDIR:/PMSBackup - $PREROLLDIR:/PreRoll labels: # - backup - autoheal=true - "traefik.enable=true" ## HTTP Routers - "traefik.http.routers.plexms-rtr.entrypoints=https" - "traefik.http.routers.plexms-rtr.rule=Host(`plex.$DOMAINNAME`)" ## Middlewares - "traefik.http.routers.plexms-rtr.middlewares=chain-no-auth@file" ## HTTP Services - "traefik.http.routers.plexms-rtr.service=plexms-svc" - "traefik.http.services.plexms-svc.loadbalancer.server.port=$PLEX_PORT" ## Flame Dashboard - flame.type=application # "app" works too - flame.name=Plex - flame.category=Media - flame.icon=https://raw.githubusercontent.com/modem7/MiscAssets/master/Icons/HeimdallIcons/plex.png networks: pihole: ipv4_address: '172.22.0.113' ports: - "$PLEX_PORT:$PLEX_PORT/tcp" - "3005:3005/tcp" - "8324:8324/tcp" - "32469:32469/tcp" - "1900:1900/udp" - "32410:32410/udp" - "32412:32412/udp" - "32413:32413/udp" - "32414:32414/udp" restart: always ``` I’ve tried both public, plexpass, and LSIO versions, just in case, but no go. I’ve attempted repairing the DB, but no errors show up. Tried disabling seccomp, no go. ```auto ❯ ls -la total 565540 drwxr-xr-x 2 alex docker 4096 Jun 3 02:28 . drwxr-xr-x 7 alex docker 4096 May 27 2020 .. -rwxr-xr-x 1 alex docker 77824 May 27 2020 com.plexapp.dlna.db -rwxr-xr-x 1 alex docker 32768 May 27 2020 com.plexapp.dlna.db-shm -rwxr-xr-x 1 alex docker 2010592 May 27 2020 com.plexapp.dlna.db-wal -rwxr-xr-x 1 alex docker 414978048 Jun 3 01:00 com.plexapp.plugins.library.blobs.db -rwxr-xr-x 1 alex docker 32768 Jun 3 02:28 com.plexapp.plugins.library.blobs.db-shm -rwxr-xr-x 1 alex docker 0 Jun 3 02:28 com.plexapp.plugins.library.blobs.db-wal -rwxr-xr-x 1 alex docker 160833536 Jun 3 02:28 com.plexapp.plugins.library.db -rwxr-xr-x 1 alex docker 32768 Jun 3 02:35 com.plexapp.plugins.library.db-shm -rwxr-xr-x 1 alex docker 1087712 Jun 3 02:34 com.plexapp.plugins.library.db-wal ``` Not quite sure where the issue may lie. Unfortunately, I can’t upload debug logs, because I can’t change the setting to enable it. [Plex Media Server Logs\_2023-06-03\_02-38-50.zip](https://forums.plex.tv/uploads/short-url/wtaTgeTcSw5TWlhTd4Qbu0lszmb.zip) (727.4 KB) * * * Seems others are experiencing the same issue: ```auto https://forums.plex.tv/t/your-changes-could-not-be-saved-for-all-preferences/828793 https://forums.plex.tv/t/your-changes-could-not-be-saved/826556 https://forums.plex.tv/t/bug-your-changes-could-not-be-saved/834843 https://forums.plex.tv/t/your-changes-could-not-be-saved/831396/20 https://forums.plex.tv/t/pms-your-changes-could-not-be-saved/832110/9 ``` ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 3, 2023, 2:12am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/2 "2023-06-03T02:12:06Z")
You can stop PMS. Edit “Preferences.xml”. On the last line, before the closing `/>`, add `LogDebug="1"` It will look like this: ```auto SomePref="Value" LogDebug="1" /> ``` Now start PMS and you’ll have [DEBUG logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1), ([DEBUG logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) is on by default so at some point you turned it off) ---
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 3, 2023, 2:31am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/3 "2023-06-03T02:31:48Z")
> [@ChuckPa](#): > > Preferences.xml Ah sweet - that did it, thanks! [Plex Media Server Logs\_2023-06-03\_03-31-03.zip](https://forums.plex.tv/uploads/short-url/fyYIvW0ZciIIwp13ZPQCOhmDJ1k.zip) (2.1 MB) Aye, I try to reduce logging as I’m on an SSD - so the fewer writes, the better if they’re not needed for day to day operations. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 3, 2023, 3:31am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/4 "2023-06-03T03:31:17Z")
It looks like you’re using proxy and a FQDN where PMS does not have the FQDN cert added Is this what you have? ---
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 3, 2023, 3:53am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/5 "2023-06-03T03:53:13Z")
I’m currently using traefik reverse proxy which handles/terminates the https/ssl side of things, and routes it to plex http. It’s been working well for a number of years now with this setup. I’ve disabled remote access as well, as traefik routes traffic to the internal network. Although locally (which is how I interact with plex 99% of the time), I’m not accessing via the RP. ---
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 5, 2023, 9:05am UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/7 "2023-06-05T09:05:16Z")
Just in case it’s useful, here’s the latest logs: [Plex Media Server Logs\_2023-06-05\_22-59-51.zip](https://forums.plex.tv/uploads/short-url/A3mgwUcqQh6bNV6mTmgwOuR1DQs.zip) (4.7 MB) And more error messages: ![image](https://global.discourse-cdn.com/plex/original/4X/e/5/4/e54becd3c1bfdac4e2a74acb53977e74f0260aa2.png) ![image](https://global.discourse-cdn.com/plex/original/4X/2/6/e/26e60807bc2cc878aa91d371f160b9020d131954.png) ---
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 5, 2023, 10:14pm UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/8 "2023-06-05T22:14:39Z")
Potential cause found: I currently have my PiHole routing [http://192.168.50.254](http://192.168.50.254) to [http://hda.home](http://hda.home). Initial investigation seems to show that if I go to [http://hda.home:32400](http://hda.home:32400) the error occurs, and if I go back to [http://192.168.50.254:32400](http://192.168.50.254:32400) the error doesn’t seem to occur (will continue to monitor in case the error comes back). Is this expected? And if so, why? If not, is this something that could be added to the bug board for further investigation? This seems to be a recent issue as the change was made a couple of months back with no ill effects. weblog with changes made from both IP and local DNS record: [local\_weblog.txt](https://forums.plex.tv/uploads/short-url/d8DpCOc4JkFZJvyqUT2Pw4NLI7p.txt) (102.4 KB) [dns\_weblog.txt](https://forums.plex.tv/uploads/short-url/zQi9PSZHFiI1wVfgWCClNX6MClx.txt) (415.0 KB) ---
**Author:** ![modem7](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@modem7](https://forums.plex.tv/u/modem7)\ **Post date:** [June 5, 2023, 11:07pm UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/9 "2023-06-05T23:07:40Z")
Looks like the issue was actually Unbound and DNS rebinding protection. > **[Can't connect to Plex directly due to Unbound](https://dietpi.com/forum/t/cant-connect-to-plex-directly-due-to-unbound/5199/3)** > > That’s done the trick, thanks for pointing me in the right direction. I can see from the other thread the OP never responded to your last question about confirming what was done. For me I simply did the following… nano... [https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/](https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/) I had overlooked the fact that I recently switched from DNSCrypt to Unbound, and didn’t link this issue and the change together. By following the advice on the dietpi link, my `primaryServerUrl` went from my RP’s domain to ` "primaryServerUrl": "https://192-168-50-254..plex.direct:32400/"` and all is now working. Will mark this as closed for now, with the cause being DNS rebinding protection. ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [September 3, 2023, 11:08pm UTC](https://forums.plex.tv/t/your-changes-could-not-be-saved/843228/10 "2023-09-03T23:08:31Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.