Server reports "Not authorized: You do not have access to this server" after password reset

Folks,

For getting QNAP machines back into your account after the password reset.

  1. Create the PlexData shared folder if you haven’t
  1. Make certain you’ve installed the QNAP “Text Editor” app.

  2. Start and stop Plex ONCE,
    (we do this so the PlexData/Plex Media Server linkage is created)

  3. Now navigate: PlexData/Plex Media Server in FileStation

  4. Right-click Preferences.xmlOpen with Text Editor

  5. In the editor, remove the following Name="Value" pairs
    – PlexOnlineUsername
    – PlexOnlineToken
    – PlexOnlineMail
    – PlexOnlineHome (if it exists)

  6. Save the file

  7. Start the server

  8. Now you can claim it.

(I would love to have a gui-based process with the installer but QNAP doesn’t have a mechanism I can use)

@ChuckPa I tried the edit of Preferences.xml with my docker container version of Plex and it did not work. Still cant claim my server and I cant access my server even thought I am on my servers IP.

Docker is unique.

Remember the PLEX_CLAIM environment variable you used ?

You need to reclaim the Container.

The easiest method I know is:

  1. Delete the container definition (but not the data)
  2. Get a new Claim Token
  3. Edit the container definition and change PLEX_CLAIM= value
  4. You will want to remove the values from Preferences as stated above.
  5. Recreate the container.

Thanks for posting this, but I’ve just done all your instructions and I’m not seeing any button to claim my server. Why is this causing so many folk so many problems?

I’ve tried this and still can’t see or access my Plex media server anymore. Please help me to solve this.

I had the same issue and nothing suggest thus far fixed it. I did figure it out however based on other suggestion here.

While editing Preferences.xml I noticed that there was another entry for “allowedNetworks” that had an old IP address. Once I removed that entry I was able to claim my server.

@ChuckPa
I am 1400 miles from my server running synology dsm7. I can gain direct access to log out of the server and log back in yet still says unauthorized. Any ideas on bring this backup after this disastrous password change?

Exact same setup as yours (Windows + QNAP servers). Took me a while to figure out and made it work pretty much using your same method. Except at some point I managed to lose the configuration and will have to setup libraries again. Thank you fore the helpful tips

Hey, Why don’t you release a pkg update to fix this shitstorm?

I’ve contemplated ditching PLEX, and I do believe this is the tipping point.

Same here, Synology DS220+ running DSM7.1.
Changed password, suddenly can’t access the server.
I’ve even tried uninstalling/reinstalling Plex but although I can open Plex from the server, it can’t access the server! (yes, I have applied the necessary permissions to the media folders).
I just get ‘you do not have access to this server’ message.

  • EDIT** I think I may have managed to get this working again - a third uninstall/reinstall using the claim token has managed to reclaim the server!

@audiomixer

The “Plex Claim Token” method resets your credentials AND accepts the EULA for you remotely.

Have you performed that step?

If you have, and have access to the shell, we can insert one preference manually to force it to “Publish” to plex.tv so you can get control

Are you in need of that ?

No amount of package updates will fix a security breach.

I have everything set in DSM 7 to do the reclaiming using the Claim Token.
IT WORKS.

The limitations of that (Thanks to Synology)

  1. Can’t perform first connection after reclaim using QuickConnect
  2. Can’t perform first connection after relclaim with app.plex.tv

What am I supposed to do?

I think I’m ok. I was able to remotely claim the server by doing this……both servers are up and running correctly.

To all here.

While I don’t have any “fixes” for a data breach,

I was able to craft a freestanding, self-configuring utility for LInux-based machines.

This includes all flavors of Linux, Synology DSM 6 & 7, QNAP QTS and QuTS and Netgear ReadyNAS .

Not all of your customers are devs. I’m on a qnap and it’s not working. There will also be mac users that can’t use claimit.

Talk to me please?

What “didn’t work” ?

I don’t expect anyone to be a dev.
I do expect to be able to:

  1. Open a terminal or SSH session
  2. Upload a file to a NAS (if using a NAS)
  3. Type a couple commands on the terminal / SSH command line.
  4. COPY * PASTE from a browser.

What about my instructions didn’t work right on the QNAP?
(I have two QNAPs here. I’ll recreate what didn’t work for you if I can)

I have already removed the server from my nas and reinstalled it. Starting again, although it now keeps disconnecting.

My new server now keeps saying ‘unavailable’.

@ChuckPa seems like you’re doing gods work with helping ppl out here…

I’M on an asustor 1004T with ADM 4.0.5.RVI1 - I did manage to get an SSH connection from windows, got to the right path for the file (/uploaded through web admin). now I’m really clueless with Linux for the most part, but I can sometimes follow instructions and get there eventually. - but my strong feeling is the asustor implementation is not very standard and I can’t just use ‘normal’ linux tools. (i.e. sudo root doesn’t work, a few other things dont behave as expected)

I’d really appreciate any help.

yes, jalas is in the admin user group, wasn’T working with shell in a box and the admin account either… so I tried from a windows terminal(powershell)