Browsing PMS using its IP treated as local, but browsing it via FQDN treated as non-local--why?

Plex Media Server
1

Server Version#: 1.42.2.10156-f737b826c
Player Version#: 4.147.1

I’ve been using Plex Media Server for years, starting with it running in a jail on FreeNAS, and then through all the subsequent FreeBSD versions with no problem. Through all this, I was able to get to all my content by browsing to the FQDN of the server (e.g., server.foobarbaz.quux:32400) from any PC/Mac on my home network (192.168.100.0/24). I’m not a Plex Pass user, and don’t need to serve anything outside of my home network.

Eventually, it was time to get the TrueNAS machine updated to the new Linux-based stuff. I did the migration and experienced no problems. The old Plex Media Server iocage jail wasn’t migrated, of course, but it was pretty straightforward to stand up the Plex “app” (basically a Docker container), and in a few minutes I could see all my stuff when I browsed to server.foobarbaz.quux:32400.

However, I couldn’t play anything; instead, I’d get a pop-up window saying that I needed to buy a Remote Watch Pass first.

But I’m not remote; my browser is on 192.168.100.1, and the Plex Media Server is on 192.168.100.252.

Looking through the wrench/spanner menu, I noticed the following line in the console output:

Request came in with unrecognized domain / IP ‘server.foobarbaz.quux’ in header Host; treating as non-local

After seeing this, I then browsed to 192.168.100.252:32400 and was able to play my content.

Is there some setting for Plex Media Server to tell it that “server.foobarbaz.quux” is, in fact, local? The server gets its IP via DHCP from my pfSense router, which also provides name service for my network (including the server).

When I was running the older FreeBSD versions of TrueNAS, I could point my browser at server.foobarbaz.quux:32400 and it all just worked. Is there a way to get back to that, or is working exclusively with IP addresses just how things are done these days?

Any light anyone could shed on this would be greatly appreciated…

2

Have you tried adding you custom URL to:
Settings -> [Select Server] -> Custom Server Access URLs

But why the need to use a custom URL in the first place? If you’re only accessing it from the local network, the bare IP address should be sufficient. Or app.plex.tv will get you where you need to go with no fuss and no muss.

3

Just a thought, on the TrueNAS, did you set Plex to run in Host mode? If not, it’s running Bridge and creating its own isolated network which would trigger the remote watch pass prompt.

4

I considered that, but the above made me think they’re in host most.

5

Is that the same IP they see on the Remote Access page under PrivateIP, that would confirm.

6

This is not a private IP address space.

7

To add to Otto,

You might be thinking of 192.168.x.x which is part of the RFC-1918 private network address specification.

8

I’ve run it in both bridge and host modes, and both will not trigger the remote watch pass prompt if I access the server by IP address, and will trigger the remote watch pass prompt if I access the server by FQDN.

9

I have not; where do I find this?

The bare IP address does work, but as a former IT guy, using a bare IP address offends my sensibilities. :wink: That said, I may well just grit my teeth and do it anyway.

It will indeed, but it will point me at the FQDN, and so it’ll trigger the remote watch pass pop-up, so it’s not very useful.

10

And you’re absolutely correct. Being a knucklehead, I used “172” instead of “192” in my post. I just corrected it. Thanks for pointing that out!

11

I fumbled the IP addresses in my original post; my home network uses 192.168.100.0/24. I’ve corrected that in my original post.

12

I’m sorry; I’m not sure I understand what you’re saying.

13

Sorry, I was responding to the other commenter about Host vs Bridge mode. Was just saying that if the Private IP on the Remote Access page in Plex matches the IP of the server, you’re not in Bridge mode. The private IP would show as 172.x in bridge mode. But you clarified you’ve tried both and that the IP you noted originally was a typo.

14

Ah, got it. Thanks for the clarification!

15

Ah, never mind–I just found it. As my Dad would say, if it had teeth, it would’ve bitten me! :grin:

16

Just wanted to post a quick update to close out this thread.

I’ve decided to just access it via IP address.

I’m annoyed that something that “just worked” under the FreeBSD-based TrueNAS line has proven to be either something that’s no longer possible or, more likely, something that’s possible, but only under some permutation of settings across Plex Media Server, Docker, TrueNAS, and plex.tv that I’ve not discovered.

Thanks to everyone for your suggestions; I do appreciate the time you’ve taken to respond!