I have installed PLEX Media Player, shared folders on NAS and done all as per instructions (it is not the first PLEX I have installed). After installation I started the server and loged in with my username and password. Problem is I cannot see the server and cannot Authorise new device, which means I cannot setup the sharing of media folders. In the place where my server should be visual on the left side of screen there is nothing.
When (in NAS desktop) I click on Application the new tab is opened and I can log in, pin is correct and I get to the HOME page. In Settings there is no server and neither is in Authorised Devices. Has anybody had similar problem?
I can offer remote access for someone knowleadgable in case of need.
Donāt use Package Center for Plex downloads anymore until we get Package Center updated.
Perform a Manual Install of the SPK file for your machine
If your server data is there, installing the Production package will āUpgradeā from Beta ā Production software & structure
Be advised ā If you have a lot of media already indexed, it will take time while it moves all the files to their new location in the PlexMediaServer shared folder (this is where Plex lives now that weāre not in Beta) ā Do Not Interrupt it.
At this point, you probably wonāt be able to open it by http://LAN.Addr.of.Syno:32400/web but might get lucky.
ā Donāt use https
ā Donāt click the QuickConnect link.
If you still donāt have access - which is possible, now we can fix it
ā Uninstall w/ Keep (again)
ā Reinstall the same package you just installed EXCEPT
ā Use the Install using Plex Claim Token option.
ā Click āGet Plex Claim Tokenā
ā When your browser tab opens, COPY the token it gives you
ā Return to your Installation tab
ā PASTE the token into the box on the install window.
ā NEXT - NEXT - NEXT and let it install again.
What itās doing is:
Installs the software again
Uses the Claim Token you gave it to talk to Plex.tv
Plex.tv gives us fresh credentials for the server.
The installation script then updates your Preferences.xml
If you have it set to start after installation, PMS will start.
Now open again by IP address and follow what PMS is telling you (Got It) and/or Sign In)
If youāre still reading ,
The reason this is so detailed and drawn out is ā We can do only 1 thing at a time as the package installs. We can either upgrade the storage location or the Claim token.
(There isnāt usually enough time to do both before Package Center gets upset).
Doing it as two steps keeps Package Center from generating errors
i have done all these steps on my Synology DS 220+ but when i log in i still get " Not Authorized to access Server" and i do not see āvolume1ā in the library. i have given access the āPlexMediaā server in the Permission setting.
Looking at your logs, I can see where youāre clicking the Quick Connect link in Package Center to open PMS.
There is a restriction on when you canāt use this.
You canāt use it before you claim the server to your Plex account (Initial setup)
Jul 20, 2022 21:11:46.518 [0x7fef03183b38] DEBUG - Completed: [192.168.0.15:59752] 200 GET /web/static/362b56e7c69551249027.woff (6 live) GZIP 0ms 63712 bytes (pipelined: 8)
Jul 20, 2022 21:11:46.890 [0x7fef031a6b38] DEBUG - Request came in with unrecognized domain / IP '192-168-0-26.alexnas-home.direct.quickconnect.to' in header Host; treating as non-local
Jul 20, 2022 21:11:46.891 [0x7fef02f50b38] DEBUG - Request: [192.168.0.15:59743 (Subnet)] GET /identity (6 live) #71 GZIP
Jul 20, 2022 21:11:46.892 [0x7fef031a6b38] DEBUG - Completed: [192.168.0.15:59743] 200 GET /identity (6 live) GZIP 0ms 480 bytes (pipelined: 15)
Jul 20, 2022 21:12:05.064 [0x7fef03183b38] DEBUG - Request came in with unrecognized domain / IP '192-168-0-26.alexnas-home.direct.quickconnect.to' in header Host; treating as non-local
Jul 20, 2022 21:12:05.065 [0x7fef02f50b38] DEBUG - Request: [192.168.0.15:59743 (Subnet)] GET /web/index.html (6 live) #76 GZIP
If you look at the above, QuickConnect injects a full domain name.
Engineering has setup PMS to treat all unknown domains as REMOTE .
The default PMS security prevents anyone remote (not on your LAN) from claiming/setting up the NAS.
I can see the NAS IP is 192.168.0.26 and your IP is 192.168.0.15 which guarantees youāre local to it.
Iāve tried to get engineering to relax this but they tell me there are cases when the presence of a domain name in the header is a security risk ā so they block it.
The solution here is to open PMS using the IP address http://192.168.0.26:32400/web and completing the setup / attaching to your account (claimed)
Once itās claimed, while it will still complain in your logs, it wonāt block authentication.
Am usually ok with this kind of stuff but this program is something elseā¦ i tried logging in with the ip address provided above and it wont let me access plexā¦
,
