Server Version#: 1.24.2.4973-7000
Today I installed the latest package for Synology DSM 7 version 1.24.2.4973-2b1b51db9 for my DS918+, updating from 1.23.4.4805.
The install seemed to go well, but after starting PMS, I’m unable to connect to my server through plex.tv.
If I launch plex through its local IP address, I get a Server Setup screen.
It appears the migration did not go as I expected.
Is there a chance that I can save my installation?
Absolutely.
Uninstall the package with KEEP option
Reinstall the same SPK
a. Select the “Plex Claim Token” option
b. Click the “Get Plex Claim Token” hyperlink
c. COPY the token Plex.tv gives you
d. Paste that token into the small window
Click NEXT
Continue through the install process normally.
This adds about 30 seconds to the normal installation time as the Installer and Plex.tv exchange authentication information.
The installer updates your Preferences.xml file with the new credentials.
It then confirms it’s claimed for you in the final pop-up as it exits.
Thanks for the quick reply.
I followed the steps exactly, and even got the confirmation that the server was claimed.
Unfortunately, I’m still unable to connect to my server. The interesting thing is that there is now a new server simply called “Diskstation”, which is I believe a new server that was setup when I navigated to the local IP address, even though I never completed any steps there.
My existing server “Pollack Home” is still showing as unreachable.
Is it possible I claimed the wrong server? Should I follow the steps again? Can I delete the “Diskstation” one?
CONTROL-F5 to force reload the Plex/web app and have it refresh the server list from plex.tv (it does not auto update)
Then, if still failing to find what you want
Go to:
a. https://app.plex.tv
b. Settings - Authorized - Devices - SERVER (dropdown)
c. Look for the duplicates.
d. Delete the older/oldest instance of the same name.
e. Force refresh the browser again.
We do this because we know the server is claimed but Plex/Web is out of sync so:
a. Clean up the server list
b. Force reload the browser window
Force reload had no effect. I also tried from another browser I rarely use, to be sure there was nothing still in the cache.
There were no duplicate servers in the list of authorized devices. I see “Pollack Home” (the one I want), and “DiskStation” (the stray new one).
Plex.tv last saw “DiskStation” , LAN IP: 192.168.1.119, 28 minutes ago.
Is this correct?
Yes, that IP address is correct. However, “DiskStation” is not the server I am hoping to see.
To be clear: “Pollack Home” is the name of the server I’m trying to connect to. I hadn’t seen “DiskStation” associated with my account until this afternoon.
One moment, I will look at the other entries.
This is going to take some investigating.
Installation procedure or update procedure ?
This might be significant
The blue menu, Update or Install ?
Update. I did a Manual Install, as I have always done, selecting the new .spk file.
There is no “PlexMediaServer” shared folder ?
There is. And there’s stuff in there.
thanks.
Logs.Right click -> Compress to Logs.zip then download and attach here please.Something silly happend
Logs.zip (231.1 KB)
I didn’t stop the server when I sent that. Should I resend?
All good.
Do you have your own cert on the box but not tied into PMS?
Aug 31, 2021 16:35:42.319 [0x7fcd12726b38] DEBUG - Connection Tester: Testing the server Pollack Home with 2 URLs.
Aug 31, 2021 16:35:42.320 [0x7fcd11c26b38] DEBUG - HTTP requesting GET https://192-168-1-119.530c35a460f84f9c97685b0623571ad6.plex.direct:32400
Aug 31, 2021 16:35:42.320 [0x7fcd11c03b38] DEBUG - HTTP requesting GET https://104-190-226-76.530c35a460f84f9c97685b0623571ad6.plex.direct:32400
Aug 31, 2021 16:35:42.354 [0x7fcd12a41b38] WARN - [CERT] TLS connection from [::ffff:192.168.1.254]:48188 came in with unrecognized plex.direct SNI name '104-190-226-76.530c35a460f84f9c97685b0623571ad6.plex.direct'; using installed plex.direct cert
Aug 31, 2021 16:35:42.358 [0x7fcd12a41b38] WARN - [CERT] TLS connection from [::ffff:192.168.1.119]:42260 came in with unrecognized plex.direct SNI name '192-168-1-119.530c35a460f84f9c97685b0623571ad6.plex.direct'; using installed plex.direct cert
Aug 31, 2021 16:35:42.365 [0x7fcd11c26b38] ERROR - Error issuing curl_easy_perform(handle): 60
Aug 31, 2021 16:35:42.366 [0x7fcd11c26b38] WARN - HTTP error requesting GET https://192-168-1-119.530c35a460f84f9c97685b0623571ad6.plex.direct:32400 (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name '192-168-1-119.530c35a460f84f9c97685b0623571ad6.plex.direct')
Aug 31, 2021 16:35:42.369 [0x7fcd11c03b38] ERROR - Error issuing curl_easy_perform(handle): 60
Aug 31, 2021 16:35:42.369 [0x7fcd11c03b38] WARN - HTTP error requesting GET https://104-190-226-76.530c35a460f84f9c97685b0623571ad6.plex.direct:32400 (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name '104-190-226-76.530c35a460f84f9c97685b0623571ad6.plex.direct')
Aug 31, 2021 16:35:42.777 [0x7fcd12283b38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.90:8008/ssdp/device-desc.xml
Aug 31, 2021 16:35:42.777 [0x7fcd12283b38] DEBUG - HTTP requesting GET http://192.168.1.90:8008/ssdp/device-desc.xml
Aug 31, 2021 16:35:42.862 [0x7fcd12283b38] DEBUG - HTTP/1.1 (0.1s) 200 response from GET http://192.168.1.90:8008/ssdp/device-desc.xml
Nope.
