Server Version#:1.28.0.5973-7000
Player Version#:
I was having trouble accessing my server settings while troubleshooting a LiveTV problem, so I deleted the server from the Authorized Devices list. I reset Preferences.xml file and app says “This server is unclaimed and unsecure”. Selecting the Claim Server button starts activity, but nothing ever happens.
I’ve searched the Forum and tried a few suggestions for other server platforms, but no luck yet.
did you ever get this sorted @ptfoster?
Yes, got it sorted. Had to do a soft reset of my Synology NAS, reset a couple of parameters due to the reset, then everything worked like it should.
What do you mean by a soft reset on your NAS? I have restarted the NAS, uninstalled and reinstalled Plex (multiple versions from 1.25 to 1.28) and nothing is letting me actually claim my server. Not to mention Plex is now not functioning properly on TVs throughout the house.
This all started when I updated to 1.28 like Plex was recommending when I logged in to view settings.
I tried all of that, too. Tech support finally said ”let’s open a ticket & get further help, but you might try a “soft reset” just in case that helps”. A “soft reset” is holding in the reset button for 4 seconds until you hear your NAS beep, then release & let it reboot. Don’t hold the reset button too long! If you hold it for 10 seconds it dies a full factory reset & you lose data. The soft reset resets the admin password and resets a few other parameters. Not sure what fixed the problem, but it did.
There is a Synology FAQ on the forums here in case anyone needs a link.
@mjbarthman (re)claiming a server gets covered here on the forums a lot, especially by ChuckPA, in posts with a common word like preferences.xml or claim and on the plex website article
In Chuck’s posts, the FAQ, and the article you should find a consensus if that’s okay not to paraphrase. If you still have problems, consider opening a new forum post so that you get everyone’s attention.
I followed Synology FAQ - Questions, Answers, and a few How-To’s ; everything that I could, uninstalled again, reinstalled, gave all of the permissions every time. I was able to use a ‘claim token’ but then when I went out to the ip adress/web none of the media would be present and it would want me to install a new server. Went through all of FAQ 5 this time after a full uninstall, but did not use the claim token now the server shows up in the web address. but the claim server button on the settings page doesn’t work.
Please see the attached logs
Logs (1).zip (139.3 KB)
Thanks for the logs.
I’ve found the problem.
The Synology DNS isn’t resolving (pointing to) your modem/router.
As a result, PMS can’t contact Plex.tv to complete all the tasks.
Jul 28, 2022 20:58:56.685 [0x7fa1ef6aa0] DEBUG - Subscription: Refreshed all content in 3 ms.
Jul 28, 2022 20:58:56.708 [0x7fa1ec5aa0] WARN - [HttpClient/HCl#12] HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)
Jul 28, 2022 20:58:56.709 [0x7fa1d14aa0] WARN - [AutoUpdateRequestHandler] Couldn't get update channels. Trying again soon.
Control Panel - Network - eth0 AND eth1.
Make certain they resolve to either your modem/router or google (8.8.8.8 or 8.8.4.4)
I do caution you, putting both adapters on the same subnet causes problems.
If you want to use both, I recommend a BOND adapter.
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - Network interfaces:
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 2 eth0 (172.17.2.21) (00-11-32-96-08-EE) (loopback: 0)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 4 eth1 (172.17.2.22) (00-11-32-96-08-EF) (loopback: 0)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
Jul 28, 2022 20:58:41.665 [0x7fa7236990] DEBUG - Creating NetworkServices singleton.
Bond merges both adapters into one IP address with twice the bandwidth.
(however no one connection can exceed gigabit… you’ll get 2 Gbps total bandwidth)
After PMS is claimed, I’d do this next.
It’s unfortunate you deleted everything because you didn’t need to
Thank you @ChuckPa I appreciate your assistance.
May I ask about the subnet advice? What are you recommending exactly?
Should I be opening up my subnet mask and having the second ethernet pointing to a different IP address? I am mainly using the second IP address for incoming traffic to the NAS (scanners, cameras, etc) and the primary IP address for outgoing or two way traffic (when I log in to interface, Plex, Drive, Photos, etc.) Any advice would be greatly appreciated; I am just diving into learning IT infrastructure and networking. Can’t believe I missed the DNS when I set the IP addresses to static on the NAS.
Lastly, also off the main topic of this thread. I saw in another FAQ post you made that you recommended folder structure for movies, television shows, etc. Would that perform better than proper naming of each file?
My examples would be that I currently ensure that movies are in a single folder and television shows all in a separate folder (but in bulk not broken out by series).
Again, thank you for your time and assistance.
You have two ethernet adapters on the same subnet.
This isn’t normally done on home LAN networks.
TCP/IP , especially on Synology, gets a bit wonky when two adapters respond as if one (but have different MAC addresses… which messes up message replies)
What I’m suggesting is:
For this one, I tend to go to MANUAL and use the IP address already established for the server.
This will make the network services restart – Don’t be alarmed.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
