Plex setup "Not Authorized"

Harlan · September 26, 2022

Not authorized

You do not have access to this server

I've been through the setup process with different hardware and different OSs. I'm considering just running it off of Windows at this point.

With unraid and truenas I'm getting not authorized when I try to actually manage the server.
After looking into the preferences.xml and claiming the account a bunch I'm not sure what's the matter. I even used a different email because originally my email started with a number.

I had pfsense running as my router not too long ago. I switch back to netgear to rule that out too.

I'm stumped. All the videos I watch are like - just set this up 123 we're streamin'!

I could use a hand with this.

Using a Dell T320
2x 8TB SATA drives
1x 128GB nvme ssd as cache

Unraid Version: 6.11.0
Intel NICs from mobo unplugged. Using 2.5gig realtek pcie card
PERC 710 card, removed Dell firmware

Honestly this must be a software thing. I'm just kinda proud of the build.

Maybe it's related to whatever's at the end of this url
http://192.x.x.x:32400/web/index.html#!/setup/xxxxxxxxxxxxxxxxxxxxxx

I got the idea to manually search for the server with HTPC app from Ben, but it gives a different error. Intead of not authorized, HTPC states that the connection's unavailable.

Jarsky · September 26, 2022

1 hour ago, Harlan said:

Maybe it's related to whatever's at the end of this url
http://192.x.x.x:32400/web/index.html#!/setup/xxxxxxxxxxxxxxxxxxxxxx

I see you tried to obfuscate this URL, theres no need to do that with a private (internal) IP address, but from the hyperlink i see its 192.169.1.69. This IP subnet is public.

You should change it to something in the private range.

Plex needs to reach out to the plex authentication service and return back, and its probably getting mixed up by the public IP address.

You should be using one of these ranges:

Class A: 10.0. 0.0 to 10.255. 255.255.

Class B: 172.16. 0.0 to 172.31. 255.255.

Class C: 192.168. 0.0 to 192.168. 255.255.

e.g 192.168.1.69

Typically for home use, Class A or Class C are used for routing your network, and Class B is used for containers (inter-container traffic).

Jarsky · September 26, 2022

Additionally once you get in, you should go into your server settings, and define your local networks there to ensure Plex treats any internal networks as internal traffic.

If you have more than 1 network, use a comma seperator, like mine below.

Harlan · September 27, 2022

Well I wanted to obfuscate because I don't believe it's part of the problem.

I'm trying to hit it from a computer at 192.169.1.11 let's say. When I reach the web UI it's via IP.

I should have added a screenshot.

It's not a 404 page from just anywhere.

Maybe I can disconnect my internet to test this.

Jarsky · September 27, 2022

2 hours ago, Harlan said:

Well I wanted to obfuscate because I don't believe it's part of the problem.

I'm trying to hit it from a computer at 192.169.1.11 let's say. When I reach the web UI it's via IP.

I should have added a screenshot.

It's not a 404 page from just anywhere.

Maybe I can disconnect my internet to test this.

Plex needs to be connected to the internet to authenticate.

I'm not guaranteeing its the problem, but imo its the most likely issue especially across multiple installs if its the 192.169.0.0/23 network has been the single constant.

Plex doesnt care about your hardware for authentication, and I doubt its software since you said you've tried multiple OS's (which means multiple versions of packages).

The entire 192.169.0.0/23 subnet is a public network.

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2022, American Registry for Internet Numbers, Ltd.
#


NetRange:       192.169.0.0 - 192.169.1.255
CIDR:           192.169.0.0/23
NetName:        PSG169
NetHandle:      NET-192-169-0-0-1
Parent:         NET192 (NET-192-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   RGnet, LLC (RGNETI-1)
RegDate:        2005-04-12
Updated:        2021-12-14
Comment:        Geofeed https://rg.net/geofeed
Ref:            https://rdap.arin.net/registry/ip/192.169.0.0


OrgName:        RGnet, LLC
OrgId:          RGNETI-1
Address:        5147 Crystal Spring
City:           Bainbridge Island
StateProv:      WA
PostalCode:     98110
Country:        US
RegDate:        1990-10-01
Updated:        2021-10-06
Ref:            https://rdap.arin.net/registry/entity/RGNETI-1

LIGISTX · September 27, 2022

5 hours ago, Harlan said:

192.169.1.11

As the poster above me said, if this is what your internal network is set up as, your going to have issues… you can’t have a public IP as your private LAN subnet of you want anything to work right. Don’t obfuscate the first 2 numbers, because if you really are using 192.169.x.x, we likely found your issue. You can change the third number to whatever you want, 192.168.x.x is a valid private IP as shown below. Anything outside of these ranges, and your going to have a bad time.

7 hours ago, Jarsky said:

You should be using one of these ranges:

Class A: 10.0. 0.0 to 10.255. 255.255.

Class B: 172.16. 0.0 to 172.31. 255.255.

Class C: 192.168. 0.0 to 192.168. 255.255.