Trying to access admin interface 192.168.xxx.xxx/admin
SSH fine to 192.168.xxx.xxx
work again after reboot
Actual Behaviour:
Firefox can’t establish a connection to the server at 192.168.xxx.xxx
pihole updatePihole
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[✓] Everything is up to date!
As mentioned SSH work fine at ip address, address set statically. Using Dietpi 6.21.1 but installed from command line if memory serves.
Network is functioning, ad blocking seems to be working, pretty confident the problem is the webserver but not sure how to check. Have rebooted twice. Hasn't been up long.
You don't need to hide the IP ranges on your LAN - everybody else uses the same ones and hiding them makes it difficult for others to help resolve your problem.
The problem is that the webserver used by Pi-Hole (lighttpd) is not running:
There is a log at /var/log/pihole.log retained for 5 days, and a long term database at /etc/pihole/pihole-FTL.db that contains up to 365 days data. Is this the logging you are referring to?
Edit - /var/log/pihole-FTL.log is also retained for 5 days
If I remember dietpi updates itself automatically...might explain that.
Raspian does not update unless told to I believe I read?
Many thanks for your time.
On logging I love the gui I just noticed my Mac isn't going to sleep all day.
My HTR receiver is making the 2nd highest DNS requests in the house (it was powered down most days need to investigate that).
Most servers are not configured to auto update/upgrade as things might break without the sysadmin knowing about it.
With servers, you always want to test major updates first in like a sandbox environment or a phased update with one server, out of several redundant servers, at a time.
Auto update/upgrade might be a nice feature for client devices but not for servers.
Plus you can configure Rasbian to perform auto update/upgrade if want it to.