Accidentally installed apache24 in freenas console

[sretalla]

I see VNET is off on the jail... perhaps that's one way to start looking at it and see if we can get it to work with VNET on.

this line
ip4_addr:mynetworkinterface|jailip/24
should be
ip4_addr:vnet0|jailip/24

I suppose you're substituting those "variables" (jailip and mynetworkinterface) in your actual setup or nextcloud would never work.

Otherwise, you can try under System | General | WebGUI IPv4 Address setting it to only the host IP (I suppose currently it shows 0.0.0.0).


Just to keep up our sleeves for later if we need it:
ifconfig re0 inet 192.168.2.134 netmask 0xffffff00 delete

 

[twsps]

I see VNET is off on the jail... perhaps that's one way to start looking at it and see if we can get it to work with VNET on.

this line
ip4_addr:mynetworkinterface|jailip/24
should be
ip4_addr:vnet0|jailip/24

I suppose you're substituting those "variables" (jailip and mynetworkinterface) in your actual setup or nextcloud would never work.

Otherwise, you can try under System | General | WebGUI IPv4 Address setting it to only the host IP (I suppose currently it shows 0.0.0.0).


Just to keep up our sleeves for later if we need it:
ifconfig re0 inet 192.168.2.134 netmask 0xffffff00 delete

Yes, I replaced those values instead of my real network interface. So I was able to get vnet on the first time with nextcloud working. However, after rebooting FreeNAS, I'm not able to get in nextcloud either by jail IP or mydomain.com
My first set up was vnet0|192.168.2.134.
Could it be possible that my other jails are enabled and using vnet that causes it not working?

Sent from my Mate 9 using Tapatalk

 

[sretalla]

Let's have another look at ifconfig on the host with the jail running.

If you try the command where I first suggested ifconfig to try, then if that works, we can make it permanent.

 

[twsps]

Let's have another look at ifconfig on the host with the jail running.
If you try the command where I first suggested ifconfig to try, then if that works, we can make it permanent.

Sorry for the delay, I have another jail running on vnet which is openvpn, so it could be the reason it might not work on vnet? Also, after a few days of not restarting freeNAS, I will be able to access freenas webgui with freenas.local.
With the code you suggested above, should I still use vnet0 if I have another jail running on vnet (openVPN on old jail system, not iocage)?

 

[sretalla]

You can run as many jails on a vnet as you need to. If what you're doing with the VPN might interfere with other jails (but it probably isn't the case) you can use another vnet for the rest of your jails.

I think your problem speaks to an issue with registering the name to the wrong IP address and I guess FreeNAS has a recurring check to re-register (perhaps explains what you see after a day).

 

[twsps]

You can run as many jails on a vnet as you need to. If what you're doing with the VPN might interfere with other jails (but it probably isn't the case) you can use another vnet for the rest of your jails.

I think your problem speaks to an issue with registering the name to the wrong IP address and I guess FreeNAS has a recurring check to re-register (perhaps explains what you see after a day).

I believe so, right now I can see two IPs on my router, one is my freeNAS IP (e.g. 192.168.2.76). FreeNAS got confused and I might need to remove 192.168.2.76 shown on my re0 (which is my network card).
I'm afraid of changing the jail into vnet will destroy my jail. If I don't choose to use vnet for my jail, is it correct that its IP will be shown in re0?