Server Version#:DSM 7.2.2-72806 Update 4
Please check that the file exists and the drive is mounted.
I wiped my yaml project and built a new one with the same results. I have signed out and reclaimed my server to no avail. I have been through my permissions and that doesn’t appear to be the problem.
I have run out of troubleshooting ideas. I was on the verge of wiping out the entire App Data file, when I thought I had better come and see if anyone has any ideas. I think there could be an issue in that App Data file, but I am unsure of where it could be.
The last piece of info that seems important is when I am in Plex and try to add a new Library (or edit an existing one) there are no subfolders under my main ones. It certainly looks like the Volume Mapping is the problem, but nothing has changed.
ChuckPa
September 26, 2025, 11:59pm
2
Do you have log files ZIP and the config file ?
We can’t help without that level of info
Docker? On Synology? That’s really doing it the hard way
services:
plex:
image: linuxserver/plex:latest
container_name: plex
network_mode: host
environment:
- PUID=10\*\*
Logs.zip (2.6 MB)
- PGID=65\*\*\*
- TZ=America/Phoenix
- UMASK=022
- VERSION=docker
- PLEX_CLAIM=
volumes:
- /volume2/docker/plex:/config
- /volume1/Data1
- /volume2/Data2
security_opt:
- no-new-privileges:true
restart: unless-stopped
I hope those help. I appreciate you taking your time.
I went to docker because when the 7.2 update happened, I lost all of my metadata and playlists and things.
Don’t post your claim token on a public forum.
Thanks. I knew I missed something.
Are you having network issues? Change an IP address or something?
Sep 26, 2025 17:10:17.925 [140588887706424] WARN - [HttpClient/HCl#b8] HTTP error requesting GET http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml (7, Couldn't connect to server) (Failed to connect to 192.168.1.177 port 49152 after 107 ms: Couldn't connect to server)
I don’t know what that is. I haven’t changed my IP. The problem started about 50 hours ago.
ChuckPa
September 27, 2025, 1:13am
9
Thanks for this:
You state the 7.2 upgrade caused you to lose all your metadata.
Did you upgrade from DSM 6 directly to DSM 7.2?
I ask because upgrading from any of the DSM 7.x → 7.2.2 never causes loss of data. There are no runtime changes.
If so, there is a well documented procedure for upgrading which moves everything to DSM 7.x without data loss. Might you have missed this?
I can guarantee it. Anyway, I went over to docker and it’s been smooth for over a year. Then two days ago, all hell broke loose. I really don’t want to rebuild all of my playlists and stuff if I can avoid it.
ChuckPa
September 27, 2025, 1:35am
11
Going through your logs.
Recommend:
Sep 26, 2025 16:14:24.541 [140588945226384] DEBUG - Network interfaces:
Sep 26, 2025 16:14:24.541 [140588945226384] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Sep 26, 2025 16:14:24.541 [140588945226384] DEBUG - * 3 eth0 (192.168.1.142) (00-11-32-BD-F4-4D) (loopback: 0)
Sep 26, 2025 16:14:24.541 [140588945226384] DEBUG - * 4 eth1 (192.168.1.141) (00-11-32-BD-F4-4E) (loopback: 0)
Sep 26, 2025 16:14:24.541 [140588945226384] DEBUG - * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1
Communication with modem/router (192.168.1.1) is good
Device at 192.168.1.177 is having problems. it advertises then fails to respond to query.
Sep 26, 2025 17:00:06.770 [140588864502584] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml
Sep 26, 2025 17:00:06.774 [140588887706424] WARN - [HttpClient/HCl#a5] HTTP error requesting GET http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml (7, Couldn't connect to server) (Failed to connect to 192.168.1.177 port 49152 after 3 ms: Couldn't connect to server)
Sep 26, 2025 17:00:20.913 [140588889815864] DEBUG - Statistics: Flushing 3 expired bandwidth entries, 1 expired media entries.
Sep 26, 2025 17:00:45.776 [140588864502584] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml
Sep 26, 2025 17:00:45.781 [140588887706424] WARN - [HttpClient/HCl#a6] HTTP error requesting GET http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml (7, Couldn't connect to server) (Failed to connect to 192.168.1.177 port 49152 after 4 ms: Couldn't connect to server)
Sep 26, 2025 17:01:15.780 [140588864502584] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml
Sep 26, 2025 17:01:15.785 [140588887706424] WARN - [HttpClient/HCl#a7] HTTP error requesting GET http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml (7, Couldn't connect to server) (Failed to connect to 192.168.1.177 port 49152 after 4 ms: Couldn't connect to server)
Sep 26, 2025 17:01:48.778 [140588864502584] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml
Sep 26, 2025 17:01:48.780 [140588887706424] WARN - [HttpClient/HCl#a8] HTTP error requesting GET http://192.168.1.177:49152/jtXyjNWDT4/wps_device.xml (7, Couldn't connect to server) (Failed to connect to 192.168.1.177 port 49152 after 2 ms: Couldn't connect to server)
Logs:
.1.log - Ordered to shutdown
.2.log - Ordred to shutdown
Can you please show me the error? (Screenshot it somehow)
I’m trying to find a playback request. I only see a couple authenticate messages from other users. I see no actual playback.
Is this what’s happening?
QUESTION: Whose image are you using?
ChuckPa:
192.168.1.177
Sorry that took so long.
The reason for the two IPs is that I have an Synology expansion. That is the other volume.
You are right. There is no playback happening at all.
The image is linuxserver.io
I’m not sure what the 192.168.1.177 is, but I am trying to locate it.
ChuckPa
September 27, 2025, 2:26am
13
Using PMS, go to Plex/web → Library section - Get Info.
Look at the path it’s telling you.
Now, get to the command line and get into the container
In the container, that path should be readable.
If it is, show me the ls -la of it. Also get the ls -la of the directory containing it
total 56
total 0
ls: cannot access ‘data2’: No such file or directory
ls: cannot access ‘volume2/data2’: No such file or directory
total 0
total 56
drwxr-xr-x 1 root root 0 Aug 19 21:04 lib.usr-is-merged
drwxr-xr-x 1 root root 0 Sep 9 19:11 mnt
total 0
total 0
drwxr-xr-x 1 root root 378 Sep 26 15:58 ..
So, My last working build had my volume set up as
volume1/Data1
volume2/Data2
That spans both the NAS and the expansion. From there, I could Add a Library in Plex and it would see the subfolders contained within.
ChuckPa
September 27, 2025, 3:26am
16
This tells me what’s going on.
Your docker config does not have a top level directory definition for /films
You show :
volumes:
- /volume2/docker/plex:/config
- /volume1/Data1
- /volume2/Data2
security_opt:
You forgot to add (map) /films
First step here is to fix that in your config spec.
So, here is something weird. It is pointing to /films, but on my server it is named Films. I wonder if that is what is causing my problems? I am renaming everything to be lowercase and then I will rebuild accordingly.
I can’t thank you enough for your guidance, and I’ll keep you posted if that doesn’t fix the problem.
You are awesome!
After such a painful process, I’m thinking about going back to the native server in Synology. Do you happen to know what folder the app data will set up so that I can copy the Docker app data into it?
ChuckPa
September 27, 2025, 5:23am
19
Linux is CaSe-SENsitive
/volume1 != /Volume1 – Those are two separate directories
Windows is the only OS (NTFS) where case doesn’t matter.
I’m the engineer who maintains Plex running on Synology (DSM 6 and now DSM 7). I wrote the installation packaging (menus and all the control scripts which run behind the scenes)
I have sufficient Linux skill to take the existing Docker database, which has different pathnames than native Plex configuration, and edit the databases to work properly with a normal DSM 7 native installation.
Given your linux skill limitations, I think Docker was the wrong choice and therefore getting you back to a native package environment , where the DSM pathnames match what PMS reports, makes the most sense as the next step
Your thoughts?
Agreed. I installed the native package. I have started to move the metadata files to the PMS Metadata folder. The web app can’t find any library files at the moment. I was reading something you’d written about it being an internal user, but I didn’t make it all the way through. I need to figure out how to get the permissions set.
Always has been