Aaron Siemieniec
Dabbler
- Joined
- Apr 13, 2015
- Messages
- 23
Pushed off redoing all my jails that were created and accessible via the "legacy" interface (v10?). FreeNAS is now on v11.3-U1 and figured it's time to re-do it all, start clean and fresh.
I used to be able to access a plugin, say SAB or Sonarr, etc, via the jail's IP and port 80. I don't like having to always enter port 8989 when going to Sonarr, same for the other plugins. Now in v11.3-U1 with iocage, the only way within the UI of FreeNAS to alter the NAT port forwarding is if I have NAT enabled, DHCP disabled. But I don't want my jails with the same IP as the FreeNAS box. Each jail gets it's IP via DHCP from my Windows server. I could even do with specifying an IP within the jail config but I still can't get the NAT port forwarding to show the text box unless I have NAT enabled in the jail config.
There has to be a conf file somewhere that allows me to change the default ports from whatever they are to 80 for each plugin and still allow me to use DHCP or a static IP.
Ideas where that file is or what file to create?
Thanks
I used to be able to access a plugin, say SAB or Sonarr, etc, via the jail's IP and port 80. I don't like having to always enter port 8989 when going to Sonarr, same for the other plugins. Now in v11.3-U1 with iocage, the only way within the UI of FreeNAS to alter the NAT port forwarding is if I have NAT enabled, DHCP disabled. But I don't want my jails with the same IP as the FreeNAS box. Each jail gets it's IP via DHCP from my Windows server. I could even do with specifying an IP within the jail config but I still can't get the NAT port forwarding to show the text box unless I have NAT enabled in the jail config.
There has to be a conf file somewhere that allows me to change the default ports from whatever they are to 80 for each plugin and still allow me to use DHCP or a static IP.
Ideas where that file is or what file to create?
Thanks