Server Version#:4.147.1
I changed may password and logged out of all devices earlier tonight. I can no longer claim my Plex Server. I do not have a claim server button. I have tried many of the fixes around, but have not been able to get any to work.
Any ideas?
I am very frustrated. I don’t know what to do. I’m using the linuxserver docker.
The *** clowns at Plex did this a number of years ago as well. I have no idea what the solution was as it was something related to reclaiming the token or something. It was 3AM someone posted a string of command line commands to fix it. It worked but that was over 5 years ago if not longer. I’m really sick of this company not fixing their crap.
See User Credential Reset utility.
It was here last time
Finally got it working after 4 hours.
Stop container
Open ./config/Library/Application Support/Plex Media Server/Preferences.xml in your preferred text editor
Delete entries for PlexOnlineUsername, PlexOnlineMail, PlexOnlineHome and PlexOnlineToken
Visit plex.tv/claim
Update PLEX_CLAIM env variable with new token
Start container again
I’m furious that this is a continuing issue. At min if you checkmark sign everything out they need to put a god damn warning about this crap happening. 
@c9house did you delete the entire entry or just the value?
So change to PlexOnlineUsername=“”
EDIT: Never mind I did the above. I backed up things before I did anything so worse case I reverted but this worked……again. This is just insane though.
so I changed the entries for username, mail, plexonlineHome to ““. And copied the claim token to the variable PlexOnlineToken. After that I started the container. When I tried to go to my internal Plex IP nothing showed up. Then I tried it again and I noticed that the field PlexOnlineToken was empty again. Some suggestions what I possibly did wrong?
EDIT: I found this in the logs:
Error 401 requesting XML from: https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxxxZqSrW
but I startet the container right after copying the token in the xml file and saving it.
I deleted the entire line. But I here just doing the value works as well. I also had the add the variable to my docker setup. I did not have it.
What do you mean with “I deleted the entire line“? Did you not just delete the value but the whole pair with name and value?
ah I use the Plex App from Synology App Store. Does that change anything regarding the Token?
EDIT: solved it with this prompt on my Synology Station via ssh:
curl -X POST ‘http://127.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE’
HellHello,
Like everyone else here, I reset my password following the email and lost access to my Plex servers. I’m using a QNAP TS233 NAS. I disconnected all my devices, then reconnected them, and the problem is still the same. I updated to 1.42, same thing. Finally, I uninstalled Plex from my NAS, rebooted the QNAP, and reinstalled PLEX, and the problem persists. Do you know how to access the PLEX configuration files on the NAS?
Thank you for your help.
My plex server was installed on my Synology NAS. I tried your advice, but it did not worked. I thus uninstalled Plex server from my NAS, choosing not to erase everythin, then reinstalled it. During the installation process, I was asked to provided the Plex_claim token obtained from https://account.plex.tv/claim. It works!
I did this and now to app stops running after I run it. I don’t know why
none of this is working.
have spent more than an hour on this.
what a ■■■■■■■ ■■■■-show!
edit: claim server button appeared in windows player and worked
Sorry yes I deleted all 4 lines, not just the values.
I have this message when I tried GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex
Nothing Works to solve th problem.
./UserCredentialReset.sh claim-vHDfoKTraN6hGkxsgGt3
./UserCredentialReset.sh: line 1: syntax error near unexpected token `newline’
./UserCredentialReset.sh: line 1: `’
I just edited the Plex claim value in the portainer stack and initially it didn’t make a difference, but magically after a few restarts and after I used the ip address of my existing Plex server, rather than the host name, in the browser. I was then able to claim the server back.
All good now, but the instructions about making you sign out of all devices after the password reset just seems like bad advice to me.
Had this same problem—updated my PW after Plex’s (latest) data breach and signed out of all signed-in devices, and my PMS immediately ■■■■ the bed. It wouldn’t even display server options when logged in directly. Following the “how to claim your server” instructions on this stupid and useless support page didn’t do a damn thing. I eventually made it to this thread and yep, had to fix my problem by downloading some rando script from github as recommended by others above.
And sure enough, the rando github script did the trick!
This lifetime pass holder is done. My Jellyfin LXC is working and I’m bailing. Congrats, Plex, you’ve finally driven me off. I won’t be back.
Yet another…
Using a QNAP NAS, went through all of the other “fixes”, including changing the password for Plex to the file shares, changing the claim code, removing all of the user online settings, etc.
One curiosity and possible clue to the problem is that no matter what I did, Plex would routinely log in without the entry of a password even though auto login is not enabled.
The script from ChuckPa as referenced elsewhere did the trick. It shouldn’t be this hard. In fact, changing passwords shouldn’t be hard at all.
Thanks for wasting at least 4 hours of my time.
Update: After comparing my previous Preferences.xml to the version corrected by the script, the one noticeable difference other than the new PlexOnlineToken is the PubSubServer address. My original version had 45.56.91.127, the new version has 66.175.222.206. Don’t know if it matters.
Well, for me, I have search and tried every post with no luck. At this point I would like to just start over instead of wasting time but can’t even do that. Every time I spin up a new plex server is has the same issue, server not authorized. Can we ask Plex support to delete our old Plex server reference, if that’s even a thing.
