Hello,
I'm having very similar problem as described in this thread;
www.truenas.com
solution from DrKK:
"Alright. That failure is really ungraceful. We'll need to bug report this somewhere. But in the meantime, let's see if the culprit is DHCP. Can you go into those jail settings, turn the DHCP off, and just try a static IP assignment, see if the jail starts?"
I wanted to add to the message that trying to install the plugin with the DHCP enabled failed. With DHCP disabled, the install fails as well. I installed it using the checkbox for the NAT in the plugin options, the installation works. However network wise without configuring an extra route on my router towards the addresses behind the NAT would require extra router configuration (and enable routing on my NAS if that isn't the case by default), but i think this would have worked as well. (router: 192.168.0.1, desktop and NAS are both in the range 192.168.0.*, but when applying the NAT option, the plugin will be installed and get an IP in the range 172.*.*.*
After I installed the plugin, using the NAT option, the installation passed, but obvious as I didn't reconfigure any routes on my router so i can't reach the address. I tried to manually apply an IP address after the installation and now I have the installation wizard of plex when i try to access the LAN address on the correct port, the "manage" link on the truenas web interface at least is linking to something that is responsive.
Btw, this is also a fresh install of the latest stable version, I didn't keep any configuration files from previous (older) installations.
wkr,
Luk
I'm having very similar problem as described in this thread;
FreeNAS Plex Jail DHCP not working
Hey guys, got this problem when trying to start the FreeNAS Plex Jail on FreeNAS 11.2-RC1 Error: concurrent.futures.process._RemoteTraceback: """ Traceback (most recent call last): File "/usr/local/lib/python3.6/concurrent/futures/process.py", line 175, in _process_worker r =...
![www.truenas.com](https://www.truenas.com/community/data/assets/logo/FORUMSFAVICON.png)
solution from DrKK:
"Alright. That failure is really ungraceful. We'll need to bug report this somewhere. But in the meantime, let's see if the culprit is DHCP. Can you go into those jail settings, turn the DHCP off, and just try a static IP assignment, see if the jail starts?"
I wanted to add to the message that trying to install the plugin with the DHCP enabled failed. With DHCP disabled, the install fails as well. I installed it using the checkbox for the NAT in the plugin options, the installation works. However network wise without configuring an extra route on my router towards the addresses behind the NAT would require extra router configuration (and enable routing on my NAS if that isn't the case by default), but i think this would have worked as well. (router: 192.168.0.1, desktop and NAS are both in the range 192.168.0.*, but when applying the NAT option, the plugin will be installed and get an IP in the range 172.*.*.*
After I installed the plugin, using the NAT option, the installation passed, but obvious as I didn't reconfigure any routes on my router so i can't reach the address. I tried to manually apply an IP address after the installation and now I have the installation wizard of plex when i try to access the LAN address on the correct port, the "manage" link on the truenas web interface at least is linking to something that is responsive.
Btw, this is also a fresh install of the latest stable version, I didn't keep any configuration files from previous (older) installations.
wkr,
Luk