QNAP - Can't Launch Setup, Not Authorized

Plex Media Server NAS & Devices
1

Server version: 1.24.2.4973

OS: QNAP, TS-231P, OS Version 4.5.4.1741

Clients, w/ versions, if applicable: tvOS

What you did?

Installed Plex Media Server.

What happened?

Launching the PMS app on the QNAP web-GUI attempts to open the first-time-setup page (http://10.30.0.10:32400/web/index.html#!/setup/e9038bfcd0751ab900ff247c4940c314cf041499). Opening this page results in a “NOT AUTHORIZED, You do not have access to this server”. I cannot complete any basic setup and therefore cannot add any media sources. Going to the main Plex web-GUI asks me to install PMS, which is hilarious because it’s the PMS itself that’s showing me this page.

[Album] imgur.com

What you expected?

To be able to run the basic setup and use Plex.

Detailed information.

Plex Media Server 1.16 was previously installed on this NAS. A reinstall was necessary due to upgrading the QNAP OS multiple times, which for whatever reason rendered my Plex server unable to read my media sources. I upgraded to PMS v1.24.2 and wanted to start fresh.

Upon opening my Plex app using the QNAP icon, it asked me to log in. I used my normal Plex account with a premium sub, which logged in fine, however it took me to the home page where my media sources normally would be. I cannot add any sources because it thinks I do not have PMS installed.

[Album] imgur.com

Upon clicking the QNAP Plex icon again, I noticed it was taking me to the first-time setup page in which you’d configure the sever so you can add media sources. This is where the “NOT AUTHORIZED” page comes into effect. I can not complete basic setup, so I cannot use PMS.

I’ve attempted many ways to remedy this:

  • Re-install PMS using the QNAP App Store. Doesn’t work.
  • Manually remove PMS from “/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer”. Doesn’t work.
  • Uninstall PMS using the “.uninstall.sh” script from within “/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer”. Doesn’t work.
  • Attempt all methods above, but log out of the app before uninstalling, then restart the NAS before installing again. Doesn’t work.
  • Remove all clients from “Authorized Devices” page, then log out/in. Doesn’t work.
  • Remove all QNAP and Plex related browser cookies, then attempt manual uninstall/re-install. Doesn’t work.

In all attempts above, the same behaviour occurs. Upon re-installing PMS, it doesn’t not ask me to log back in, so user credentials are being cached/stored somewhere on the QNAP outside the .qpkg/PlexMediaServer app install directory. I believe this is the crux of the problem and old files are being stored somewhere within my QNAP that don’t get removed when uninstalling the app. If anyone knows where these files are located that would be fantastic, because I’ve not found any answers on the Plex forums or anywhere else yet. If anyone knows another solution that would be welcome too.

2

Bump.

3

@NovaS1X

  1. Stop Plex

  2. Create a Shared Folder named PlexData

  3. Restart Plex

  4. Stop Plex

  5. Open FileStation

  6. Navigate PlexData/Plex Media Server

  7. Delete Preferences.xml

  8. Exit File Station

  9. Start Plex - wait a minute for it to start up

  10. Open an INCOGNITO window to http://10.30.0.10:32400/web

  11. Now start setup

If it still fails,

  1. Stop Plex
  2. PlexData → Plex Media Server → right-click Logs → Compress to Logs.zip
  3. Download and attach here.
4

Hello to everyone

I’m in the same situation with a TS-.251A (2G)
OS Version 4.5.4.1741

with PlexMediaServer-1.24.2.4973-2b1b51db9-x86_64.qpkg installed.

this is my logs @ChuckPa
logs.tar.gz (69.3 KB)

let me know… thanks

5

@ak1ra

Your logs show you’re trying to access the server from a remote (WAN) IP

PMS won’t allow this (default security to protect your media if/when the server is remote and not under your control)

I also see a CURL ERROR 60 (certificate conflict)

Sep 11, 2021 10:36:57.823 [0x7fd72dcf1b38] DEBUG - Completed: [127.0.0.1:59226] 200 GET / (2 live) GZIP 2ms 2147 bytes
Sep 11, 2021 10:36:57.880 [0x7fd72d324b38] ERROR - Error issuing curl_easy_perform(handle): 60
Sep 11, 2021 10:36:57.928 [0x7fd72d347b38] ERROR - Error issuing curl_easy_perform(handle): 60
Sep 11, 2021 10:36:57.931 [0x7fd72d3ffb38] ERROR - Error issuing curl_easy_perform(handle): 60
Sep 11, 2021 10:36:59.407 [0x7fd72d743b38] DEBUG - NetworkServiceBrowser: SERVER arrived: 127.0.0.1 (QNAP-TS251A)

Please describe your actual configuration because if this is your home LAN then changes / special accommodates will need be made to make it work.

6

You are right because I just have another plex server on my lan (on a UnRaid station).
After read your post I finished the configuration of this QNAP on my father’s lan.
It worked like a charm! Thanks for your support.

7

Thanks for the reply, Chuck. Unfortunately this didn’t work for me.

I’ve attached my logs. Logs.zip (163.8 KB)

8

@NovaS1X

Thanks for the logs. I can see what’s happening.

The QNAP is at 10.30.0.10

The connection request - to claim - is coming from another subnet (10.10.0.52) and being declared WAN.

PMS cannot be claimed from a WAN connection.

Sep 13, 2021 18:17:07.008 [0x720d1d48] DEBUG - Request: [10.10.0.52:49653 (WAN)] GET /web/static/b38a559594ac52d049ba.png (5 live) GZIP

Either switch to the same subnet then open the QNAP again

-or-

execute a SSH-level claim. (can give instructions)

Which would you prefer ?

9

Hey Chuck,

Thanks for the quick reply. That makes a lot of sense!

I’d prefer the ssh claim method please!

10

here we go:

  1. Stop PMS

  2. SSH into the QNAP

  3. cd /share/*/.qpkg/Ple*/Li*/Ple*

  4. rm Preferences.xml

  5. Start PMS

  6. Stay in the shell

  7. In separate browser tab, Claim | Plex

    (This claim token is only valid for 5 minutes so do not waste time but do be correct in what you do)

  8. It will present you with a claim token COPY it to your browser

  9. Back in the SSH,

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

  1. It will look like

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

  1. Hit enter

  2. Wait for the reply (15-20 seconds depending on NAS and internet)

(PMS and Plex.tv are negotiating new credentials during this time)

  1. When successful, it will print a whole bunch of “Feature Flags”

  2. The NAS is now claimed to your accounut.

1 Like
12

That worked perfectly! Thanks a million!

13

Hi Chuck, I’m having the same issues. I had to rebuild my NAS and after reinstalling PMS I cannot PMS Logs.zip (37.1 KB)
get it configured. Attached are my logs

14

Your eithernet adapter is not RFC-1918 compliant.

It’s showing as a 172.172.x.x address which is owned by a firm in New York, NY

Is this a typo in the DHCP server of your modem/router ?

RFC-1918 addresses are 172.16.x.x → 172.31.x.x

If you meant to have 172.17.x.x, you’d be fine for use on the local LAN.

15

Yeah, that was the issue. I had changed my DHCP server IP to 172.16.xxx.xxx range and it’s fine now, thanks for the help.

16

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