I just received the email from plex “Action required: Notice of a potential security incident”. As such, I changed my password and it logged all of my plex sessions out on all devices, and the plex media server as well as the email indicates. Not sure what to do now. I sign back in to plex.tv with my account new password and it works, but none of my libraries are available; under account settings it says I am signed in. If I go to the lan ip of the plex server (ie https://ipaddress:32400/web) it won’t even load, it comes up with a ERR_CONNECTION_TIMED_OUT page. It has only done this since this password change and force log out. I restarted my qnap to see if that will help, but no go same message. The plex app is started, and waited a bit to make sure it would be running. This was all working fine before the password change and logout as I was actively watching a movie on Plex.
Since changing my password per the email, I have re-installed Plex media server and Plex multiple times on my Windows PC. I even tried installing the Plex media server beta, but I have not been able to access my libraries. I deeply regret changing my password.
Same here. I’m about to through this piece of ■■■■ out of the window. Have tried following several help articles about clearing up the Preference file, restarting the server, signing out and back in. My server is simply gone after the password reset. How is that even possible? Is the server authenticating towards the Plex cloud via my password?! Can’t even see my libraries browsing the local server’s web UI. What a joke…
See this post for Windows server: Unable to access server after password reset - #116 by OttoKerner
Yes, this is a real Cluster-F.
So I looked at the re-claiming doc. The http://<IP_OF_QNAP>:32400/identity Identity url for me shows the following (I have replaced the machine identifier)
So it says claimed = 0.
I copied the claimpms.sh file on to my qnap and ran it and it has this:
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
******** ERROR ********
We failed to authenticate towards plex.tv
Please check username and password, as well as network access
But the password is definitely the one I just changed to as I verified in a private window, and is stored in my password manager.
Changing the password with the checkbox ticked which says “Sign out connected devices after password change”, will remove all access for all devices to your plex.tv account. That includes your server.
As a result, you will need to re-connect your server to your account (i.e. “claiming” it)
Yes, all plex authentication lives on plex.tv, and not on your local server.
MediaContainer size=“0” apiVersion=“1.1.0” claimed=“0” machineIdentifier=“blahblah” version=“1.42.1.10060-4e8b05daf”
didn’t like the xml paste
Thanks, that make sense. Ofc we tick that box when the user database has been breached… But how about actually allowing the claim? From what I can read up on, one should simply sign in on the local PMS server’s web UI and click “Claim”. Well, that would have helped if there were a claim button. I don’t even see my server. By browsing this forum for a couple of seconds you soon realaise half the word is in the same situation…
What is your server platform?
Okay update on mine, I realized one little thing, when I load my plex server in browser I go to https://ipaddress:32400/web/
However, to claim it is not “https” it is “http” which is why the page was not loading for me. When I go to the plain http page, I was able to claim it.
Now I will try logging in to a couple devices and see if they load
Docker on an Unraid server. plexinc/pms-docker:latest
I am at HTTP and even enabled insecure access from everywhere. No server as far as the man can see. 
Wierd because I’m browsing the actual PMS. How can’t it even find itself?
Btw my /identity URI says unclaimed. Don’t know what that means in terms of the next steps.
That is just as expected after changing the password.
You now need to claim the server, just like you did when you installed it.
I understand you could use this shell script GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex
Thanks! I will look into the script. Yeah, I understand I need to claim it, but shoudn’t I be able to do so from the PMS server’s web UI after signing in to my Plex account? I have no claim button, no server, no nothing. Can’t really remember how I made it in the first place all those years ago.
PLEX you caused this, you sort it out
Ok so after claiming it on local network, I tried logging in to my plex with a couple browsers (phone and computer), as well as 2 fire tv stick apps, and phone apps plexamp and plex and plexdash and they are all showing media. so that worked. wow, that was scary thinking I lost everything. It would be handy if the “https” worked rather than having to go to the “http”, I just couldn’t see why the site wasn’t loading at all.
I got it back! Many thanks for providing the script! As I’m running in Docker, I had to stop the container, run the script on the host system and use the `-p` switch to point to the Preferences file.
While I’m glad I got it sorted, it’s still a shame that we have to rely on third-party tools for such simple tasks… Wonder how many Plex servers are broken now…
https can only work if there is a security certificate. But there aren’t any for private IP adresses. They are pretty much only available when using domain names.
Hence why the server claming has to be done with http as protocol.
Without a “valid” certificate, https works, it just comes up with this message each time:
”
Your connection is not private
Attackers might be trying to steal your information from nas1 (for example, passwords, messages, or credit cards). Learn more about this warning
net::ERR_CERT_COMMON_NAME_INVALID
“
But in an unclaimed state, the https page wouldn’t load at all and that’s what was getting me.
