Plex Media Server - Not Authorized You Do Not Have Access To This Server

@Richieyute

This one isn’t on you in any way. There is a problem with PMS for ARM systems
There is a problem with PMS when it first installs on ARMv7 systems

Please do the following workaround.

  1. Uninstall the Plex package with the ERASE option (to remove the broken DSM 7 installation)
  2. Download and install this package from my Google Drive using the Plex Claim Token method ( Because your IP addresses are not RFC-1918 compliant here )
  1. After it is installed, you can upgrade to the normal DSM 7 package you already have in your possession.

@ChuckPa Very much appreciate you coming back to me, but after following your instructions, then also change my LAN IP to be 10.10.10.X, which I believe should now be RFC - 1918 compliant, I am sadly no closer to getting this stuff to work.

I am now getting this can’t be reached message now. Anyway I have uploaded my recent Logs.zip (4.8 KB)

Is there anything else I could try that doesn’t include a hammer or drill…seriously, I regret upgrading to DSM 7.

@ChuckPa Ignore the server log as it might be the old one and I am tired now…so best come back to you later.

@Richieyute

Your logs show a known database start problem on ARMv7 systems.
It only happens on a brand new installation for PMS 1.23.0 and above.

We’re awaiting a fix from engineering.

Once you install with 1.22.3, you will have that working database you need.

All upgrades, Auth, and any Claim Token usage will work as expected.

@ChuckPa Hey thanks again for your reply…I got up this morning and basically tried your steps again, so I have 1.22 running and my server was claimed without any visual issue.

Once installation was down I open Plex, but this time I am presented with the below screens

Then I simply open up in incog in chrome, I was still hit with the same issue, but out of desperation I hit the browser back button then I was in…I can see my server, I can also add libraries…Just going to keep my fingers cross that Roku works now…Massive thanks for your time and help again

I have a similar problem:
Have an existing Synology Plex server that’s workings, busy installation a new one with bigger storage attached. Copied all the media across but get the not authorizen screen on setup. However when I remove some extra characters up until setup, I get in but it connects to the old existing Synology

Plex Media Server-2.log.zip (39.6 KB)

Would you be able to assist with getting the new Plex server up, please

@Richieyute

I’m sorry I didn’t see this until now.

It sounds like you have a split install (what can happen when installing / repairing from Package Center). You end up with two (one disconnected, one new) server data sets on the box.

Might this be the case for you?

@MasterEA

Since you have two servers on your LAN, it’s sometimes (more often than not actually) easier to install the package with the “Plex Claim Token” option.

What this does is gets the server all signed into your account so you don’t have to fuss with the other server interfering.

As for the second image, that’s simply a “Hey, I don’t know this machine. Is it what you expect?” (anti-phishing). Since the IP address is on your LAN, if you indeed recognize it then you ignore it.

I recommend using the Plex Claim Token method to get this up

  1. Uninstall with the KEEP option
  2. Reinstall ,
    a. Click “Install using Plex Claim Token”
    b. Click “Get Plex Claim token”
    c. Browser opens a claim token is presented.
    d. COPY it
    e. Return to the installer page.
    f. Paste into the box
    g. Click NEXT to continue installation
    h. It will take about 15-20 seconds longer than normal because it’s communicating with Plex.tv to setup the server for you before it actually starts it.
2 Likes

I have tried that option as well. Still get the same error
Logs.zip (129.8 KB)

@MasterEA

Do you intend for your Synology to be using a Public WAN address?

Sep 19, 2021 21:38:56.972 [0x7f3f39b1d258] DEBUG - Detected primary interface: 172.0.69.30
Sep 19, 2021 21:38:56.972 [0x7f3f39b1d258] DEBUG - Network interfaces:
Sep 19, 2021 21:38:56.972 [0x7f3f39b1d258] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Sep 19, 2021 21:38:56.973 [0x7f3f39b1d258] DEBUG -  * 3 eth1 (169.254.32.117) (loopback: 0)
Sep 19, 2021 21:38:56.973 [0x7f3f39b1d258] DEBUG -  * 4 eth0 (172.0.69.30) (loopback: 0)
Sep 19, 2021 21:38:56.973 [0x7f3f39b1d258] DEBUG -  * 1 lo (::1) (loopback: 1)
Sep 19, 2021 21:38:56.973 [0x7f3f39b1d258] DEBUG -  * 4 eth0 (fe80::211:32ff:fe17:9537%eth0) (loopback: 0)
Sep 19, 2021 21:38:56.973 [0x7f3f39b1d258] DEBUG - Creating NetworkServices singleton.

172.16.x.x → 172.31.x.x is the range for RFC-1918 compliant private networks.

Not at all, the 192.168.x.x or 10.10.x.x address is used commonly across networks I connect to via VPN. Having too many routing problems. Just opted to use the 172.169.x.x address.

@MasterEA

If you use a Public IP address, PMS will treat everything, including all devices on your LAN, as REMOTE.

Looking at your account, I don’t think you want to collide with this host?

[chuck@lizum ~.2012]$ nslookup 172.0.69.30
30.69.0.172.in-addr.arpa	name = adsl-172-0-69-30.lightspeed.miamfl.sbcglobal.net.

Authoritative answers can be found from:

[chuck@lizum ~.2013]$ 

Plex.tv and all the internet routers will send your traffic there and not to you.

You really should pick something RFC-1918 compliant

10.x.x.x, 172.16.x.x-172.31.x.x , or 192.168.x.x

No problem - Will change the network from 172.0.x.x to 172.169.x.x tonight once I get home

I see your point. So change to 172.16.x.x
Thought the internal address gets Nat through your external IP

I have the same problem and need your help!
I’m using DS220j DSM7.0.
When I open it to Plex Media Server (IP: 100.64.1.201:32400/), it says Not Authorized.
I have tried the workarounds talked about in the thread.

I downloaded the Plex installer from the Plex website.
PlexMediaServer-1.24.3.5033-757abe6b4-aarch64_DSM7.spk

I will provide the Log file.Logs.zip (781.8 KB)

Is 100.64.1.201:32400 your LAN IP ?

That looks like CGNAT Public IP

Continuing the discussion from Plex Media Server - Not Authorized You Do Not Have Access To This Server:

Thank you for your answer.

The following IP is the local IP address of my LAN.
IP: 100.64.1.201

The network administrator has assigned this IP range, so I cannot change it.

Does the specification require compliance with RFC 1918 to work?
I have changed the URL to log in to DSM to the host name of the NAS.
Is this the same reason why I can’t get it to work when I log in with this hostname address?

i have the same problem “Not authorized” and i can tell you is not because of the LAN ip.i update to truenas 12 and it mest up plex pretty good.not sure what is going on, but i reinstall truenas, redone the jails, with and with out pluging, and still nothing.i know they introduce a thing where you have to add a user id 987, but thats more for to read the media folder.i dont even get there. any solution to any of this?

oh i know. sorry. i just though to jump in and state that this is a problem that affect pretty much everyone, on different platforms, even win, mac and linux.
wish you guys the best.

Thanks for the explanation.

Is the following explanation correct in meaning in a double NAT configuration
“If you are able to, plug a router into your network using the WAN input port on the router.”

Example:
[NAS] —(LAN port)[router](WAN port) — [router] — (internet)