Plex server is gone!

Plex Media Server
1

Server Version#: No idea
Player Version#: Neither (browser)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I have two servers. One on my PC I only use for management. One on a Pi4 I use as the server.

I had to reset the pw of the Pi server, because you got hacked!

I couldn’t reclaim my server it wasn’t there.

I deleted the server from “Authorized Units”.
I followed all guides by Plex I could find. The latest was this: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

I stopped my server, then

Linux

  1. Quit/exit your Plex Media Server, so it’s not actively running

  2. In your text editor, remove the following attribute/key pairs from the Preferences.xml file:

    • PlexOnlineHome="1"

    • PlexOnlineMail="jane@example.com"

    • PlexOnlineToken="RanD0MHex1DecIm4LtoKeNheR3"

    • PlexOnlineUsername="ExampleUser"

I did! I restarted the server! I logged in via the local IP http://192.168.1.115:32400/web
The server is there, but I don’t get to choose what server I want to use, becaus e theserver is GONE! But I’m clerarly running on it, since I get a “page not found” when the server is stopped.

1 Like
2

I wonder what will be the bullshit where they’ll blame users to follow the app owner recommendation causin access loss PMS

3

To me, it’s infuriating that I have to spend 8-12 hours, every time I have to reset my pw, because they messed up! It’s never the same solution, their online guides do squat, nothing ever works!!

4

Try this. Worked for me

5

I wasn’t sure this would work, as the Github said
”Linux (wkstn/svr) | N/A | N/A”

But I put the script at /var/lib/plexmediaserver/ and ran the script, according to the guide, from /var/lib/plexmediaserver/UserCredentialReset-1.0.9/
I’m not even sure if it mattered, where I put the script.

And I got my server back, after 8 hours of troubleshooting, so thx a lot to mm98

2 Likes
6

As long as you put and run the script, as root, on the host, in the right environment (e.g. Native or in the container), it will do its best to figure out what it’s looking at and self-configure to find the path to Preferences.xml

If all else fails

./UserCredentialReset.sh -p "/path/to/Preferences.xml"

and it will go into manual mode. This allows running it from outside a container or with containers shut down