Not Authorized

I have a Qnap NAS as my Plex Server and it was working perfectly, but recently it was having some issues with playing content. To fix the issue I removed the Plex Server from my NAS and attempted to reinstall. The install went fine, but when I attempted to access my Plex through the local web interface and after entering my pin I get “Not authorized. You do not have access to this server”. I have never seen this before and I can’t resolve the issue. I have tried what I think is the kitchen sink, like setting the NAS to factory settings and reinstalling Plex Server to even reinitializing the NAS and reinstalling. Every time I get the same issue. To me it appears the I need to reclaim my NAS as my Plex Server.

When I delete all associated devices through plex.tv login and try login through the NAS local connection I enter my Plex login info and it allows me to select the user (See below) but when I enter my pin there is no option for me to claim the server. The NAS is on the same network/subnet and even the same static ip address as before.

I am looking for any assistance. I have no idea what to do next.

Thank You


I have attempted to SSH the NAS and follow the steps to reclaim the device by deleting the Preferences.xml file, but when I attempt to remove the file it comes back with the file is not in the directory. (QNAP - Can't Launch Setup, Not Authorized - #9 by NovaS1X) I can confirm that the Preferences.xml is located on the Shared>PlexData>Plex Media Server>Preferences.xml. What I have attempted to do is stop the PMS remove the Preferences.xml file from the above file path and then follow the steps of claiming the device via the claim token SSH, but this no success. Is there anything I am missing?

Server Version#:1.25.3.5385
Player Version#:

The preferences.xml is actually a couple levels deeper

.qpkg/PlexMediaServer/Library/Plex Media Server/preferences.xml

When I try to cd the deeper file path you stated I get the “No such file or directory”. Am I doing this correctly?

Would logs help? If so what logs would you need?

Thank You

the last folder has spaces in the name of that folder so you need to put \ at the end of each word that has a space after it ( so there is a space after the \

/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex\ Media\ Server

or put quotes around entire path

"/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server"

I appreciate clarifying the pathway.

I follow the updated file path and remove the Preferences.xml file, but when I continue with the step to claim the server. I don’t get any response from my NAS showing that the Claim Token has worked. I get see a print of a whole bunch of “Feature of Flags”. Is there something else I am missing here to claim my server to my plex account? See what I am talking about below.

Thanks

  1. You will need a new claim token because the one you use there has now expired.

  2. What you’re missing in that line is the closing ' (apostrophe)

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

I tried running the claim token command and now I am getting “Unauthorized” response. See below. Any other ideas? I am sorry this is being such a pain.

i don’t think 172.168.1.100 is a compliant RFC 1918 private address which could be issue. Looks like it is owned by Yahoo 172.168.1.100 IP Address Location | SG IP network tools

Also removed your terminal window images that had your token in them. don’t display that to the public

I appreciate you removing the token.

The 172.168.1.100 is my local lan address for my NAS. Should I be using my WAN IP Address when requesting a new token?

The IP Net 172.168.1 is not in private address space, and as such not recommended, since not only will PMS see that IP Net as one you can’t claim your QNAP from, but it might also collide with the actual owner of that IP Net, if you try to browse to that.

For the B-Class, it’s 172.16.0.0 – 172.31.255.255
Ref: Private network - Wikipedia

To claim your QNAP, try this:

You need to download it, put on your QNAP, and follow this:

Or read this, specially On a Different Network

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.