Server Version#: 1.26.0.5715
OS: QNAP TS-251B v 5.0.0.1986 (2022/03/24)
I had PMS on my QNAP NAS at my previous address. When I moved, I turned off the NAS and transported it to the new address. When I tried to setup the NAS using the network at the new address, I immediately had issues with Plex. I thought this could be fixed with a factory reset of the NAS, and deleting the old server from my device list through the Plex browser client (i.e. starting again). I’ve obviously just made things worse - after trying for days to get PMS working again on the NAS I’m stuck. When I try to launch PMS from the NAS it says “Can’t Launch Setup, Not Authorized”.
Very similar issue to the one detailed here: QNAP - Can't Launch Setup, Not Authorized, but the applicable solution doesn’t seem relevant, at least based on my non-expert review of the logs.
It does seem like somehow even after the factory reset and PMS uninstall there is something (e.g. cache, old PMS details) on the NAS somewhere preventing the login.
I would really appreciate any help with this. I have attached the logs with the most recent attempt again resulting in the error. Logs.zip (182.1 KB)
It looks like you’re trying to access it using a WAN IP. This won’t work.
You must be on the same subnet, or using a SSH tunnel, or use the Plex Claim Token method to complete initial setup
May 03, 2022 12:10:34.438 [0x7f11699e4b38] DEBUG - Completed: [192.168.0.1:55587] 200 GET /web/js/chunk-830-8616060f1841c97c3337-plex-4.76.1.22469-3117cd9.js (6 live) GZIP 1ms 967 bytes (pipelined: 2)
May 03, 2022 12:10:34.438 [0x7f11699e4b38] DEBUG - Completed: [192.168.0.1:55588] 200 GET /web/js/chunk-884-6a5571e350dd82b13ef2-plex-4.76.1.22469-3117cd9.js (6 live) GZIP 1ms 16697 bytes (pipelined: 1)
May 03, 2022 12:10:34.446 [0x7f1169a07b38] DEBUG - Request came in with unrecognized domain / IP '122.107.XXX.168' in header Host; treating as non-local
May 03, 2022 12:10:34.446 [0x7f1169390b38] DEBUG - Request: [192.168.0.1:55586 (Subnet)] GET /web/js/chunk-408-263035433e3dcbaa4aa1-plex-4.76.1.22469-3117cd9.js (6 live) GZIP
May 03, 2022 12:10:34.446 [0x7f1169390b38] DEBUG - Final path: "/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-8cf78dab3/WebClient.bundle/Contents/Resources/js/chunk-408-263035433e3dcbaa4aa1-plex-4.76.1.22469-3117cd9.js"
May 03, 2022 12:10:34.446 [0x7f1169390b38] DEBUG - Content-Length of /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-8cf78dab3/WebClient.bundle/Contents/Resources/js/chunk-408-263035433e3dcbaa4aa1-plex-4.76.1.22469-3117cd9.js is 79284 (of total: 79284).
That is strange. My NAS is plugged in via ethernet to the back of the router into one of the ports labelled “LAN”. I have also checked the IP address for the router and NAS are the same. The unrecognised domain in the log snippet you included looks like the public IP address for the router. So I don’t understand why they are being treated as different subnets with this setup.
Are you able to confirm the steps for the Plex Claim Token method to complete initial setup? I will give that a go.
Without those pairs in the Preferences.xml file, your server is “Unclaimed”
When we use the Claim Token method above, we want it unclaimed.
We also need it to sit idle (don’t access via the web page yet)
Given the server is already unclaimed, that’s fine.
Confirm the NAS has internet connectivity (DNS and Gateway are correct).
Then run the procedure in the SSH session starting with the " Now for the claim token"
And above output means that routing and DNS is okay, so next step is to ensure that your PMS is really not claimed, so in a browser, browse to: http://<IP_OF_QNAP>:32400/identity
Dbirch, I then did as you suggested, though I had tried this so many times and it allowed me to login but then asked me to install PMS. Bizarrely, I have just tried this again and it launched the PMS setup wizard. I can’t explain why it has started working - PMS is setup and media is syncing.
