Plex server “indirect” connection, TrueNAS & pfSense

Apps and Virtualization
1

Server Version#: 1.1.14
Player Version#: Connecting via multiple players & web player

The server is running in a TrueNAS container with an internal container IP of 172.16.1.2:32400 and a local IP address of 192.168.4.14:32400. On the Internet it can be found at 45.19.23.43:3290
I don’t know if it makes a difference, but the Plex Remote Access settings page shows the container IP as opposed to the local IP.

When I check the server stats, it shows I have an indirect connection. When I look at the relay it shows my server is fully accessible from the Internet.
My content is fully accessible both on local LAN and the Internet, but that ‘!’ is giving me a bad case of Forrest Whitacre eye so it needs to get fixed.

I’m running pfSense 2.7.2 with an override of:

server:
private-domain: "plex.direct"

in the DNS resolver settings.

I completely turned off DNS rebinding protection, for testing and there was no difference.

Looking for anything else that may be able to resolve this issue.

2

Might be worth it to try host mode network instead of bridging for that container.

3

What’s the issue exactly?

4

Had the same issue myself on a new clean Plex-install.
I had to enable host network for my instance of Plex. Then i got local connection, instead of “remote” only.
Im a newbie TrueNAS and docker person, so i have no idea what might be the reason/problem.

1 Like
5

Not sure if there are any negative repercussions for doing this, but it does indeed seem to resolve the issue.
I can’t THINK of any specific downside to turning this feature on, even though the ‘tool tip’ suggests “It’s recommended to keep this disabled.”

6

This also fixed the same issue for me, I’m also a bit new and I’m very greatful you posted this here as I was trying to figure this out for hours.

1 Like