FreeNAS PLEX Jail DVR(Beta) Cannot Discover HDHR

[daddygoofball]

FreeNAS
Build FreeNAS-9.10.2-U3 (e1497f269)
Platform AMD A4-5300 APU with Radeon(tm) HD Graphics
Memory 7334MB
System Time Thu Apr 27 01:18:21 EDT 2017
Uptime 1:18AM up 4 days, 15:27, 0 users
Load Average 0.12, 0.20, 0.32

Plex Jail
Reinstalled to a new jail after updating FreeNAS from 9.3 to 9.10
Plex plugin version 1.5.5.3634

Silicone Dust HD Home Run Devices
HDHR Dual HDHR-US FW 20161117
HDHR Dual HDHR3-US FW 20161117

Network.
LAN:192.168.1.0/24
Plex and HDHRs are physically connected to the same switch

Issue
Cannot discover HDHR devices from the Plex DVR Beta feature inside the Plex jail.

Steps..
Testing network and HDHR HW
-Installed Plex on a windows 10 laptop connected wirelessly and ran the discover feature. It immediately Auto discovered both HDHR devices.
From the same laptop I am able to watch live TV through the HDHR installable application.

Attempted discovery through Plex Jail. Will not discover.
Attempted specifying IP will not discover
Attempted to specify IP and port will not discover.
Can ping the HDHR Devices from the Jail console.

Please let me know what logs you need for troubleshooting. Looking for direction.

 

[dlavigne]

Were you able to resolve this?

 

[daddygoofball]

Thank you for responding.
Unfortunately no I have not been able to resolve this.

I have since deleted the plugin and jail and reinstalled PMS and still get the same results. You can see in the following PMS logs that a connection is made but I am wondering if we are dealing with a PMS bug or something with the jail.

Searching in the Plex forums I see that other FreeNAS users are successfully connecting to HDHR devices but I have not seen anyone identify the FreeNAS version or HDHR hardware version they are working with.

I also have a thread going on the Plex Forums for this issue.

http://forums.plex.tv/discussion/268417/freenas-dvr-beta-cannot-discover-hdhr#latest

It would be helpful to isolate the issue to either a FreeNAS or a PMS issue.

In version 1.5.2 there was a fix for this issue.
https://forums.plex.tv/discussion/62832/plex-media-server#latest

Code:

Apr 27, 2017 16:45:56.434 [0x809c0e400] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.																																 
Apr 27, 2017 16:45:56.434 [0x809c0e400] DEBUG - Auth: authenticated user 1 as DaddyGoofball										 
Apr 27, 2017 16:45:56.434 [0x809c0e400] DEBUG - Auth: Came in with a super-token, authorization succeeded.						 
Apr 27, 2017 16:45:56.435 [0x809c15c00] DEBUG - Request: [XXX.XX.XX.XXX:9339 (WAN)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/
devices?uri=192.168.1.56 (3 live) TLS GZIP Signed-in Token (DaddyGoofball)														 
Apr 27, 2017 16:45:56.435 [0x809c15c00] DEBUG - MediaGrabber: Checking device URI http://192.168.1.56							   
Apr 27, 2017 16:45:56.435 [0x809c15c00] DEBUG - HTTP requesting GET http://192.168.1.56/discover.json							   
Apr 27, 2017 16:45:56.545 [0x809c15c00] DEBUG - HTTP 200 response from GET http://192.168.1.56/discover.json						
Apr 27, 2017 16:45:56.546 [0x809c15c00] DEBUG - HTTP requesting GET http://192.168.1.56/capability								 
Apr 27, 2017 16:45:56.650 [0x809c15c00] DEBUG - HTTP 404 response from GET http://192.168.1.56/capability						   
Apr 27, 2017 16:45:56.651 [0x809c15c00] DEBUG - HTTP requesting GET http://127.0.0.1:32600/devices/								 
Apr 27, 2017 16:45:56.651 [0x809c15c00] ERROR - Error issuing curl_easy_perform(handle): 7										 
Apr 27, 2017 16:45:56.651 [0x809c15c00] WARN - HTTP error requesting GET http://127.0.0.1:32600/devices/ (0, No error) (Failed connect to 127.0.0.1:32600; Connection refused)																						 
Apr 27, 2017 16:45:56.651 [0x809c15c00] ERROR - Error parsing content.															 
Apr 27, 2017 16:45:56.651 [0x809c15c00] ERROR - Error parsing XML.																 
Apr 27, 2017 16:45:56.651 [0x809c15c00] ERROR - MediaGrabber: Error obtaining device status.										
Apr 27, 2017 16:45:56.652 [0x809c0e400] DEBUG - Completed: [XXX.XX.XX.XXX:9339] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/
devices?uri=192.168.1.56 (3 live) TLS GZIP 217ms 452 bytes (pipelined: 1)														   
Apr 27, 2017 16:46:25.798 [0x809c0e000] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.											 

 

[HardDrv00]

I had no issues with my PMS beta and HDHR Connect. I can get more details when I am back at home, but I am on FN 9.10.2 u1 and the latest Plex beta. I don't recall off-hand what version my jail is.

Sent from my XT1254 using Tapatalk
Edit: corrected FN version

 

[daddygoofball]

If you could help me validate the jail version or some commands that I could run to check the health of the jail itself that would he helpful also. In my experience its the overlooked details that usually become the culprit.

My evening is booked solid I may not be able to respond until tomorrow or Saturday but I can VPN back to the house and run some commands and get more data.

Thanks again

 

[HardDrv00]

I am actually running FreeNAS 9.10.2-U1 (86c7ef5) on
Supermicro X10SL7-F
Xeon E3-1231 v3
32GB DDR3L ECC 1600

Plex Media Server v1.5.5.3634 performing DVR with,

HDHomeRun CONNECT, Model: HDHR4-2US, Firmware 20161117, same subnet, both connected to same L2 switch

The Plex jail was originally installed from a Plugin, plexmediaserver-0.9.14.6.1620-amd64. This plugin version I think dates to my initial install of FreeNAS 9.3. Within the jail, executing the following commands shows the jail wasn't updated. The userland/jail is 9.03, the kernel/host is 10.03:

Code:

root@plexmediaserver_1:/ # uname -U
903000
root@plexmediaserver_1:/ # uname -K
1003510

The PMS was updated to PlexPass version with the script here, https://forums.plex.tv/discussion/1...e-freenas-plex-plugin-pbi-to-plexpass-version linked by Plex Forum TurboJailer. (maybe FreeNAS Forums @Jailer, unconfirmed).

My jail configuration:

• IP and mask are set
• Sysctls: allow.raw_sockets=true
• autostart: checked
• VIMAGE: checked
• NAT: unchecked

I would add the sysctls item if you don't have it. If you already have VIMAGE checked you can uncheck and test; and re-check as I've seen forum posts that mentioned the behavior is inconsistent. The User Guide, section 13 Jails Configuration states:

VIMAGE gives a jail its own virtualized network stack; requires promiscuous mode be enabled on the interface

I'm not sure how promiscuous mode is set on the 'host' Ethernet interface, but it appears mine is set for igb0. Running
ifconfig on the host:

Code:

[root@NAS01] ~# ifconfig
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
  ether xx:xx:xx:xx:xx:xx
  inet 192.168.0.120 netmask 0xffffff00 broadcast 192.168.0.255
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet autoselect (1000baseT <full-duplex>)
  status: active
igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
  ether 0c:c4:7a:6c:13:0d
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet autoselect
  status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
  options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
  inet 127.0.0.1 netmask 0xff000000
  nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
mlxen0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=ed07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
  ether xx:xx:xx:xx:xx:xx
  inet 192.168.10.120 netmask 0xffffff00 broadcast 192.168.10.255
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
  status: active
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
  ether 02:96:fd:6f:bc:00
  nd6 options=1<PERFORMNUD>
  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
  member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 7 priority 128 path cost 2000
  member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 8 priority 128 path cost 2000
  member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 6 priority 128 path cost 2000
  member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:ff:20:00:06:0a
  nd6 options=1<PERFORMNUD>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:ff:20:00:08:0a
  nd6 options=1<PERFORMNUD>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:ff:20:00:07:0a
  nd6 options=1<PERFORMNUD>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
[root@NAS01] ~#

And the jail interface for reference, epair0b:

Code:

root@plexmediaserver_1:/ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
  options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
  inet 127.0.0.1 netmask 0xff000000
  nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:65:2b:00:0a:0b
  inet 192.168.0.201 netmask 0xffffff00 broadcast 192.168.0.255
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
root@plexmediaserver_1:/ #

 

[Jailer]

(maybe FreeNAS Forums @Jailer, unconfirmed).

The same. Jailer was taken over there when I created my account so TurboJailer is my fallback alias.

 

[daddygoofball]

Code:

root@plexmediaserver_1:/ # uname -U
903000
root@plexmediaserver_1:/ # uname -K
1003510

My Jail settings matched what you described above but my Jail version did not.

Code:

root@plexmediaserver_1:/ # uname -K
1003510
root@plexmediaserver_1:/ # uname -U
1003000

I decided to update my Jails
After running the following commands...

Code:

pkg update
pkg upgrade

The versions still remained the same but a whole bunch of packages updated.

My PMS still did not discover HDHR Devices on my network.

 

[daddygoofball]

The PMS was updated to PlexPass version with the script here, https://forums.plex.tv/discussion/1...e-freenas-plex-plugin-pbi-to-plexpass-version linked by Plex Forum TurboJailer. (maybe FreeNAS Forums @Jailer, unconfirmed).

I followed the guide you linked above and it lead me to the solution.

I followed the steps in the guide passing the -a option to auto update to the newer version. This did not work.

Code:

root@plexmediaserver_1:/ # ./PMS_Updater.sh -h
Illegal option -h
usage: ./PMS_Updater.sh options

This script will search the plex.tv download site for a download link
and if it is newer than the currently installed version the script will
download and optionaly install the new version.

OPTIONS:
   -u	  PlexPass username
			 If -u is specified without -p then the script will
			 prompt the user to enter the password when needed
   -p	  PlexPass password
   -c	  PlexPass user/password file
			 When wget is run with username and password on the
			 command line, that information is displayed in the
			 process list for all to see.  A more secure method
			 is to create a file readable only by root that is
			 formatted like this:
			   user={Your Username Here}
			   password={Your Password Here}
   -l	  Local file to install instead of latest from Plex.tv
   -d	  download folder (default /tmp) Ignored if -l is used
   -a	  Auto Update to newer version
   -f	  Force Update even if version is not newer
   -r	  Remove update packages older than current version
			 Done before any update actions are taken.
   -v	  Verbose
   -n	  Use normal version (not PlexPass) version
root@plexmediaserver_1:/ #

I ran the same command with a -f to force the update even if the version is not newer.
And now both my devices discovered scanned and the guide is currently downloading.

SOLUTION

Code:

./PMS_Updater.sh -u PLEX_USER -p PLEX_PASSWORD -a -f

Thank you so much for your time and help.

 

[HardDrv00]

I would look into the networking settings because the broadcasts from the HDHR are not reaching PMS. Do you have VIMAGE or the allow raw sockets option? What happens if you manually give PMS the device IPs?

Sent from my XT1254 using Tapatalk

 

[HardDrv00]

Glad you found a solution, sounds like it was a PMS issue.

Sent from my XT1254 using Tapatalk