Can't Claim My Server After Password Change

Plex Media Server
21

The claim token that authorizes your server is in a config xml file within the config folder. This config file stores the server’s token in it (or a hashed version of it) so it knows what account to log into in Plex. If you want to create a new server but use the existing Config/metadata/database, deleting this file (or inserting a new token into it) and then copying your backup over the existing config folder should work.

Note: Deleting this file OR starting over both require the same steps to claim the server for yourself.

22

oh man thanks. you fixed it for me. every guide i found online was talking about registry edit and entering claim tokens in url. i had no idea what i was doing.

1 Like
23

I am genuinely livid right now, I have plex running in a container. I’ve cleared my preferences and used the webui but it still says not authorized. EVERYTHING identifying my server as being claimed has been deleated, this is ■■■■■■■ unacceptable software design because now I can’t even access my server. All because I reset my password BECAUSE OF A DATALEAK OUT OF MY CONTROL. It is unacceptable for claiming a server to be this hard, why can it not just realize its claim is invalid, and unclaim itself so that I can claim it again in the webUI. and why when i delete the preferences config file that makes it think its invalidly claimed does IT CONTINUE TO NOT LET ME CLAIM.

These past few months with plex have been unfucking acceptable, first I have to change how my music videos are accessed since music support was removed from the mobile apps. Now I can’t even use the software anymore. If every other solution for locally hosted music didn’t suck this would be the straw to break the camels back but of course I’m STUCK here because its plex that sucks the least (somehow).

Edit: I redid my entire docker container by deleting the image and all configuration. Basically having created an entire new container, and it still doesn’t work, I’m canceling my plex pass until a patch that makes server claiming FUNCTIONAL is released. Until then, ■■■■ off.

2 Likes
24

Thank you! This was the solution for me! Not sure why the Claim Token didn’t work like usually but changing my subnet to the same as my server allowed me to get to the server management and click claim.

25

If it’s of help to anyone, nothing said here was working for me (using Windows) until I simply uninstalled Plex Media Server, downloaded again, installed, restarted my server.

Good luck to anyone in a pickle!

1 Like
26

Hi Mijac, when you uninstalled did you lose any of your metadata?

27

Nothing at all. You’re just replacing the Plex Media Server ‘build’ if you like, but not touching database of your libraries. Let me know if that helps :slight_smile:

28

Thanks, unfortunately that didn’t work for me. Please media server starts fine, I can see the process running, but the page wont display. Even on localhost. Still unauthorized. I may try a restart in between the removal and re-install. The logs haven’t been helpful. This all happened after my pass change yesterday. Will continue to dig. Thanks

edit - the restart in between the removal and re-install worked. Thanks for the tip.

29

Worked for me also thanks @pshanew just weird you have to do that. I didnt even have an options to recreate a new plex server if I couldnt claim it.

Do you know if all home users will still work or will they need setting up again?

1 Like
30

Hey guys, for anyone on Synology, the following worked for me (thanks to ChatGPT getting really into the weeds):

1. Get a fresh claim token from https://plex.tv/claim (it expires in a few minutes).

2. SSH into your Synology NAS.

3. Run the following commands (replace claim-xxxxxxxx with your token):

CLAIM=“claim-xxxxxxxxxxxxxxxx”

curl -X POST “http://127.0.0.1:32400/myplex/claim?token=$CLAIM”

sudo synopkg restart PlexMediaServer

4. Verify it worked by either:

  • Opening http://:32400/web and checking that the server is no longer “Unclaimed”, or

  • Running:

    grep PlexOnlineToken “/volume1/PlexMediaServer/AppData/Plex Media Server/Preferences.xml”

Notes:

- The curl command may return “Unauthorized”, but the claim usually still succeeds.

- Always use a fresh claim token.

3 Likes
31

I had to follow this article: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

And since I’m on a Windows core install, I used Invoke-WebRequest -Method Post -Uri “http://127.0.0.1:PORT/myplex/claim?token=$CLAIMTOKEN” to complete the claim

33

This worked for me as well, thanks!

1 Like
34

I have Plex running in a docker container on Unraid. Which directory should I wget and run the utility? Also, should Plex be running when the utility runs?

35

Did you backup and restore your library settings?

36

thank you… simple and easy

37

See the instructions & examples on GitHub. Plex Media Server must be stopped.

41

Life saver! This worked for me on my Synology NAS. I just had to reclaim the server on the webapp (under server name, hit the 3 dots, then manage server).

image
image524×376 26.2 KB

42

Thank you! That worked for me. So I went inside the docker container and did the same thing.

43

Thanks azamk100, this worked! What a PITA!!

44

When I tried to execute the UserCredentialReset script, it said, “Unrecognized host type. Cannot continue.”
Any idea why that might happen?