Cannot access QNAP Plex Since resetting password

I received the email and followed all the instructions as direction and boy am I sorry I did so. I’ve got very strong passwords so I probably should have let it be, but here we are.

I cannot even see my server name listed on my plex homepage, much less being told I need to claim it again.

Can someone from Plex please help me figure out what is going on . Following your instructions got me here. I would appreciate your help getting my server back. Thanks.

1 Like

I am having the EXACT same issue… PLEX please fix the issue or at least give us SIMPLE instructions on how to fix this. NOT happy at all

2 Likes

I am in the same boat on both of my servers, it’s more than annoying, as up until now they’ve been great. For what it’s worth I am running my Plex on two different Qnaps, and up until I did the password reset all was well; also all of my friends/family are in the same situation and cannot access anything.

I am running 2 servers one being a remote running off a Qnap NAS the other being local running off a PC.
As per the instructions i changed my password and lost the server running off the NAS. I even changed back to the original password and that did not help.

We need a fix ASAP

On QNAP, we need to do a manual reset in two steps.

  1. Setup access via FileStation
  1. Restart Plex one time (to populate the PlexData share) then stop Plex

  2. Navigate (Using FileStation) PlexData/Plex Media Server

  3. Install the Text Editor app from the App Center (if not already installed)

  4. In FileStation, right click Preferences.xml → Open with Text Editor

  5. Carefully, remove 4 preferences from the file
    Each preference consists of the Name="Some_Value_here"

  • PlexOnlineUsername
  • PlexOnlineToken
  • PlexOnlineMail
  • PlesOnlineHome (if it exists)
  1. Save the file

  2. Start Plex

  3. If you and the QNAP are on the same RFC-1918 LAN subnet (192..168.x.x, 10.x.x.x, or 172.16.x.x - 172.31.x.x)

  1. If you’re on a different subnet, you have two choices:
  • SSH tunnel to it:
ssh -L 8888:127.0.0.1:32400  ip.addr.of qnap
  • Leave the session open & idle
  • In your browser open http://127.0.0.1:8888/web
  • You should be greeted with the Plex/web and claiming process.

==================================================

  1. (Alternate method ) Plex claim token
    – After having cleared out the Preferences.xml file (above)
    – With PMS started
    – In a new browser tab, open https://plex.tv/claim
    – It will present you with a claim-xxx token
    – COPY it to the browser

  2. In the SSH shell still open

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

Hit enter.

As long as there are no errors, it will sit there 15-20-ish seconds while it negotiates new credentials in your PMS.

It will respond with a bunch of XML flags ending with </MyPlex> when successful.

You’re done and ready to go.

Open via the LAN IP one time to confirm it’s all working as expected

Hi @ChuckPa,

I have my Plex Server running as a QPKG on QNAP, and I am local. The above directions do not work for me. I can log into my local Plex server [local IP]:32400/web, but I do not see the option to claim my server under settings.

When I load [local IP]:32400/identity I get the following:

MediaContainer size=“0” claimed=“0” machineIdentifier=“(REMOVED)” version=“1.28.1.6041-738907df3”

The server is clearly in an unclaimed state, but I absolutely cannot claim it. I have tried all the directions from Plex, including your post above with no success.

I have tried the Claim It tool, and get the following:

I have tried adding claimpms.sh to PlexData and running it. I get the following:

IP Address of PMS server: 127.0.0.1
Comparing entered passwords
Comparing entered passwords ok
Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
******** ERROR ********
We failed to authenticate towards plex.tv
Please check username and password, as well as network access

I have cleared out the specified entries in preferences.xml. I have stopped and restarted the server. I have rebooted the NAS.

I am completely out of ideas and need help.

I don’t know much about Dane22’s claim tool.

I am more of a “BIG HAMMER” guy as I show above.

Thanks so much for the response. I’ll use a big hammer if necessary. The issue I’m having is that nothing works at all. I’ve followed all directions from your post above. I don’t get the claim server functionality, no matter what I do.

I really have no idea what to do next.

I’m starting to wonder if my reset credentials are messed up somehow. I can login fine to plex.tv, and to my local plex web, but I just discovered that the Android app rejects those same credentials.

Trying to use the above description leaves me even more frustrated, since I don’t even see the folder PlexData using the FileStation app?
Oddly enough, I can see the folder from the dropdown list in Advanced search, but still not showing elsewhere in FileStation? (I see the folder from the ControlPanel/Shared folders, but have no rights to change any Properties or Permissions?)

I see it from my Windows computer, but cannot login.
I used both the Plex login and QNAP Admin credentials, but no luck.

What is left now?
Can I remove the server installation completely, and start over?

Pretty much the same problem here as well. Tried every solution offered here on the forums, to no avail. Every time I try to connect to Plex on my local QNAP NAS, I get this:
Plex error
Is this still due to the Plex servers being overloaded and if so, when can we expect that to be resolved?
Thx

no luck here even finding the mentioned plexdata folder.

Looks like the hard way is to stop plex, uninstall plex, reinstall plex and loose all watched history…

Taking that route here… don’t really want to, but it has to be up and running soon.
I think I’ll live with loosing watched history

Stop Plex server
Delete the QPKG
Remove the PlexData folder (on my NAS, it is listed as being present on NO volume?)
Reboot NAS
Install Plex server and reconfigure
… Live long and prosper

Hi @ChuckPa , first: Thanks for trying to help us! I tried your method but failed at step 6: My Preferences.xml is not updating/being populated with up to date info and only contains the following:

  • OldestPreviousVersion
  • MachineIdentifier
  • ProcessedMachineIdentifier
  • AnonymousMachineIdentifier
  • MetricsEpoch
  • GlobalMusicVideoPathMigrated

And thats it, so no onlineUsername, Token etc to be removed… Am I doing sth wrong? I stopped and restarted PMS multiple times now, still no changes to the Preferences.xml. Pls help :see_no_evil:

Please see: (Re-)Claiming a QNAP Plex Media Server

Hi @dane22,

Thank you very much for the detailed list of things to attempt. Unfortunately, as you’ll see from my post above i have tried all of them and nothing works.

Thinking maybe i need to do another password reset?

For a start, and since claimit showed an TLS error, please retry with that, and after doing so, upload the PMS logs

Just tried again and got the same error. Then took a look at the logs, and I see this:

Aug 25, 2022 07:13:52.827 [0x7fc84bc29b00] DEBUG - Request: [127.0.0.1:55562 (Loopback)] GET / (4 live) #4401a Token ()
Aug 25, 2022 07:13:52.829 [0x7fc84e162b00] DEBUG - Completed: [127.0.0.1:55562] 200 GET / (4 live) 1ms 4299 bytes (pipelined: 1)
Aug 25, 2022 07:14:20.183 [0x7fc84bc29b00] DEBUG - Request: [10.0.1.53:7424 (Subnet)] GET /identity (4 live) #4401f
Aug 25, 2022 07:14:20.183 [0x7fc84e13fb00] DEBUG - Completed: [10.0.1.53:7424] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Aug 25, 2022 07:14:51.099 [0x7fc84bc29b00] DEBUG - Request: [127.0.0.1:55774 (Loopback)] GET / (3 live) #44020 Token ()
Aug 25, 2022 07:14:51.100 [0x7fc84e162b00] DEBUG - Completed: [127.0.0.1:55774] 200 GET / (3 live) 1ms 4299 bytes (pipelined: 1)

Please zip and upload complete log, and not a copy/paste of a snip

Here you go:

1 Like

Huh, log doesn’t show you ran claimit?

Here’s what happened when I did it:

Aug 25, 2022 13:22:23.200 [0x7f598b318b00] DEBUG - Request: [127.0.0.1:56610 (Loopback)] GET /identity (5 live) #30d
Aug 25, 2022 13:22:23.200 [0x7f598e62eb00] DEBUG - Completed: [127.0.0.1:56610] 200 GET /identity (5 live) 0ms 398 bytes (pipelined: 1)
Aug 25, 2022 13:22:23.945 [0x7f598b318b00] DEBUG - Request: [127.0.0.1:56616 (Loopback)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxR8GCvA (5 live) #32b Token ()
Aug 25, 2022 13:22:23.945 [0x7f598b318b00] DEBUG - [Req#32b/HCl#37] HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxR8GCvA
Aug 25, 2022 13:22:24.159 [0x7f598af12b00] DEBUG - [HttpClient/HCl#37] HTTP/2.0 (0.2s) 200 response from POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxR8GCvA
Aug 25, 2022 13:22:24.159 [0x7f598b318b00] DEBUG - [Req#32b] MyPlex: Did token exchange for claim (returnCode: 200)
Aug 25, 2022 13:22:24.160 [0x7f598b318b00] DEBUG - [Req#32b] MyPlex: Stored token xxxxxxxxxxxxxxxxxxxx
Aug 25, 2022 13:22:24.219 [0x7f598b318b00] DEBUG - [Req#32b] MyPlex: Got a token poked, let's act on it.
Aug 25, 2022 13:22:24.220 [0x7f598b318b00] DEBUG - [Req#32b] MyPlex: username is dane22, login is XX@YY.dk, home is 1, has pin
Aug 25, 2022 13:22:24.222 [0x7f598b318b00] DEBUG - [Req#32b] Disabling DLNA server because the server is now in a home.