Changed admin password and now admin doesn't have access to the local media server

Plex Media Server NAS & Devices
1

Server Version#: Version 4.76.1
Player Version#: N/A

As the title explains, I changed the password of my admin account and now I don’t have permission to access the local plex server hosted on my NAS (via a docker container). All I see is the below image. Does anyone know how on earth I give the admin account access again?

image

I’ve already tried editing the preferences.xml file and removing the following:
image

I then duplicated the docker container, pulled the latest image, and tried logging in again. Still don’t have access to the local server.

I am also accessing the server via the local ip:32400 port.

1 Like
2

Same situation here after I changed the admin pass according with the email with security breach received.
The difference from vividus101 is that I run the server directly from a Synology NAS, not via container. Error is the same

in preference.xml the token appears as null
PlexOnlineToken=“”

4

Same here. Updated my password, tried to access my library and I get the very same error. Running plexmediaserver on Linux VM. Can’t access locally nor via any app or web interface anymore.

5

I am also having this same issue. I’ve reset my password. The process threw an strange token error but seems to have worked, as I can log in with the new password.

  • I have done the above steps removing the entries from Preference.xml.
  • Logged in, logged out.
  • Remove all devices from my account.

I even have taken the step of uninstalling plexmediaserver, sudo apt remove plexmediaserver, removing the entire /var/lib/plexmediaserver/Library/Application Support/Plex Media Server directory and re-installing plexmediaserver.

Nothing. The server will not show up in my account. :person_shrugging:

Edit: I am NOT running this on a Synology NAS device, however. I am running this in an LXC container on Proxmox. I don’t believe this is an issue with the device, but rather the Plex accounts themselves.

6

Plex servers on DSM 7 can use the “PlexClaimToken” method to regenerate credentials.

  1. Uninstall the package with “Keep”.
  2. Reinstall the package with the “Plex Claim Token” option
  3. On the option page, Click “Get Plex Claim Token”
  4. Browser opens with claim token
  5. COPY to browser
  6. Return to installer window,
  7. PASTE into box in the form.
  8. NEXT NEXT NEXT and install begins
  9. An extra 15-20 seconds will be required while the installer:
    – Uses the claim token to contact Plex.tv
    – Gets new credentials for your server’s Preferences.xml
    – Writes those new credentials in Preferences.xml
  10. When claim is complete,
    – Successful install reported
    AND
    – Shows your Plex username in the report popup (CONFIRM THIS)

You may now open the synology (First time only) by using the LAN IP.
Do not use App.plex.tv or QuickConnect.

8 Likes
7

Same problem, except I am on Qnap nas.

8

Could you please explain how to Uninstall the package with Keep and “Reinstall the package with the “Plex Claim Token” option”.

Kind regards

Reinier van Haeften

1 Like
9

There is a similar method for other hosts:

  1. SSH into the machine / get into the container , etc as required.
  2. Stop Plex
  3. Edit Preferences.xml
  4. Carefully remove the following Name="Value" pairs
    – PlexOnlineName
    – PlexOnlineToken
    – PlexOnlineEmail
    – PlexOnlineHome (if it exists)
  5. Save the file
  6. Start Plex

On your computer

  1. Open Claim | Plex
  2. COPY the token given into your browser
  3. On the command line (where the server is), type:
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE'
  1. Hit Enter.
  2. Wait 15-20 seconds for Curl / PMS to talk to Plex.tv and setup new credentials.

The curl statement will look like this:

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'
8 Likes
10

On DSM 7,

Package Center
– Remove
– Package menu pops up
– FIRST option is “KEEP”. Use this option (select the radio button)
– NEXT and continue to uninstall.

(the reverse of installing in Package Center)

The DSM 7 claim token procedure is above (what I just wrote)

Also here in the FAQ

@rvhaeften

If you’re having language difficulties, the DSM 7 package does work in Dutch native language. Change your Synology system language and the package will adjust all dialog appropriately.

11

Thanks a lot, it worked for me !

12

This fixed it for me, thank you so much!

13

Well, that was all kinds of ridiculous that this was necessary, but it worked! Thanks!

2 Likes
14

There is a similar method for other hosts:

  1. SSH into the machine / get into the container , etc as required.
  2. Stop Plex
  3. Edit Preferences.xml
  4. Carefully remove the following Name="Value" pairs
    – PlexOnlineName
    – PlexOnlineToken
    – PlexOnlineEmail
    – PlexOnlineHome (if it exists)
  5. Save the file
  6. Start Plex

On your computer

  1. Open Claim | Plex
  2. COPY the token given into your browser
  3. On the command line (where the server is), type:
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE'
  1. Hit Enter.
  2. Wait 15-20 seconds for Curl / PMS to talk to Plex.tv and setup new credentials.

The curl statement will look like this:

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'

this worked for me
thanks

1 Like
15

This did not work for me, instead I received error 401:

Unauthorized

401 Unauthorized

I followed (Linux) instructions - edit Preferences.xml, start plex. Curl, then error as per above, 401.

Can you please advise? Thank you,

16

Thank you, this saved me a mighty headache!
Saving it for future reference, very useful

17

This worked for me too, thank you!

18

This worked on my Synology DMS6. Thanks!

19

Thank you, @ChuckPa ! This did the trick for me.

m!

20

Randomly, this didn’t work for me on TrueNAS.

I can walk the URL tree with curl and get HTML responses but posting the claim results in a 500-internal server error.

Anyone else navigated this challenge?

21

What a clusterfuck

4 Likes