As I said, this is a network issue. Pi-hole is working as expected.
You need to find out why your connection works just for a while and then fails.
Typically this indicates a problem with IP addressing and using DHCP in addition to static IP. When you get the error can you run arp -a and then run that same command when you are able to access the web interface. We're looking to see if the MAC addresses are the same or if they are different.
If they are different then you probably have a DHCP server that is handing out 192.168.50.246 to some other network client.
Yeah my router is handing out 192.168.50.125 but I also manually assigned the ip to the pi hole in my router DHCP settings.
So do I disabled DHCP on my router but doesn't it make my network vulnerable.
DHCP really doesn't have anything to do with network security. You need a DHCP server unless you manually configure each network client to have a static IP.
Your DHCP server settings should have a place to say how big a pool of addresses you want to hand out. Just make sure that the Pi-hole's IP address is not in that range so that it's IP address will not be a part of the pool to be handed out. And make sure the Pi-hole's IP address is set manually and static.
But I can't set the pihole’s up outside of the DHCP pool
The debug log shows a different information.
Your router offered 192.168.50.246...
* Received 300 bytes from 192.168.50.1 @ wlan0
Offered IP address: 192.168.50.246
Server IP address: 192.168.50.1
... and this is the IP actually shown on your debug log:
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether <REDACTED> brd ff:ff:ff:ff:ff:ff
inet 192.168.50.246/24 brd 192.168.50.255 scope global dynamic noprefixroute wlan0
Maybe the address was changed after the debug log was generated.
Why not?
Idk it showed the ip address is not valid. My ip address pool is from xxx.xxx.xx.2 to xxx.xxx.xx.254. so when I put the pi holes ip to .255 or more then that it says ip address is not valid
Yeah my router offered.246 when it restarted and I was able to connect to it but after like 1 or 2 minutes my router offers different ip address from the DHCP pool
This is expected.
IP addresses contain 4 numbers from 0 up to 255, separated by dots.
You can't use numbers above 255, never. Addresses ending with .0 cannot be used here.
Also, the last address on every subnet range (192.168.50.255 in your specif case) is called "broadcast address" and it is reserved - you can't use that.
You can change the DHCP range on your router to something different (example: 192.168.50.50-192.168.50.254) and set a static IP to Pi-hole (example: 192.168.50.40).
That's why you need a static IP, so it will never change.
Ok I'll try that
Didn't work. I put pihole to .31 and my router DHCP on .50 to .254 but I still can't access the web ui
I give up. I tried everything. I asked claude, Gemini, chatgpt. Tried everything I could. I'm gonna use the raspberry pi for something else. And for DNS I'm using control d server
A post was split to a new topic: Unrelated to Pi-hole
A post was merged into an existing topic: Unrelated to Pi-hole
I had similar web UI access issues when running Pi-hole on my off-grid setup. Turned out to be a power stability issue - my Raspberry Pi was browning out during low voltage moments. Ended up upgrading my solar panels and adding a dedicated DC-DC converter to give the Pi stable 5V even when battery voltage fluctuates. Rock solid since then. For anyone running Pi-hole off-grid, make sure your power supply can handle voltage sag under load.
1 Like