Something happened to my Plex install on my Synology NAS and I ended up reinstalling it. Now when I run through the setup wizard it is throwing an error that it is unable to claim the server. I have uninstalled and reinstalled multiple times making sure that I deleted the share/user etc. I have tried both the package available from Synology as well as the latest Synology package from Plex, nothing is working. I am thinking there is something left over that I am missing in the uninstall process related to the token or something but I am not certain. This is not a network connectivity issue as my Synology is available remotely and I also have an Ubuntu VM running another instance of Plex as well that is working just fine, it is something wrong with the Plex install on my Synology. I have been pouring over forum posts and nothing has worked yet. Any ideas? Thanks in advance, Jesse.
Go to app.plex.tv -> Settings -> Authorized Devices - Servers (dropdown)
Delete the old server name (REMOVE button).
Plex/web is still looking for that one which you deleted.
By deleting it, the web client won’t confuse your Syno’s hostname with it. ( Default friendly name is the host name and there is a collision )
Also, after doing this,
- Sign out of Plex/web
- Open an incognito window to the Syno’s IP address :32400/web
Thanks for the suggestion, I did what you suggested however now when I try to claim the server in an Incognito window it asks me to sign in, which I do, and it spins for awhile and then states that there was a problem signing in.
Now we’re onto the root cause.
Please manually grab the log files and attach them.
Here you go.
PMS Server Logs.zip (147.8 KB)
Also just FYI I tried claiming the server from multiple different systems, one that had never been to the site before, cleared browser history etc. and they all had the same result. I also tried renaming the preferences.xml file to preferences.xml.old and starting the service again to recreate the file with no luck. I looked through the logs a bit and I see curl parsing errors as well as something about content length is -1 of -1 or something like that, which does not sound right to me but I am not sure what to do about it. Verbose logging is not currently enabled BTW.
I am concerned about the host IP. 192.168.0.254 ??
I also do not see any inbound traffic attempting to authenticate (from your browser)
Thanks everyone, I was able to figure out the issue. I have my Synology joined to a Windows Active Directory Domain and when you join a domain Synology sees fit to have you specify the DNS settings in the Domain area of the control panel instead of the Network area of the control panel (which is really stupid if you ask me, why would they move settings around depending on how you configure it?). I had decommissioned the domain controller that the Synology was pointing to for DNS/NTP and because it was an AD integrated DNS zone when I demoted the domain controller that meant it was no longer a DNS server so the Synology was not able to resolve DNS names outside if its local subnet, however it did not affect any of the external access as the firewall was still successfully able to route external traffic to the Synology and I had not checked name resolution via SSH on the Synology because all of my other systems were working fine and DNS was correct on the Synology in the network area of the control panel. As soon as I remembered the other area to specify DNS when joined to a domain I switched DNS to a valid DNS server and I was able to claim the server.
Thanks again, pointed me in the right direction.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
