VM web-ui breaking TrueNas web-ui on separate interface and IP.

[phebert]

I'm running a fresh VM of PiHole and somehow the PiHole web-ui is responding on the TrueNAS web-ui IP address, breaking access to TrueNas. I can fix the issue by changing the web-ui ports on each, but I'm concerned as to why they are crossing over despite me telling it what to use.

PiHole
guest static IP: 192.168.44.2/24
vm nic interface em1

TrueNas
web interface ipv4 listen on 192.168.44.40/24 ports 80, 443
em0 - static 192.168.44.40/24
em1 - none, no-dhcp

 

[sretalla]

Under System | General, do you have 0.0.0.0 under the "Web Interface IPv4 Address"? (just confirming even though you said it)

 

[phebert]

nope, as specified : web interface ipv4 listen on 192.168.44.40/24 ports 80, 443

 

[sretalla]

How about the HTTP to HTTPS redirect?

 

[phebert]

 

[sretalla]

Just a guess, but maybe when the HTTP to HTTPS redirect was set, you still had 0.0.0.0 as the address, so it's still in a config file somewhere (and if this guess is right, there's a bug in the code when you change the IPv4 address, which should re-do the HTTP to HTTPS redirect again on a change).

Perhaps try un-setting it, save and re-set and save...

 

[phebert]

1. VM Off
2. Disabled redirect in TrueNas
3. Restarted TrueNas webui
4. VM On
5. Was working for a few minutes, then same issue

VM on.

• http://192.168.44.40:80 goes to the VM
• http://192.168.44.2:80 goes to the VM

VM off

• http://192.168.44.40:80 goes to TrueNas
• http://192.168.44.2:80 no ping.

Edit: for clarity on the VM guest side: The guest is set to listen on 0.0.0.0 I believe. However that shouldn't be an issue since the VM NIC is assigned to a completely different interface. Im about to reinstall the entire core. There's no real data on the drives and its not a production. Just would prefer to find the culprit of the issue, for learning ya know.