itskando
Contributor
- Joined
- Apr 30, 2018
- Messages
- 172
I was just able to fix it
Thank you for sharing your solution - could be helpful for the next guy : j
I was just able to fix it
Definitely! I figured out most of it between google and scouring this and plex forums. Unfortunately, nobody at Plex was willing to help until after I figured it out and 2 days later.
it starts with a “ and should be a "
I'm trying to get Plex to work properly and my situation seems to be similar to what you described in this thread.
Plex doesn't find metadata.
Transcoding doesn't work.
I tried going to Jails->Edit and add:
IPv4 Default route: <Set to the IP of my router>
VNET: on
Berkelet Packet Filter: on
auto-start: on (I think this corresponds to "boot: on")
But after doing so I can't access plex at all. That is, when entering the Plex IP in my web browser it just hangs there and nothing happens.
I was wondering if this could be some router setting that needs to be set, now that I have "included it" by giving its IP to the Plex jail.
The only thing I have done in the router is to change the DHCP setting so that its range is outside the IP range I'm planning to use for the NAS. DHCP starts at 192.168.0.100, while the Plex jail has the IP 192.168.0.52. The NAS has a static IP in the router, but I have not "told" the router in any way about the Plex jail's IP. Do I need to do this? I'm not sure how I would go about it since the jail doesn't have a MAC address? (or?)
I'm just throwing questions at you now, but anything you know is greatly appreciated!
I will add anything I learn to the thread you made, it seems odd to me that the Plex plugin doesn't have some official "these things you absolutely have to do to make it work"-list!
Router (IPv4 Default Route) IP: 192.168.86.001 Router DHCP-Reserved IPs: 192.168.86.021 - 192.168.86.200 IPMI IP: 192.168.86.002 freeNAS OS IP: 192.168.86.003 (If you ) Plex Jail IP: 192.168.86.010
iocage get all <plexJailName>
,<plexJailName>
is the name of your Plex jail.iocage set ip4_addr="vnet0|172.16.1.250/24"
iocage stop plex iocage set ip4_addr="vnet0|192.168.86.10/24" vnet="on" boot="on" allow_raw_sockets="1" defaultrouter="192.168.86.1" plex
Nevermind that, I eventually figured it out: when VNET is disabled, and even if assign_localhost is enabled, the Plex Transcoder will not work because, from what I can guess:
1) The transcoder probably tries to establish a connection to 127.0.0.1 (instead of "localhost"), which is looped back to the main jail IP (AIUI reading on the operation of FreeBSD jails, which I understand very little about): I noticed that all connections where happening within the jail over the LAN IP and that the loopback address was completely unused; and
2) The transcoder doesn't seem to authenticate with the PMS, which by default probably only allows unauth connections on 127.0.0.1
If I get all that right, the net result is that because the PMS sees an incoming unauthenticated connection over the LAN IP instead of the loopback device it denies it, thus the transcoder cannot access the media and so the transcoding fails and the player ends up with nothing to play (meanwhile, CPU spikes on the server while all this happens and cryptic messages are left in the logs).
The solution is very simple, and it might serve others so here it is: simply allow the LAN network in the unauthenticated Networks PMS preferences (either in the preference file: "allowedNetworks", or via the web configuration, section "Network"), and voilà: Plex installed in a jail without VNET, and transcode works.