Hacker News new | ask | show | jobs
by withinrafael 1401 days ago
This disclosure is no where to be found on their website or blog, and it provides no timeline, no details about the attack, and no details about what data was accessible beyond "a limited subset of data that includes emails, usernames, and encrypted passwords". Very very frustrating.

As of Aug 23 11:24PM PST, Password change page is sort of working, at times displaying error message "Internal Server Error. Something went wrong on our end". I was able to get my request through. Shortly after, a server instance started showing unclaimed status and reassociating it resulted in "Plex is down for maintenance \ Don't worry, it will be back soon \ status.plex.tv".

1 comments

It appears the password change works fine if you deselect the "Sign out connected devices" box. [1]

[1] https://twitter.com/troyhunt/status/1562329358282285057

Mine worked fine with that checkbox on. However, I cannot get my home server to appear again, even after getting a new claim and restarting it.
This is exactly what I had happen as well.

I'm going to give it some time. I also even went through these steps (https://support.plex.tv/articles/204281528-why-am-i-locked-o...) without success.

It didn't work for me after restarting with a new claim and when i checked the preferences it contained `PlexOnlineToken=""`.

After removing the attribute entirely it was able to successfully reclaim the server.

So a coworker suggested I try accessing my Plex instance by internal IP, not internal hostname. And that... worked. When using hostname, the way I always had for everything else, it'd show that I didn't have access to the server.
I had the same "", but after restarting all the web interface says is Connecting. Then the server just doesn't show up in the list. <sigh> Might just need to blow up my whole config and reimport everything.
I got it claimed again after several tries. I suspect they are getting hammered by a lot of people doing the same thing (changing passwords)