Yea, I stopped the server, edited the file, restarted. no effect. And my changes are still there (those PlexOnline... values are gone)
FWIW I can still see the server listed under his account. It’s just been down for a while…
Then sadly no more clues…If ClaimIt get’s a 401, it in 99,9 % of the times means it’s already claimed, and claiming info indeed held in the xml file…
But when said, if preferred to loose sharing, but not metadata, try this:
Power down PMS, and then rename XML file to .old
Then power up PMS again, and it’ll be considered a new fresh PMS, but with it’s database intact
no difference, but I do have a MUCH smaller XML file!
The behavior I am getting is I go to the URL, it redirects to plex.tv to authenticate. I authenticate as my dad, and it goes back to his server. From there I can only see my shared server with him.
WAIT! the script now worked.
I think I am in business…
1 Like
Why on earth did you not auth as you?
It’s his server.
ROTFL, and makes sence
Thanks for all the help. Everything looks good right now!
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
Having Trouble Claiming a server that had previously been working. After Updating QNAP firmware and Server versions I Can not get the server to Claim. I tried the claimpms.sh shell script and got an internal server error. I Have tried Changing the DNS to 8.8.8.8 and 8.8.4.4, which didn’t change anything. I have noticed the same server is currently not populating Artwork for content locally on the NAS but the plex streaming content does have artwork. QNAPplex Logfile 20201208.txt (22.8 KB)
Sorry, but the logfile you attached, is from the webclient, and the screendumps makes it hard to read and search
What I need here, is for you to provide the output from the claimit.sh script in a screen dump, and did manage to spot on you screen dumbs, that you are faces with curl error 7, meaning
CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.
So start by checking your QNAP DNS Settings, as well as the default gateway first, before providing what I asked for
plex.tv Password:
plex.tv Password Repeated:
IP Address of PMS server: 192.168.1.109
Comparing entered passwords
Comparing entered passwords ok
Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 500
Tried this with Both DHCP IP settings and Static. For DNS I used 8.8.8.8 and 8.8.4.4 using Google DNS it took much longer to give the fatal error message.
So, since you did manage to get the user token from plex.tv, I would assume that your gateway as well as DNS is okay
However, the 500 error is an internal PMS error code, so please look here on item 1 and 2:
