PMS on QNAP doesn't show local server capabilities

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

After my QNAP crashed and had to be reset, I reinstalled PMS. It seems be running fine, except that it doesn’t have any local media content, and the server settings are unavailable. When I click on “Your Media” it tells me to Get Plex Media Server. But that’s the software I just installed. So, not sure what to do next.

I’m accessing PMS directly from the QNAP app screen, which redirects me to the PMS home screen (http://192.168.86.32:32400/web/index.html#). When I click on “your media” the URL redirects to http://192.168.86.32:32400/web/index.html#!/get-plex-media-server.

Sounds like you’ve either used a different user then the one that had claimed the server in the first place or you’re trying to open the Plex Media Server for the first start through the hosted version of Plex Web (http://app.plex.tv/desktop) -> to claim your server after a re-install, you need to access it through its local IP instead (e.g. http://[QNAP IP address]:32400/web).

If you had been using a different user… check this support article

I am accessing Plex through its local IP (http://192.168.86.32:32400/web). That takes me to the home screen. I don’t see the option of claiming my server.

Settings > Server > General

That’s the thing … There is no ‘Server’ under Settings.

which brings us to the support article linked above:
Why am I locked out of Server Settings and how do I get in?

My goodness … I’m going to start documenting what I did, just for the benefit of poor souls who may encounter the same problem.

1/ The webpage you listed doesn’t have instructions for NAS-based installations. However I did find Where is the Plex Media Server data directory located? | Plex Support

2/ Based on the instructions there, and given that this is LINUX system, I’m trying to locate the preferences.xml file. So:
[/] # getcfg -f /etc/config/qpkg.conf PlexMediaServer Install_path
/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer
[/] # cd /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer] # ls
CrashUploader* Plex Commercial Skipper* Plex Media Scanner* Plex Relay* Plex Transcoder*
lib/ Plex DLNA Server* Plex Media Server* Plex Script Host* Plex Tuner Service*
Library/ Plex Media Fingerprinter* Plex Media Server Tests* plex.sh* Resources/
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer] # cd Library
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library] # ls
Plex Media Server/ tmp/
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library] # cd Plex\ Media\ Server/
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server] # ls
Cache/ Crash Reports/ Logs/ Metadata/ Plug-ins/ Preferences.xml Thumbnails/
Codecs/ Diagnostics/ Media/ plexmediaserver.pid Plug-in Support/ Scanners/

3/ I used my best ‘vi’ skills to edit the Preferences.xml file and delete the following attribute/key pairs:

  • PlexOnlineMail="jane@example.com"
  • PlexOnlineToken="RanDoMHexIDecIALtoKeNheRE"
  • PlexOnlineUsername="ExampleUser"
    I could not find the following attribute/key pair: PlexOnlineHome=“1”

4/ I restarted PMS … same result as before. Server doesn’t show up :frowning:

Well, since above post looks like you can handle an SSH towards your QNAP :smiley: look here:

Also, and adding to self here:

Try browsing towards: http://<IP_OF_QNAP>:32400/identity

Does it show:

claimed="1" ?

Ok, fixed it (I think). The issue was that the PMS process was still running on QNAP, even after killing the browser window. Which makes sense.

So, I did this:
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server] # ps aux | grep -i plex
3041 admin 924 S grep -i plex
23379 admin 74544 S ./Plex Media Server
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server] # kill 23379
cd /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer] # ./Plex\ Media\ Server &

And then started PMS from the app home screen on QNAP… bingo …

PMS is currently syncing all the media folders.

So in all this, you never ever reverted to the old windows trick, and restarted your QNAP after a total crash and PMS reinstall?

1 Like

I did try the reboot before modifying the preferences file, but that didn’t help.
I just rebooted it now … and that messed things up again. Argggh!!! The system lists the server that I just configured as ‘not found’, and then added a new server that is ‘unclaimed’. When pressing the claim button, the system is spinning for a while and then just stops and the server disappears… Only the old server remains with status ‘unreachable’.

If so, then check my former posts, and also note, that if yoy did have a complete crash, then everything OS wise might have corrupted files!

I tried running the ClaimIT script but it fails with error
“We failed to authenticate towards plex.tv. Please check username and password, as well as network access”

It’s strange because when I log in on plex.tv and click ‘launch’, it correctly launches PMS on my NAS but shows the server as ‘not available’.

Are you using extended characters in either username or password?

Yes, a lot.

Then please use this version, not yet released:
https://github.com/ukdtom/ClaimIt/archive/passencode-fix.zip

same error

Ok, so I changed my password. The error went away but I now got a different error:
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
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 401

So, 401 error seems to indicate “Locked out of server setting” so, here we are again:

  1. I edited the preferences file and removed the 3 attribute/key pairs.
  2. I restarted my QNAP server
  3. Then I ran the ClaimIt script. It finished without error this time ("Claiming Server ok 200).
  4. I browsed towards http://<IP_OF_QNAP>:32400/identity and verified it indeed says “claimed=1”
  5. Finally I started PMS at http://<IP_OF_QNAP>:32400/web BUT THERE IS NO SERVER !!!

Arrgghh! I’m out of ideas at this point .