TrueNAS 12.0 U8 - Trying to Install Plex Manually & Having Network Issues

truenasjw · Apr 10, 2022

Hello, I have been racking my head for a while now and I am thought I would ask the great and almighty Internet for the answers to my problem. The problem is probably so obvious that I cannot see it, but maybe you can. I have created a new TrueNAS 12.0-U8 system on bare metal. The OS is running great and I have no problems accessing the NAS via SSH, SMB, and NFS. The Plugin for Plex and Plex beta fail to install no matter how many times I try... but that is neither here no there because I have a Plex Pass so I know I will have to manually install the application anyways.

I followed the instructions to install Plex manually from here. I cannot get past the section "Access Web Interface" because my desktop cannot reach the Plex web interface. I have tried from numerous Windows systems on this very flat LAN without any security or VLANS... and yet the browsers just timeout without any response from the Plex server.

I can ping hosts on the LAN, I can reach the gateway router, I can resolve hostnames, I can also reach the Internet. I can do everything EXCEPT reach the Plex interface from my desktop.

To troubleshoot the problem I have tried every combination of creating 3 different jails with all the different combinations of:

RELEASE
12.3-RELEASE-p5 (current)
12.0-RELEASE-p13 (attempted)
11.4-RELEAE-p13 (attempted)

BASIC PROPERTIES
DHCP (attempted)
NAT (attempted)
VNET (current)

This is my CURRENT typology:
192.168.0.1 <-- Default Gateway
192.168.1.100/16 <-- igb0 <-- TrueNAS
192.168.1.101/16 <-- igb0:bridge0 <-- Plex Jail

This are my CURRENT jail settings:
(unchecked) DHCP Autoconfigure IPv4
(unchecked) NAT
(checked) VNET
(checked) Berkeley Packet Filter

vnet_default interface = igb0 (I have tried auto as well at times)
IPv4 Interface = vnet0
IPv4 Address = 192.168.1.101
IPv4 Netmask = 16
IPv4 Default Router = 192.168.0.1

(unchecked) Autoconfigure IPv6

(checked) Auto-start

My basic networking works great... but can't get the darn Plex interface to appear.

ifconfig from Plex Jail:

Code:

root@plex:~ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
        groups: pflog
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 26:e9:b3:14:fa:0a
        hwaddr 02:12:a6:02:6f:0b
        inet 192.168.1.101 netmask 0xffff0000 broadcast 192.168.255.255
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=1<PERFORMNUD>

arp -a from my Windows desktop:

Code:

Interface: 192.168.5.201 --- 0x8
  Internet Address      Physical Address      Type
  192.168.0.1           6c-ae-f6-b6-03-d2     dynamic <-- Gateway
  192.168.1.100         24-e9-b3-16-08-30     dynamic <-- TrueNAS

arp -a from Plex Jail:

Code:

root@plex:~ # arp -a
? (192.168.5.201) at 80:38:fb:88:84:25 on epair0b expires in 427 seconds [ethernet]
? (192.168.4.43) at 8c:5a:25:b9:8c:20 on epair0b expires in 497 seconds [ethernet]
? (192.168.0.1) at 6c:ae:f6:b6:03:d2 on epair0b expires in 1176 seconds [ethernet]
? (192.168.4.64) at 4c:12:65:f6:5e:ae on epair0b expires in 1177 seconds [ethernet]

ping google.com from Plex Jail:

Code:

root@plex:~ # ping google.com
PING google.com (142.250.189.174): 56 data bytes
64 bytes from 142.250.189.174: icmp_seq=0 ttl=117 time=11.572 ms
64 bytes from 142.250.189.174: icmp_seq=1 ttl=117 time=11.638 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.572/11.605/11.638/0.033 ms

netstat -a from Plex Jail:

Code:

root@plex:~ # netstat -a
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address          Foreign Address        (state)
tcp4       0      0 plex.54516             192.168.4.64.9080      TIME_WAIT
tcp4       0      0 plex.18102             192.168.4.43.9080      TIME_WAIT
tcp4       0      0 plex.65449             192.168.4.64.9080      TIME_WAIT
tcp4       0      0 localhost.32600        *.*                    LISTEN
tcp4       0      0 localhost.50725        localhost.35082        CLOSED
tcp4       0      0 localhost.35082        *.*                    LISTEN
tcp4       0      0 localhost.65447        localhost.27885        ESTABLISHED
tcp4       1      0 localhost.27885        localhost.65447        ESTABLISHED
tcp4       0      0 localhost.46921        localhost.50450        ESTABLISHED
tcp4       0      0 localhost.50450        localhost.46921        ESTABLISHED
tcp4       0      0 localhost.32401        *.*                    LISTEN
tcp46      0      0 *.32400                *.*                    LISTEN
udp4       0      0 plex.31917             *.*
udp4       0      0 *.1901                 *.*
udp4       0      0 plex.44694             *.*
udp4       0      0 plex.49199             *.*
udp4       0      0 *.32413                *.*
udp4       0      0 *.32412                *.*
udp4       0      0 *.32410                *.*
udp4       0      0 *.32414                *.*
Active UNIX domain sockets
Address          Type   Recv-Q Send-Q            Inode             Conn    Refs          Nextref Addr
fffff8132f435200 dgram       0      0                0 fffff8274c72f800       0 fffff8026c5a9d00
fffff8026c5a9d00 dgram       0      0                0 fffff8274c72f800       0                0
fffff8274c72f800 dgram       0      0 fffff82731da41e0                0 fffff8132f435200                0 /var/run/logpriv
fffff823673acd00 dgram       0      0 fffff82731da43c0                0       0                0 /var/run/log

I am not sure if there is any port security or VIP things that I have missed which would be standing in my way but if anyone has any suggestions I am ready to play the game. Thank you in advanced for your time.

truenasjw · Apr 10, 2022

Just for kicks and giggles I completely disabled my Windows Firewall and no change. I still believe the problem to be between the jail and the TrueNAS someplace.

truenasjw · Apr 10, 2022

I installed wget with 'pkg install wget' and then I tried to access the Plex interface and it works. Still doesn't answer the million pesos question of why I cannot access the Plex web interface from anywhere else on the network.

wget from Plex Jail:

Code:

root@plex:~ # wget http://192.168.1.101:32400/web
--2022-04-10 19:34:06--  http://192.168.1.101:32400/web
Connecting to 192.168.1.101:32400... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://192.168.1.101:32400/web/index.html#!/setup/80dd3d247e31a78c7be360199a51b067ee8a6dbb [following]
--2022-04-10 19:34:06--  http://192.168.1.101:32400/web/index.html
Reusing existing connection to 192.168.1.101:32400.
HTTP request sent, awaiting response... 200 OK
Length: 9206 (9.0K) [text/html]
Saving to: ‘web’

web                 100%[===================>]   8.99K  --.-KB/s    in 0.04s

2022-04-10 19:34:06 (214 KB/s) - ‘web’ saved [9206/9206]

root@plex:~ # more web
<!DOCTYPE html>
<!--
   =======   ==
  /==////== /==
  /==   /== /==   =====   ==   ==
  /=======  /==  ==///== //== ==
  /==////   /== /=======  //===
  /==       /== /==////    ==/==
  /==       /== //======  == //==
  //        //   /////   //   //

  Credits
   * Glyphicons - http://glyphicons.com
-->
<html lang="en" data-cast-api-enabled="true">

truenasjw · Apr 10, 2022

I also tried from my android phone and a Chromebook... same results. Cannot reach the Plex web interface, but the TrueNAS web interface comes back fine meaning it is neither a firewall or network issue and the problem has to reside within the TrueNAS domain.

jgreco · Apr 11, 2022

truenasjw said:
I also tried from my android phone and a Chromebook... same results. Cannot reach the Plex web interface, but the TrueNAS web interface comes back fine meaning it is neither a firewall or network issue and the problem has to reside within the TrueNAS domain.

No, it's a networking problem. It may be a networking problem related to what you've done inside TrueNAS, but that doesn't make it a TrueNAS problem.

You've selected "NAT" which puts your VM behind a NAT. Machines outside the NAT will not be able to access your VM. Turn off the NAT. I believe that's your problem here. Also turn off DHCP and let your VM bridge onto your main network, picking up your primary DHCP server's assignment.

truenasjw · Apr 11, 2022

Sorry for any confusion... I have *tried* all the different basic network settings; but the one that I continue to focus on is my desired VNET. So here is my current typology and jail settings:

192.168.0.1 <-- Default Gateway
192.168.1.100/16 <-- igb0 <-- TrueNAS
192.168.1.101/16 <-- igb0:bridge0 <-- Plex Jail

Anywhere I said VIP, I consider that to be the abbreviation for Virtual IP.

(unchecked) DHCP Autoconfigure IPv4
(unchecked) NAT
(checked) VNET
(checked) Berkeley Packet Filter

vnet_default interface = igb0 (I have tried auto as well at times)
IPv4 Interface = vnet0
IPv4 Address = 192.168.1.101
IPv4 Netmask = 16
IPv4 Default Router = 192.168.0.1

(unchecked) Autoconfigure IPv6

(checked) Auto-start

(checked) allow_set_hostname
(unchecked) allow_raw_sockets (I have tried enabled at times, especially when using attempting NAT)

Interfaces = vnet0:bridge0

(checked) ip4.saddrsel
(unchecked) ip6.saddrsel

ip4 = New
mac_prefix = 26e9b3

I can wget the Plex Web Interface through wget from TrueNAS and of course I can from within the Plex Jail as well. Nothing on the local LAN can however reach 192.168.1.101 (Plex Jail), not in ARP Tables, not to ping, not to web to 32400. With this clarification, I hope this helps present the present state of my system better. If there are any configuration files that would serve better to convey my system settings, please just let me know which ones (I am not a TrueNAS Admin by trade).

truenasjw · Apr 11, 2022

Just a thought, do I need to do anything within TrueNAS | Network | Interfaces | Add ? Do *I* have to manually configure a Bridge Interface to allow systems on the LAN to know that the .101 (Plex Jail) is behind .100 (TrueNAS)?

truenasjw · Apr 11, 2022

ifconfig from TrueNAS Shell:

Code:

root@truenas[~]# ifconfig
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e123bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 24:e9:b3:16:08:30
        inet 192.168.1.100 netmask 0xffff0000 broadcast 192.168.255.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=9<PERFORMNUD,IFDISABLED>
igb1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 24:e9:b3:16:08:31
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
igb2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 24:e9:b3:16:08:32
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
igb3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 24:e9:b3:16:08:33
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
        groups: pflog
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:d2:30:4a:c2:00
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto stp-rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge
        nd6 options=1<PERFORMNUD>

netstat -a from TrueNAS: (there is no 32400 listener at the TrueNAS OS Level... why?)

Code:

root@truenas[~]# netstat -a
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address          Foreign Address        (state)
tcp4       0      7 localhost.x11          localhost.65443        ESTABLISHED
tcp4       0      0 localhost.65443        localhost.6000         ESTABLISHED
tcp4       0      7 192.168.1.100.http     192.168.5.201.58679    ESTABLISHED
tcp4       0      0 localhost.x11          localhost.26039        ESTABLISHED
tcp4       0      0 localhost.26039        localhost.6000         ESTABLISHED
tcp4       0      0 192.168.1.100.http     192.168.5.201.58676    ESTABLISHED
tcp4       0      0 localhost.x11          localhost.23803        ESTABLISHED
tcp4   53782      0 localhost.23803        localhost.6000         ESTABLISHED
tcp4       0  33336 192.168.1.100.http     192.168.5.201.59113    ESTABLISHED
tcp4       0      0 192.168.1.100.microsof 192.168.5.201.55144    ESTABLISHED
tcp6       0      0 *.http                 *.*                    LISTEN
tcp4       0      0 *.http                 *.*                    LISTEN
tcp6       0      0 *.https                *.*                    LISTEN
tcp4       0      0 *.https                *.*                    LISTEN
tcp4       0      0 *.ssh                  *.*                    LISTEN
tcp6       0      0 *.ssh                  *.*                    LISTEN
tcp4       0      0 192.168.1.100.5357     *.*                    LISTEN
tcp4       0      0 *.netbios-ssn          *.*                    LISTEN
tcp4       0      0 *.microsoft-ds         *.*                    LISTEN
tcp6       0      0 *.netbios-ssn          *.*                    LISTEN
tcp6       0      0 *.microsoft-ds         *.*                    LISTEN
tcp4       0      0 *.881                  *.*                    LISTEN
tcp6       0      0 *.992                  *.*                    LISTEN
tcp4       0      0 *.elcsd                *.*                    LISTEN
tcp6       0      0 *.elcsd                *.*                    LISTEN
tcp6       0      0 *.nfsd                 *.*                    LISTEN
tcp4       0      0 *.826                  *.*                    LISTEN
tcp6       0      0 *.826                  *.*                    LISTEN
tcp4       0      0 *.nfsd                 *.*                    LISTEN
tcp4       0      0 *.sunrpc               *.*                    LISTEN
tcp6       0      0 *.sunrpc               *.*                    LISTEN
tcp4       0      0 *.x11                  *.*                    LISTEN
udp4       0      0 *.26924                *.*
udp4       0      0 *.mdns                 *.*
udp4       0      0 *.15589                *.*
udp4       0      0 239.255.255.250.3702   *.*
udp4       0      0 localhost.ntp          *.*
udp6       0      0 fe80::1%lo0.ntp        *.*
udp6       0      0 localhost.ntp          *.*
udp4       0      0 192.168.1.100.ntp      *.*
udp4       0      0 *.ntp                  *.*
udp6       0      0 *.ntp                  *.*
udp4       0      0 *.984                  *.*
udp6       0      0 *.684                  *.*
udp6       0      0 *.951                  *.*
udp4       0      0 *.*                    *.*
udp4       0      0 *.elcsd                *.*
udp6       0      0 *.704                  *.*
udp4       0      0 *.826                  *.*
udp6       0      0 *.826                  *.*
udp6       0      0 *.*                    *.*
udp4       0      0 *.745                  *.*
udp4       0      0 *.sunrpc               *.*
udp6       0      0 *.616                  *.*
udp6       0      0 *.sunrpc               *.*
udp4       0      0 localhost.1031         *.*

NugentS · Apr 11, 2022

@danb35 wrote an automated plex installer that I used to build my plex jail (I also have a plex pass). It works. It was designed for 11.2/11.3 but worked on the 12.x that I was running when I installed the Jail.

It takes a config file and just installs Plex. I seem to recall having to play with the config file a bit, different options - but it didn't take long

truenasjw · Apr 11, 2022

NugentS said:
@danb35 wrote an automated plex installer that I used to build my plex jail (I also have a plex pass). It works. It was designed for 11.2/11.3 but worked on the 12.x that I was running when I installed the Jail.

It takes a config file and just installs Plex. I seem to recall having to play with the config file a bit, different options - but it didn't take long

If I try to go the Plex Plugin route route, here is what happens:

Code:

Official Plugin verified_user
Version: 1.25.6.5577
Installed Instances: 0

Plugin Name = plexmediaserver
Jail Name = plexplugin
(checked) DHCP
(unchecked) NAT

SAVE

Install
50.00% - ffmpeg

It sits there for about 1min and then I lose the TrueNAS web interface. It says it is "Connnecting" and then the TrueNAS login appears and I have to relogin. I go to jails and only the first time did I see a URL under Admin Portals. Now it is a 50/50 everytime that the plugin won't have even installed and other times the Plex plugin is there but the Admin Portal is blank. If I expand the plugin, this is what I see:

Code:

IPv4 Address:192.168.5.235
IPv6 Address:N/A
Version:1.25.6.5577
Plugin:plexmediaserver
Release:12.2-RELEASE-p15
Collection:
https://github.com/freenas/iocage-ix-plugins.git

If I try and reach plex (http://192.168.5.235:32400/web or https://192.168.5.235:32400/web)... it is the same problem as I have with the manual instances... the browser times out and I never reach the Plex web interface. If I try from the TrueNAS shell... I can wget the Plex web html just from http://192.168.5.235:32400/web . Something is preventing me from reaching the Virtual IP's of the Jails from the LAN.

truenasjw · Apr 13, 2022

48hr bump

winnielinnie · Apr 13, 2022

You can ping the Plex jail's IP address from your desktop PC?

truenasjw · Apr 13, 2022

winnielinnie said:
You can ping the Plex jail's IP address from your desktop PC?

Seriously... WTF! I started the Jail up and trying to gather the information requested I was able to now ping the Plex Jail from the desktop. So I went ahead and tried the web interface on a whim and it came back with the Plex web interface. Thank you, I guess????

winnielinnie · Apr 13, 2022

Check your Plex server's network and security options. It's not as intuitive as you would assume. (Plex server options; not the jail options.)

Patrick M. Hausen · Apr 13, 2022

truenasjw said:
Just a thought, do I need to do anything within TrueNAS | Network | Interfaces | Add ? Do *I* have to manually configure a Bridge Interface to allow systems on the LAN to know that the .101 (Plex Jail) is behind .100 (TrueNAS)?

You should, because the FreeBSD documentation explicitly states that you must not have an IP address on a bridge member interface (igb0 in your case). The IP address must be on the bridge0 interface. The only way to achieve that is to manually create and configure the bridge0 IF.

If you can bear a reboot, the best method is to set all jails' autostart to "off" and reboot the system. It will then come up without a bridge, so you can create one in the network settings. The bridge must have igb0 as the member interface and igb0 must have hardware offloading disabled and "up" in the options field. IP address assigned to bridge0, not igb0.

HTH,
Patrick

truenasjw · Apr 13, 2022

Ok, now I am just dumbfounded. So I couldn't access Plex after I stopped it to add mount points and restarted. After some playing around here is what works... cannot explain why... but I have confirmed by reproducing the problem/solution multiple times:

I have two jails, one is a manual install called Plex that I have been referencing this entire time. In an attempt to troubleshoot, I had TrueNAS Plugins create a Plex Plugin jail called Plexplugin.

DOES NOT WORK:
STOP > Plex (Jail)
STOP > Plexplugin (Jail)
START > Plex (Jail)

Desktop can ping TrueNAS but cannot ping Plex (Jail)
TrueNAS can ping Plex (Jail) but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)
Plex (Jail) can ping TreuNAS but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)

DOES NOT WORK:
STOP > Plex (Jail)
STOP > Plexplugin (Jail)
START > Plex (Jail)
START > Plexplugin (Jail)

Desktop can ping TrueNAS but cannot ping Plex (Jail)
TrueNAS can ping Plex (Jail) but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)
Plex (Jail) can ping TreuNAS but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)

DOES WORK:
STOP > Plex (Jail)
STOP > Plexplugin (Jail)
START > Plexplugin (Jail)
START > Plex (Jail)

Desktop can ping TrueNAS and can ping Plex (Jail)
TrueNAS can ping Plex (Jail) but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)
Plex (Jail) can ping TreuNAS but cannot ping Desktop (this is normal Windows Firewall behavior so not concerned by)

There is absolutely no reason for this behavior and to repeat I tried different orders numerous times to ensure that I wasn't misinterpreting the results.

Here is the Plexplugin (Jail) settings so to prove that I am not connecting somehow to it instead of the Plex (Jail) (plus I do NOT have any mapped mount points configured in the plugin... so I 100% certain).

Code:

Boot:on
IPv4:192.168.5.235
IPv6:none
Type:pluginv2
Template:0
Basejail:yes

So I guess my problem is solved? I mean, it is not solved, but at least resolved.

faktorqm · Jul 4, 2022

Same problem here. Please see my post. Do you have it working now?

Important Announcement for the TrueNAS Community.

TrueNAS 12.0 U8 - Trying to Install Plex Manually & Having Network Issues

Dabbler

Dabbler

Dabbler

Dabbler

Resident Grinch

Dabbler

Dabbler

Dabbler

MVP

Dabbler

IPv4 Address:​

IPv6 Address:​

Version:​

Plugin:​

Release:​

Collection:​

Dabbler

MVP

Dabbler

MVP

Hall of Famer

Dabbler

Dabbler

Similar threads

IPv4 Address:

IPv6 Address:

Version:

Plugin:

Release:

Collection: