Dear Pi-hole community,
I broke my Pi-hole - here's how.
I ran the recent v6.0.6 update, apparently this completed without issue on a Pi 4.
Now feeling quite good about myself I believed all is right in the world and there's absolutely no reason not to update to Ubuntu mate v24.04.
Since these apparently simple updates I have not been able to access the Pi-hole UI.
I now receive an 'unable to connect' message from the browser.
Was there a README I'm supposed to have read, despite an hour or two of research I can't seem to find any useful guidance.
I'd really appreciate advice for effective troubleshooting, someone to confirm I'm silly for believing.
Thanks in advance.
What URL are you using to access the web interface?
Your log shows the web server is using ports 8080
and 443
:
[✓] tcp:0.0.0.0:443 is in use by pihole-FTL
[✓] tcp:0.0.0.0:8080 is in use by pihole-FTL
[2025-05-05 14:43:44.045 BST 1927] Initializing HTTP server on ports "8080o,443os,[::]:8080o,[::]:443"
Are you able to connect using these links?
1 Like
Yes, that did it. Uncertain why these addresses might have changed.
Is there a recomended read list that would help me make sense of this change?
Should I leave all other devices connecting to the original Pi-hole address or update those devices so they target the .57 new address?
Sincerely appreciated rbwebdesign
If you were running Pi-hole v5 before the update, the default port (80
) was probably in use by the previous web server and the installer used the alternative port (8080
).
You log shows port 80
is available. If you want to access without adding :8080
you can change the ports running this command:
sudo pihole-FTL --config webserver.port '80o,443so'
After that the web interface will be available at http://192.168.1.57/admin
1 Like
I'll definately update the server port thank you.
The real confusing part was the UI shifting the IP from .11 > .57.
The Ether settings still suggest .11 I'll attempt to dig a bit deeper I'd rather fully understand unexpected changes.
Thanks again.
This is not touched by Pi-hole installer.
Your debug log show the IP is set by the DHCP server (192.168.1.1
- probably your router).
Further investigation showed a new ethernet interface had been created with the .57 IP, netplan0. Early research suggests this is likely associated with the Ubuntu mate upgrade. Possibly the original interface took too long to launch, subsequently this was set with a priority of -999 and the netplan interfeace assigned a priority of 0.
It seems the .57 is now acting as the Pi-hole address.
Still uncertain if this is 'normal' or a full wipe and reinstall is warranted. The Pi 4 works albeit a little slower with the later ubuntu version.