Server Version#: 1.29.0.6244-819d3678c
Player Version#: 1.54.2.3267-d35cd36f
Like many others, I reset my password as advised and now I can’t even see my server on the player app. PMS is definitely running on the NAS. We’re on the same /24 subnet. I looked into the regedit tip but I have different HKEYs than the documentation (It’s under plex.tv instead of Plex, Inc. and the 4 documented keys aren’t even present). The app Settings section has no troubleshooting section to get to so had to access the logs manually directly from the NAS linux file system. How can I access (claim?) my stuff again? Speaking of… I am never offered a claim regardless of how many times I reset, close browsers, go incognito, etc.
PMS on a QNAP doesn’t use any window’s HKEY regedit stuff.
PMS on QNAP use a Preferences.xml file.
Not to worry. We will get you up and running again.
Your main reference document will be the Dane22 Howto ReClaim a QNAP PMS Server.
Let’s start by making sure we gracefully stop any duplicate Plex related processes.
Log into your QNAP desktop as Admin and open the App Center.
Stop the Plex Media Server.
A minute or so after it says it’s stopped, reboot the QNAP NAS.
wait 10min for it to boot
log back in as Admin to the QNAP desktop
In App Center don’t click Open if you see that, but you can Start the Plex Media Server if it is still stopped.
Now that you’ve rebooted to clean up your processes, let’s verify PMS is unclaimed.
If your QNAP PMS responds to 192.168.1.20 then you would sit at a PC and visit
http://192.168.1.20:32400/identity
doing so is the first step in your reference document, and you should see claimed="0" or very bad things, one of the two
If you’re using a docker for Plex, let us know the details.
Thanks! The identity URL definitely helped. I was not able to get the browser to ever let me claim but I was able to use the claimit script. I did have trouble with the script as it doesn’t deal well with my complex password which uses symbols (re: there’s no escapes). I could either fix script to add escapes to the chars used or dumb down the pass temporarily which I elected to do. Claimed my server and able to see the stuff on my NAS again.
Looking at the repo some more, the problem is that Dane22 is linking to the release v1.1 version of the script which does not include the encoding fix. This was resolved later that same year. ClaimIt/claimpms.sh at master · ukdtom/ClaimIt · GitHub for those out there that get stuck on this part too.