Warning: Potential Security Risk Ahead
Firefox detected a potential security threat and did not continue to 192.168.0.2
Which is new.
The .54 was what it was connected to and working perfectly fine on until 20 minutes before I posted.
And I'm not sure? I remember I had some trouble setting everything up when I got it at the start of September 2025, because my router (Virgin Media Hub 3.0) didn't have some of the settings the guide said it should, so I pieced things together from a few different guides till it worked.
that firefox warning on 192.168.0.2 is normal once you hit the https admin after the ip changed. pi-hole is using its own cert, so firefox yells.
click Advanced, then Accept the Risk and Continue (wording varies). or force http://192.168.0.2/admin for a quick check.
.54 dying after the update usually means the pi grabbed a new dhcp lease (.2). set a dhcp reservation for the pi on .2 (or whatever you want) in the virgin hub, and pick one dhcp server. running both the hub dhcp and pi-hole dhcp at once is a common way the admin ip keeps moving.
Pushing through firefox got the admin page back, thank you!!
But when I turned off the DHCP in my router the internet died and I lost the admin page again. So I'm guessing I've set something up wrong somewhere??
Pi says the router is .1, and it's giving out everything from .3 -> .254 to everything else
And the router has .2 reserved for the pi's MAC, but also "starting local address" is .2
What do I turn off to still have everything go through the pihole before it gets to me?
And my wifi isn't back yet. Is there something I need to change to fix that?
I really appreciate your help and your patience, I haven't done anything with this since I set it up last year so whatever I learned about all this back then has faded
yeah if you kill hub dhcp before pi-hole dhcp is actually serving leases, every client goes dark. thats what you hit.
for virgin hub 3 + pi-hole the usual working setup is:
leave hub dhcp ON for a minute
in pi-hole Settings, DHCP, enable the dhcp server, range .3-.254 is fine, router/gateway = 192.168.0.1
keep the .2 reservation for the pi mac
THEN disable dhcp on the hub
reboot phones/pcs (or renew lease) so they grab a lease from the pi
also point hub dns at 192.168.0.2 if the hub has a dns field, or just let clients take dns from the pi via dhcp. do not leave both dhcp servers fighting.
if wifi is still dead after that, turn hub dhcp back on temporarily so you can reach the admin again, then redo the order above. the hub "starting local address .2" while .2 is reserved for the pi is messy. once the pi owns dhcp, hub dhcp should stay off.
if you paste a screenshot of pi-hole dhcp settings (range + gateway) we can sanity check it.
I double checked everything was like you said, turned off hub DHCP and restarted my pc and now it can't find the router at all. Windows network diagnostics says
Ethernet 4 doesn't have a valid IP configuration
Guessing I need to factory reset the hub and start from scratch?
Settings->Network & Internet->Ethernet->edit IP assignment
And I tried putting 192.168.0.4 as the IPv4/6 (not at the same time, tried one then the other) and it says it can't save the settings? Do I need to do anything else?
I am really out of my depth here, I only got the pi so I'd stop seeing temu and shien ads and pop ups in mobile games, so I'm sorry if I'm missing something really obvious with all this
dont factory reset yet. first turn hub dhcp back on so the lan breathes again, then set a static on the pc so you can reach the hub + pi while you sort dhcp.
windows Settings "cant save" is usually the subnet field. it wants Prefix length, not 255.255.255.0. use:
IP: 192.168.0.4
Subnet prefix length: 24
Gateway: 192.168.0.1
Preferred DNS: 192.168.0.2 (or .1 for now)
if Settings still refuses, use the old dialog: Control Panel → Network and Sharing Center → Change adapter settings → Ethernet → Properties → Internet Protocol Version 4 → Use the following address. same numbers, subnet mask 255.255.255.0 works there.
once you can hit http://192.168.0.1 and http://192.168.0.2/admin again: leave hub dhcp ON, confirm pi-hole dhcp is enabled with gateway 192.168.0.1 and range .3-.254, THEN disable hub dhcp, then reboot the pc (or set it back to DHCP) so it leases from the pi. if that still kills the lan, leave hub dhcp on and only point dns at the pi. you do not need pi-hole dhcp just to block ads.
Control panel method got me the hub and pi/admin back thank you!!!
But i now don't have lan on my pc
Just to check before I turn router DHCP off again, pi should look like this?
Did you configured a static IP on the Raspberry Pi OS before disabling the router DHCP server?
When you disable the router DHCP server, the Raspberry Pi will loose its DHCP lease and it will loose the IP. You need to set an IP directly on the Raspberry Pi OS before that.
your pi dhcp screenshot (gateway .1, range .3-.254) is the right shape. leave hub dhcp ON until that pi static sticks, THEN disable hub dhcp and renew the pc lease (or set the pc back to dhcp).
if you just want ads blocked and less pain: leave hub dhcp on forever, point hub dns (or each device dns) at 192.168.0.2, and turn pi-hole dhcp OFF. that skips this whole dance.
Not sure if I got the last one right as i dont have a Netplan system:
$ apt-file list netplan.io | grep service
netplan.io: /usr/share/dbus-1/system-services/io.netplan.Netplan.service
FYI:
$ apt show netplan.io
[..]
Description: YAML network configuration abstraction for various backends
netplan reads YAML network configuration files which are written
by administrators, installers, cloud image instantiations, or other OS
deployments. During early boot it then generates backend specific
configuration files in /run to hand off control of devices to a particular
networking daemon.
.
Currently supported backends are networkd and NetworkManager.
