I fear you are correct Otto, in which case, you should click on the unclaimed server from the list, then click on Remove.
I removed the unclaimed server through the server settings.
Now I just have to set up remote access and unpin every folder that points to the old server, and repin every folder of the new server, on every app for every user lol. And of course this will be interesting again if Plex roll out a fix for unclaimed servers, because when removing it said this server will appear again if it is available 
Thank you for your time @trumpy81 , very much appreciated.
You are welcome and my apologies for the rookie mistakes, don’t know where my head is right now … lol
Happy Plexing! 
I don’t have a Claim Token Button… why does it come up for some people but not me?
Hello i have same problem and cannot claim my server back, it grey button, who can help please
This is all fine and dandy (not) - any help for the asustor folks here?
I have no idea how i found this but thank god i can access my library again
Thanks for the idea!
I reach my PMS both from LAN and remote using Nginx and certificate from my public domain. Due to this mess the DNS returns 502, but service is reachable via local IP. I tried using my DSM by going there via IP as well and… installation actually seems to work! I am being prompted now. For now, I will wait with update until I have claimed my server back. Good thing to know though. Many thanks!
after the password reset, I could claim my server but the issue still persists. From mobile devices I can access the server and content, but from my TV (Android set top box), the server shows up with a red triangle warning sign and nothing happens when I select it. No content, no libraries. Can someone please help?
The server runs on Ubuntu Linux
Came here for the exact same issue. I can see my library on my PC but can’t access from my TV right in front of me. 
I thought it was just me!
You did try this via ssh on your NAS? Did you use sudo?
I did all of these steps and never got an unclaimed server button. When I restart, I just click Open Plex and it lets me log back in. I still can’t see anything on my TV but everything came back on my Win11 pc. I’m not super technical beyond RegEdit updates and I read what is noted below for DSM 6 but none of that means anything to me. Changing a password shouldn’t break a product. I’m not sure where to go from here with my limited tech capabilities. I should have just left it alone.
SSH, no sudo. In the end I fixed it using WinSCP with the following steps:
- Completely delete preferences.xml while the server is stopped.
- Start the server.
- Stop and restart server again.
Now I had a claim server button for a duplicate of my server, same name, same everything. Claimed it, removed the old unclaimed one, and I’m back up and running.
Same. I tried what I could understand but this is all over my head as well. I’m very frustrated. This all worked perfectly until it didn’t. My server remains claimed and I can see my libraries on my Win11 pc but can no longer access from my Amazon Fire Cube. I even tried deleting and re-adding the Fire Cube app thinking it was my own issue. I hope that Plex does the right thing and issues an update that fixes this for those of us who aren’t so tech saavy.
Fire Cube is a different issue for me. Just learned what I could on the forum, applied what I could and got lucky. Had to re log into both Samsung tvs but that was minor. Good luck!!
lifesaver, thank you!
For what it’s worth – On a Synology NAS running DSM 6, after reading through all posts on this thread many of the solutions did not work for me (Preferences.xml edit, no claim option, sign out of all and back in, etc.) - The only solution that did work was running this UserCredentialReset.sh script.
There have been similar reports for Android devices.
What has worked for some:
Reboot the Plex server.
Then, after the server is back online, force quit and relaunch the Plex Android TV app (or reboot the Cube).
After spending time troubleshooting this yesterday, I just kind of gave up and walked away from it for a few hours. Came back for one more try and it works now. Maybe it was all just slow on the back end because so many people were changing their passwords at once. But it seems to be all good now. Thank you for jumping in with so much helpful advice.
I run the UserCredentialReset.sh utility but it did not work either.
