Short:
Guessing: Freenas is assigning a jail ( vBox ) to the same ip address as the web ui. Once the jails start to load on reboot I can not longer access freenas webui.
What happened?:
-Started off on freenas 11.0 and upgraded to 11.2 ran that for a couple of days and figured it was stable.
-Change my motherboard settings to enable VT-x for docker. and updated IMPI firmware.
-Reboot
-Freenas loads, web ui starts then suddenly becomes unresponsive(pretty much only have time to log in before it doesnt respond)
-Freenas now redirects to my plugin vBox(static ip) under the same ip (freenas ip was dynamic). so it seems to me that the vBox web ui is overwriting the port for the freenas webUI.
Any ideas how I can fix this without a reset to defaults/ deleting the jail?
Guessing: Freenas is assigning a jail ( vBox ) to the same ip address as the web ui. Once the jails start to load on reboot I can not longer access freenas webui.
What happened?:
-Started off on freenas 11.0 and upgraded to 11.2 ran that for a couple of days and figured it was stable.
-Change my motherboard settings to enable VT-x for docker. and updated IMPI firmware.
-Reboot
-Freenas loads, web ui starts then suddenly becomes unresponsive(pretty much only have time to log in before it doesnt respond)
-Freenas now redirects to my plugin vBox(static ip) under the same ip (freenas ip was dynamic). so it seems to me that the vBox web ui is overwriting the port for the freenas webUI.
Any ideas how I can fix this without a reset to defaults/ deleting the jail?
