If you just installed a new Plex Media Server, but it can’t be found, or you simply can’t claim it, then this might be helpfull
2 Likes
Either a firewall issue, or PMS is not running, or wrong ip entered
And would be nice if you could do the translation 
Updated to V1.1.0.0
I get this:
plex.tv Password:
plex.tv Password Repeated:
IP Address of PMS server: 127.0.0.1
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 401
Maybe this can help?
Or this known issue?
And if not, more info is needed, as well as PMS logs
Hmmm… so I tried cleaning out those entries from my Preferences file, that appeared to do nothing (yes I stopped service, removed entries, restarted, then connected directly again). It basically behaved the same way. I did notice that the prefs file didn’t get changed at all after I edited it…
The other suggestion didn’t work (it is the ClaimIT part that is failing, not the auth as the user)
Where would I find the plex logs exactly (running on readyNAS). Didn’t find anything obvious in /var/log
Not knowing ReadyNas, but take a peak here:
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Got it. So it says that it is already claimed…
IP of PMS, and are you running ClaimIt directly on that, and use 127.0.0.1 as IP when asked, or from remote, and if so, IP of workstation running it?
Yea, running directly on PMS, so using 127.0.0.1
I’m wondering if it would be easier to stop/remove/reinstall and start from scratch?
Only you can make that call, and as said, not a ReadyNas dude, so no idea if your database will be removed as well
And still haven’t seen any logs from you, so blindfolded here, and me not like 
Here’s what appeared in the PMS.log after I ran claimit:
Jul 20, 2019 16:57:20.196 [0x7f5291ffb700] DEBUG - Request: [127.0.0.1:54396 (Loopback)] GET /identity (4 live) Signed-in
Jul 20, 2019 16:57:20.268 [0x7f52e5bd8700] DEBUG - Completed: [127.0.0.1:54396] 200 GET /identity (4 live) 81ms 398 bytes (pipelined: 1)
Jul 20, 2019 16:57:22.172 [0x7f52e5bd8700] DEBUG - Auth: authenticated user 1 as RobChapman
Jul 20, 2019 16:57:22.172 [0x7f5271ffb700] DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
Jul 20, 2019 16:57:22.173 [0x7f5291ffb700] DEBUG - Request: [127.0.0.1:54402 (Loopback)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxQ_vEey (4 live) Signed-in Token (RobChapman)
Jul 20, 2019 16:57:22.173 [0x7f5291ffb700] WARN - MyPlexRequestHandler: server was already claimed
Jul 20, 2019 16:57:22.174 [0x7f52e53d7700] DEBUG - Completed: [127.0.0.1:54402] 401 POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxQ_vEey (4 live) 2ms 297 bytes (pipelined: 1)
Jul 20, 2019 16:57:22.213 [0x7f5271ffb700] DEBUG - HTTP requesting GET https://plex.tv/servers/58bb7312c6dcb4d715dc42336147eb5b794cfe43/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
Jul 20, 2019 16:57:22.986 [0x7f5271ffb700] DEBUG - HTTP 200 response from GET https://plex.tv/servers/58bb7312c6dcb4d715dc42336147eb5b794cfe43/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders
=1
Jul 20, 2019 16:57:23.009 [0x7f5271ffb700] DEBUG - MyPlex: updating with 15 access tokens
Jul 20, 2019 16:57:23.055 [0x7f52e4bd6700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jul 20, 2019 16:57:23.636 [0x7f52e4bd6700] DEBUG - HTTP 200 response from GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Please!
Not saying you didn’t find what was relevant in the log, but saying I need the full log as a zip, and not copy/paste!
And AFTER a PMS restart, then using ClaimIt
1 Like
Plex Media Server.log.zip (37.8 KB)
Your server is already claimed, and as such, a new claim is denied!
Above could be the clue
Yea, I figured. I can’t get to the server to configure it. Any options at this point?
Try editing the xml again, and make sure to save
