I have pihole running on an ESXi VM and it's running fine but my config tells me it has one IP (10.0.0.8 ) under the admin UI settings. But I can not bring up the web ui with that IP address. If i log into the console and run ifconfig I get eth0 having a 10.0.0.181 address and the web ui DOES come up there.
Not sure where it's getting this but somehow it seem that DHCP is on and over riding the settings part.
I'm sorry when I looked at my notes I took the two address from the old network. I forgot that I moved pi-hole to the 192. (I need more sleep) when I run the sudo ip addr I get this:
Ok so I ran the install again and it did default to the 192.168.7.181 IP again, I changed it to the 192.168.7.8 ip and now when I got to the 192.168.7.8 I get this:
Website Blocked
Access to the following site has been blocked:
192.168.7.8
If you have an ongoing use for this website, please ask the owner of the Pi-hole in your network to have it whitelisted.
This page is blocked because it is explicitly contained within the following block list(s):
Go back Whitelist this page Close window
Generated Sat 12:11 PM, Feb 04 by Pi-hole v2.12.1
BUT when I go to my blacklist I get that it's empty.
I meant when I visited the 192.168.7.8/admin I got that. I just gave up and nuked the VM and did a fresh install of minimal debian and reinstalled. Up and running now.
not exactly sure whats going on but if you shutdown the ESXi 6.5 VM that is running pi-hole and restart it it stops using the static IP that is assigned during install. It grabs a DHCP IP and from then on you can't access the admin UI unless you go to the new DHCP address. Is there a setting that can turn off DHCP?
I did it again just to be sure, I go through all the steps (it defaults to the .220 address here) change it to the one I want (.5) and it still wants to be on .220. Reboot and still the same (ifconfig shows eth0 as .220). WebUI doesn't respond to the .5/admin but does to the .220/admin.
I have no idea WTF is going on BUT I did notice that it wasn't a reboot of the VM it's whenever Pi-Hole gets updated that it jacks things up.
EDIT: Just tried it again, restored the image I took of the VM prior to the upgrade, rebooted vm twice and it held the settings. Upgrade and it's fine until you restart the VM then even if you tell it to use a specific IP it keeps grabbing it from DHCP. For now I just entered a static in the DHCP server.