@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 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
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.
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
Uninstall with the KEEP option
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.
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.
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
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
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.
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.”