Plex Media Server running on QNAP is not detecting that it's running

Plex Media Server NAS & Devices
1

Server Version#: 1.23.4
Player Version#: N/A

Hello,

I’ve had a Plex account for a long time but I’m only really trying to utilize it now. I cannot get a Plex Media Server to work from a NAS.

This is not limited to a specific NAS. I have tried a Western Digital, QNAP, and Synology NAS for this.

Currently I’m using the QNAP, but the problem is the same every time. I can install the PMS app and it’s running on the NAS, but when I open the app it takes me to a login page for the PMS at the IP address of the NAS followed by port 32400.

The first time it asks me to sign in and then shows a Plex page, but it just shows my media library is empty and there’s a button to ‘Get Plex Media Server’. After the first attempt, trying to open it from the NAS typically brings me to a page that lets me choose a Plex account login, but then it says it’s not authorized to access the server.

I’ve tried using multiple browsers. I’ve also tried using incognito mode, clearing my cookies, using another PC, rebooting all of the NAS devices I’ve tried, logging out after installing then logging back in, and even multiple Plex accounts.

In my “Authorized Devices” within the Plex page that opens up, it only ever shows my web browser, so it seems like it’s never authorizing the NAS (even though the NAS is being used as the server…).

I’ve seen similar problems on many other forums and help threads, and there’s usually never a resolution, or it’s a different fix every time. I’m really hoping I don’t have to try using Wireshark to figure this out, and I’m pretty disappointed that the only support Plex has in-house seems to be for billing.

Please help, as I’ve spent many many hours on this already.

2

If incognito mode doesn’t work, the obvious questions are:

  1. LAN IP of the QNAP and of the Computer you’re using? Are they on the same RFC-1918 subnet ?

  2. You can create a shared folder, named (exactly) PlexData

  • Stop Plex

  • Start Plex

  • Wait 30 seconds

  • Stop Plex again

  • Open File Station

  • Navigate PlexData/Plex Media Server

  • Right-click ‘Logs’ → Compress

  • Download the Logs.zip file

  • Attach it here for us to review and see what’s wrong.

3

Hello,

Thanks for the response. This is already somewhat enlightening.

I was able to create the PlexData directory, and after restarting the service as directed, it did create the Media Server folder within it! That’s the first time this happened.

When I tried to compress the logs, I didn’t have the option to. When I tried to compress the enclosing folder, it said I didn’t have the permissions, even though the account I was using is part of the administrators and everyone groups.

I think one of the problems is that I disabled the default admin account on the QNAP for added security and was trying to use my own account as the real admin user. Once I enabled the admin account I was able to compress the logs. This also makes me concerned as there doesn’t seem to be a way to set default folder ownership to an account that isn’t the default admin one…

Attached are the logs. Normally I’d scrub through logs myself but I don’t have the ability to do that at the moment.

Thanks!

MODERATOR EDIT: Logs removed for privacy

4

Thank you for the logs.

I found it immediately.

The ethernet adapter is using a public IP address.

Nov 08, 2021 23:16:14.353 [0x75e67ed0] DEBUG - * 2 eth0 (21.21.21.77) (loopback: 0)

This is the root of the problem. It’s not per ITU & RFC-1918 standard.

Judging by the numbering, it looks like you kinda-randomly chose 21.21.21.x for your home LAN?

Would it be possible to change that easily ? ( Change the DHCP server so everything on your home network is in compliance with RFC-1918 ?

5

The Ethernet adapter of the QNAP? That sounds very strange as it’s on the same LAN (not using any VLANs) as all my other devices, and connected to the same 8-port managed switch. It’s also getting a DHCP IP from my network which is how I’m able to access it (21.x.x.x is my network).

6

I recognize the IP range in use. Is that required because of where you reside ? (Internet is provided to you that way)

7

Oh, the rest of your reply loaded in after I already responded.

That’s interesting…I work on networks fairly regularly and I’ve never had an issue with a custom IP scheme like that. Is this a NAS-specific thing?

(I created the 21.x.x.x network just to keep things differentiated in my mind. My public IP is from Xfinity and starts with 69 or 73)

8

Look up RFC-1918.

It’s the spec which defines “Private Network” and how all home modem/routers differentiate between LAN and WAN addressing blocks.

The ideal solution for you would be to have a LAN subnet address anywhere in

  • 192.168.x.x
  • 10.x.x.x
  • 172.16.x.x - 172.31.x.x
9

To add -

Given you selected 21.x.x.x to keep things distinct, you might want to know your LAN IP addresses collide with DNIC

NetRange:       21.0.0.0 - 21.255.255.255
CIDR:           21.0.0.0/8
NetName:        DNIC-SNET-021

This is what’s blocking PMS because that’s a Public IP and not a Private IP.

The packets you’re sending are getting routed back to some machine somewhere on the DNIC network.

10

I’ll check that out for sure. I’m just surprised I haven’t come across it before. Looks like I’m going to need some network downtime in the near future… I’m going to have to redo some static IPs too. If me using 21.x.x.x as my network ends up being the reason, thanks for the help.

11

It is the reason PMS can’t authenticate / work.

I’ve seen these situations before.

As soon as your LAN is back in compliance,

  1. Comcast will be a lot happier
  2. PMS will work
  3. You’ll be able to use Remote Access if you so choose .
12

Oh, that’s not great. I figured NAT, the routing tables, and MAC addresses would have prevented something like that from happening.

13

If you look at the backbone’s BGP routing tables, You’d find any packets getting sent to you are also getting send elsewhere . Their firewalls are blocking them from entering but proper netiquette would be to get it right again…

Remember, MAC accesses aren’t routable. Only IP addresses are

14

BGP-scale networks are outside of my experience so far, but thats good to know and I have some important things to review.

For the MAC addresses I more meant that I thought their arp entries would help, but I guess the way these packets are being routed isn’t affected by that.

Thank you for your help. I’ll try to come back to this thread and post the results of my changes so others can use this in the future.

15

For follow-up, the above resolved my issue. Changing from a 21.x.x.x network to something suggested by RFC1918 allowed me to access the server as expected.

Thanks!

1 Like
16

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.