No Remote Access on TrueNAS Scale

Plex Media Server Remote Access
1

Server Version#: 1.32.4.7195
Player Version#: Web browser

I am currently having issues accessing my Plex server remotely. I migrated my Plex Server over to different hardware due to issues with the old hardware and I am currently unable to go back. When I check the Remote Access locally on my plex server, it says its connected.

image
image937Ă—533 50.4 KB

But when I go to plex via app.plex.tv/desktop, the server says that it is connected indirectly.
image
image252Ă—134 3.45 KB

My current setup:
ATT Modem > Opnsense Router (192.168.1.1)> Unmanaged Switch > TrueNAS Server (192.168.1.2)

ATT Modem Config:
I currently have the port forwarding set for port 32400.

image
image976Ă—617 35.6 KB

At the moment I have set IP Passthrough to pass through to my Opnsense router.
image
image658Ă—614 25.6 KB

One red flag I have noticed here, is that if I do this before forwarding the port, I am unable to select Opnsense as the device on the port, so I have to do the IP passthrough 2nd. Is this redundant?

Opnsense Config:
I have assigned the static IP address 192.168.1.2 to the TrueNAS server. I then Port Forwarded 32400 to the IP address 192.168.1.1

image
image1141Ă—438 17.3 KB

image
image1114Ă—449 16.1 KB

TrueNAS Scale/Plex Config:
Here are some screenshots of the config setup for the Truechart’s version of Plex.

image
image747Ă—156 3.7 KB

image
image744Ă—213 5.91 KB

image
image751Ă—189 4.77 KB

Plex Logs:
Plex Media Server Logs_2023-07-14_15-01-58.zip (1.2 MB)

Any insight would be helpful. I will be leaving for the weekend starting tomorrow, so there is a chance that I might be slow to respond.

2

if I do this [Passthrough] before forwarding the port, I am unable to select Opnsense as the device on the port, so I have to do the IP passthrough 2nd. Is this redundant?

Yes, it’s redundant. Passthrough is all ports.

Does it work remotely, just not from the LAN?

From your logs, something is blocking Plex’s DNS+SSL magic. This can be enough to prevent local LAN connections from being “Direct” even though remote connections may work.

Jul 14, 2023 12:22:40.320 [140180378696336] DEBUG - Network: 172-16-2-66.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 172.16.2.66 but instead yielded (null)

In OPNSense, I think it’s here:

Services > Unbound DNS > Advanced
Add plex.direct to Private Domains
Apply, then restart the Unbound service

3

OMG that worked! You sir are a gentleman and a scholar.

1 Like
4

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