I suggest this because, while we can optimize the database manually, PMS terminating after 15-20 seconds is extremely severe.
Specifically, I’d like to test PMS itself minus your existing data.
Open FileStation
Navigate to PlexMediaServer
Rename AppData → AppData.KEEP
Create Folder AppData
Right-click AppData → Properties
Make certain “System Internal User” PlexMediaServer has Read/Write access
Now start PMS
Let sit completely idle until the CPU calms down (it’s performing first-run setup)
When the CPU is idle,
– Open an incognito browser window
– Open PMS by the NAS LAN IP http://ip.addr.of.syno:32400/web
– Start a normal setup of PMS
– HOWEVER
– Give it a FRIENDLY NAME which won’t conflict with your existing (“TEST SERVER” ?)
– Now add some media sections and let it build.
When building is complete,
Check the settings (replicate what you had before)
Test it.
If it runs without incident then we’ve encountered a deep database error.
There is no remedy for that.
What we can do is move your watched history from the old to the new if you wish.
Once I’ve gotten to step 9 – Start a normal setup of PMS
I open plex web and the player loads but doesn’t prompt to setup a new server. It tries to load the old libraries but it’s unable to locate the media, ie the libraries are greyed out with a hazard symbol.
I feel like I’m doing something wrong
To confirm, at this stage
– Start a normal setup of PMS
I’m opening the synology NAS in an incognito browser and then loading plex from within the synology.
Sounds like you forgot Incognito. If not, then Sign-out of Plex/web
make certain you’re on the same subnet as the server (no remote or FQDN references). you need to be on 192.168.1.x
When you open with Incognito:
a. It will have you sign in.
b. Knowing there is no known server (because we renamed the folder),
c. YOu’ll be greeted by “Got It”
d. Then start the setup wizard
Yes, we can pull all your watch history from instance to instance.
I’m definitely following all of those steps, incognito, 192.198…syno.svr… logging out, renaming AppData etc but I’m coming to the same conclusion when hitting sign in via chrome incognito.
It automatically signs into my plex account and takes me to home where the libraries are greyed out.
ok, I managed to actually type the ip address correctly and go thru the earlier steps 1 thru 12
The music is playing without any issues
I’ve attached the logs from today here
192.168.1.83 is a telus wifi extender but I can’t identify …71. Do you have a trick to find the device name of the device on the network using the ip or mac address?
[chuck@lizum ~.2001]$ nmap 192.168.0.20
Starting Nmap 7.80 ( https://nmap.org ) at 2022-07-08 20:26 EDT
Nmap scan report for glock (192.168.0.20)
Host is up (0.00011s latency).
Not shown: 990 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
514/tcp open shell
2049/tcp open nfs
3551/tcp open apcupsd
8181/tcp open intermapper
8443/tcp open https-alt
9090/tcp open zeus-admin
Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
[chuck@lizum ~.2002]$
If I query the entire subnet:
sudo nmap -v -sn 192.168.0.0/24
<some entries redacted>
MAC Address: 00:17:88:B3:3D:18 (Philips Lighting BV)
Nmap scan report for 192.168.0.187
Host is up (0.075s latency).
MAC Address: 7C:25:DA:12:A9:1B (Unknown)
Nmap scan report for 192.168.0.200
Host is up (0.00033s latency).
This is for a Linux host. Synology doesn’t have nmap loaded (not needed).
If you’re using Windows or Mac, I’m sure there’s an equivalent.
I’m seeing something coming in over quickconnect (the hyperlink in package center).
Jul 02, 2022 09:05:40.465 [0x7fdfd5a60b38] DEBUG - Request: [192.168.1.89:55903 (Subnet)] GET / (21 live) GZIP
Jul 02, 2022 09:05:40.465 [0x7fdfd5a60b38] DEBUG - Completed: [192.168.1.89:55855] 200 GET /web/static/362b56e7c69551249027.woff (21 live) GZIP 1ms 63712 bytes (pipelined: 8)
Jul 02, 2022 09:05:40.466 [0x7fdfd5a60b38] DEBUG - Completed: [192.168.1.89:55903] 401 GET / (21 live) GZIP 0ms 435 bytes
Jul 02, 2022 09:05:40.466 [0x7fdfd5a1bb38] DEBUG - Request came in with unrecognized domain / IP '192-168-1-100.dbooty.direct.quickconnect.to' in header Host; treating as non-local
Jul 02, 2022 09:05:40.466 [0x7fdfd5a1bb38] DEBUG - Request: [192.168.1.89:55851 (Subnet)] GET /media/providers (21 live) GZIP
Jul 02, 2022 09:05:40.466 [0x7fdfd5a1bb38] DEBUG - Completed: [192.168.1.89:55851] 401 GET /media/providers (21 live) GZIP 0ms 357 bytes
Jul 02, 2022 09:05:40.467 [0x7fdfd5a60b38] DEBUG - Completed: [192.168.1.89:55904] 200 GET /web/js/chunk-441-b1989358201caee3597d-plex-4.76.1.22469-3117cd9.js (19 live) GZIP 47ms 648797 bytes (pipelined: 7)
Jul 02, 2022 09:05:40.532 [0x7fdfd5a1bb38] DEBUG - Request came in with unrecognized domain / IP '192-168-1-100.dbooty.direct.quickconnect.to' in header Host; treating as non-local
Jul 02, 2022 09:05:40.533 [0x7fdfd5320b38] DEBUG - Request: [192.168.1.89:55907 (Subnet)] GET /identity (19 live) GZIP
This is your workstation?
Notice the permission denied (http 401 errors)
because of what Synology did in DSM 7 with this, I would like to recommend you make a browser bookmark. In that bookmark, open plex by http://ip.addr.of.syno:32400/web. It works and avoids the problems with QuickConnect.
I’m still looking and don’t see anything which could cause the failure.
The next time it stops, would you please grab the logs while it’s still down?
Logs (2).zip (2.5 MB)
New logs attached.
The logs from the previous post were from the new test appdata folder which is why there may not have been much to report.
These are from the original appdata folder which has just been run and crashed instantly
Yes you’re correct. The last set of logs I uploaded (filename Logs (2).zip) are from the original AppData folder and not the AppData test scenario we ran.
Is the next step to reset the certificate as you suggested?
We reset your certificate at Plex.tv and you restart the server.
We stop PMS, delete the certificate it has locally, start PMS and let it download it again.
