Previously Authorized Server No Longer Authorized After Plex Update

Plex Media Server
1

Server Version#: 1.40.5.8854-f36c552fd
Player Version#: 4.138.0

I updaed my server verson of Plex Media Player on my Asustor AS5304T NAS. Now, I get the following message every time I try to open Plex Media Server from my NAS:

image
image816×466 29.6 KB

It also no longer shows up in my Plex account on my authorized devices list, but I can’t seem to get it back on that list because the only guidance I am finding to do so requires me to go through the Plex Media Server on my NAS, so… round and round I go.

Advice?

2

Try this: GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex

4

Holy crap. No idea how to use that.

5

here is the more generic version then: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

6

Yeah, that’s the “Support Article” that it references in the screenshot above. I did everything in that article with no success.

7

@ChuckPa can you lend a hand? odds are its something simple

8

Google/Github are evil.

I couldn’t download my own script.

Let me know if there are any difficulties

I WAS going to steal the QA machine for a minute. They’re running tests.
I can’t borrow it.

  1. ChuckPa (Chuck) · GitHub
  2. You’ll find the UserCredentialReset script
  3. Download and then upload into the NAS
  4. You’ll likely need to add ‘curl’ just as I do here.

Here’s my session

root@ASUSTOR-AS6704T:/volume1/.@root # df
Filesystem            1K-blocks       Used  Available Use% Mounted on
rootfs                  1883880      64572    1819308   4% /
tmpfs                   1893736          4    1893732   1% /tmp
/dev/md0                2029392     370212    1538044  20% /volume0
/dev/loop0                  951         16        915   2% /share
/dev/md1              476072968  216967956  255942920  46% /volume1
//10.0.10.143/media 11527082656 4667545824 6859536832  41% /share/quank
cgroup                  1893736          0    1893736   0% /sys/fs/cgroup
root@ASUSTOR-AS6704T:/volume1/.@root # cd /volume1/Plex/Library/Plex\ Media\ Server/
root@ASUSTOR-AS6704T:/volume1/Plex/Library/Plex Media Server # ls
Cache                   Crash Reports           Drivers                 Media                   Plug-in Support         Preferences.xml         Scanners                Setup Plex.html         UserCredentialReset.sh
Codecs                  Diagnostics             Logs                    Metadata                Plug-ins                Preferences.xml-save    Scripts                 Updates                 plexmediaserver.pid
root@ASUSTOR-AS6704T:/volume1/Plex/Library/Plex Media Server # PATH=/volume0/usr/builtin/bin:$PATH
root@ASUSTOR-AS6704T:/volume1/Plex/Library/Plex Media Server # which curl
/volume0/usr/builtin/bin/curl
root@ASUSTOR-AS6704T:/volume1/Plex/Library/Plex Media Server # ./UserCredentialReset.sh 
 
          Plex Media Server user credential reset and reclaim tool (ASUSTOR)
 
This utility will reset the server's credentials.
It will next reclaim the server for you using a Plex Claim token you provide from https://plex.tv/claim
 
ERROR:  PMS is running.  Please stop PMS and try again
root@ASUSTOR-AS6704T:/volume1/Plex/Library/Plex Media Server #

At this point, it will wait for you to go get a token from https://plex.tv/claim
and paste it here.

It will get credentials and fix your Preferences.xml file

Lastly, you start PMS again

9

I really appreciate this response. For some reason, it won’t stop PMS on mine (see my session below):

root@AS5304T-4F17:/volume1/home/Alexandria4F17 # cd /volume1/Plex/Library/Plex\
Media\ Server/
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # ls
Cache                   Logs                    Updates
Codecs                  Plug-in Support         UserCredentialReset.sh
Crash Reports           Plug-ins                plexmediaserver.pid
Diagnostics             Preferences.xml
Drivers                 Setup Plex.html
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # PATH=/volume0/usr/bu
iltin/bin:$PATH
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # which/curl
sh: which/curl: not found
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # which curl
/volume0/usr/builtin/bin/curl
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # ./UserCredentialReset.sh

          Plex Media Server user credential reset and reclaim tool (ASUSTOR)

This utility will reset the server's credentials.
It will next reclaim the server for you using a Plex Claim token you provide from https://plex.tv/claim

ERROR:  PMS is running.  Please stop PMS and try again
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server # ./UserCredentialReset.sh

          Plex Media Server user credential reset and reclaim tool (ASUSTOR)

This utility will reset the server's credentials.
It will next reclaim the server for you using a Plex Claim token you provide from https://plex.tv/claim

ERROR:  PMS is running.  Please stop PMS and try again
root@AS5304T-4F17:/volume1/Plex/Library/Plex Media Server #

I’m uncertain how I would manually stop PMS on an Asustor.

10

On ASUSTOR, don’t you have a button to stop the Plex package ?

(That little script doesn’t have a lot of stop/start knowledge. That would be anothr 300+ lines of code)

11

Yeah, I’m just dense today. Thank you so much. This worked perfectly!