Good, that works, thank you, i got something appears.
But there is another problem, i already tryied to find it on my plex page : i dont have my unclaimed server on Plex > General (see the picture below)
You’re checking the Plex Web > General settings – not those of the server.
Are you accessing those settings via your server’s local IP from the same subnet? → http://192.168.1.15:32400/web
1 Like
Thank you very much guys, you helped me a lot.
I explain :
your message made me think about the protocole “http” as ‘JaysPlex7’ told me to, and you told me that i was not on my server itself, to see the good menu.
Now it works.
For the guys who have the same problem as mine, here is the solution :
- Make sure that your router has the exception line for the port you are using for Plex. For example : 32400 → TCP/UDP
- Use your local address (connecting your server/nas), for example : 192.168.1.10:32400
- Use the HTTP protocole and not HTTPS (or you will have an error), for example : http://192.168.1.10:32400/web
After that, maybe you will have to configure your server again (set folders, etc) and sometimes the page will infinite load, just open the page in another tab and then continue to configure your server.
Special thanks to tom80H and JaysPlex7.
Thank you to the Plex community 
That’s got nothing to do with reclaiming your server. As you’re speaking about remote access and port forwarding… there’s no need for the public port to be 32400 (public port can be pretty much anything; private port must be 32400); Plex remote access only uses TCP; no UDP required.
That’s correct.
No server re-configuration will be needed.
I’v seen a few remarks that specific clients might ask you to re-do the customization, which libraries to be pinned to the sidebar – that’s the extent to that.
1 Like
@FordGuy61
FordGuy61Plex Ninja
That will not work when trying to claim a Synology based server.
Use a incognito/private browser window. Go to http://<syno_ip_address>:32400/web.
You have to use the IP address when claiming. Using a hostname, Synology quickconnect, etc will not work.
That was the piece I was missing, thanks! Didn’t see that tidbit of information anywhere.
1 Like
It actually also works if you use the mdns .local hostname; my Synology is named blob and I was able to adopt it at http://blob.local:32400/web.
Yeah I am trying to figure out if auth tokens were compromised as well and not really seeing any clear communication on that. I was 2FA since inception so not overly concerned on the PW front but if the tokens were stolen then this is a whole other story.
The thing is they have no idea what the hell happened or what exactly was taken as per the norm for companies that fail to implement proper checks and balances into their backend.
If I’m wrong then release exactly what happened. What was EXACTLY taken and HOW THEY DID IT. Not some statement that says well they potentially had acces to this and that but in reality we have no clue.
The statement “out of an abundance of caution” is an antonym for DISCERNING.
1 Like
The recommendation is that you should consider them being compromised.
Your Plex account does have a password on it.
This password needs to be changed. Urgently.
If you still know this password, change it here https://app.plex.tv/desktop/#!/settings/account and tick the checkbox to sign out all devices. This does take care of all access tokens.
If you don’t know the password anymore, you need to use the “Forgot Password” link on the Sign-In page, as instructed in the Email.
Waiting for the password reset email can still take several hours, unfortunately.
I did reset my acct PW on 08/24 and have had 2FA enabled since Plex first implemented it.
The question relates specifically to the auth tokens and whether or not they were stolen as part of this hack. The acct PW seems irrelevant (2FA or not) if the auth tokens were stolen as they could be used to authenticate sans PW/2FA could they not?
I have seen reports of users stating there account was compromised/accessed post 08/22 but I have no way to validate those claims and have not personally experienced this. If accurate that would lead me to believe either the PW was hashed with MD5 or the tokens were indeed compromised.
Plex has made statements that the tokens may have been compromised however no indication as to why and it is not specifically called out in the list of items in the database that was accessed. I get that this is only a week old and the investigation is on-going and am by no means being critical here, just looking for discussion and a better understanding of what has happened. Look forward to reading the postmortem in the months to come.
I have already revoked all authorized devices from my side, however when it comes to shared libraries I have no way to revoke the token of other users. Or is there something else I am missing here?
I took a bullet for the community and decided not to take any action to this situation and just wait. I didn’t change my password and I had no 2FA activated. Last week I started to have new clients connecting to my server, they had IP addresses from USA and Vietnam (I am located in Germany).
So I would think that the breach was more than what we were informed and it was not only the salted hashes.
I have now changed my password, activated 2FA and kicked out the unwanted clients.
1 Like
As mentioned above, access tokens should be considered as compromised.
That’s all an attacker needs to connect to your server and access its contents (and also change certain preferences).
So change the password and tick the checkbox to sign out all devices, as originally instructed.
nothing. I have notice nothing, not even a sniff.
And since Plex still refuse to say exactly what was compromised i aint changing diddly
Well, since this all happened I can no longer access my music files. Completely gone and replaced with Tidal. Not happy at all. Garbage.
You probably missed the notice that you’ll have to re-claim your server afterwards.
Go here for an easier option: You need to reclaim your server, but don't dare to touch the Windows Registry
Didn’t have to reclaim mine…
Then you either
- didn’t use the check box to sign out all devices (not recommended, it means you are still vulnerable to rogue access)
- have your server configured to not require authentication in your local network. But in this case you will still see some malfunctions.
I didn’t sign out all devices. Didn’t seem like something I was really concerned about. Wouldn’t signing out all devices require all my users to have to sign in again? I didn’t want them to have to do that. They are neophyte computer users and I didn’t want to confuse or worry them.
Did I do something bad? If so then how to correct it? I have problems getting my users to even use the thing. Having to have them reset passwords is probably too much of a bother for them.
Only if they use your account. (i.e. if they are either managed users or you have shared your account credentials with them [bad idea])
I’m the only one who uses my account. I have no managed users either.
So then:
- Do I need to sign out all devices?
- How do I do that?
- Would doing so require me to re-claim my server? I ask because others have reported problems with doing so.
- What happens if I don’t sign out all devices?
https://app.plex.tv/desktop/#!/settings/devices/all has all kinds of devices and always has. IOW I could never tell what these things are for. For example, I have 6 entries for “Earth” my desktop yet I have only one desktop.
I have two listed as Earth Plexamp, one 2 days ago and the other says 5 months ago. The first one says 4.3.0 while the 5-month one says 4.2.0. Don’t these get cleaned off when a new version appears?
I similarly have duplicate entries for Plex for Linux (is that Plex web?), Plex HTPC for Linux (I played with that)
I also have multiple entries for my Android phone, WebTools, several Chrome ones, and Firefox ones as well as some for my Vizio TV, PS4, etc. and Tautulli, Sonarr, etc. As I said, this is a mess!
