Type in the browser address bar 192.168.1.197/Admin and see the admin page
Unable to connect
https://tricorder.pi-hole.net/5rgeze8yzs
The debug says "No IPv4 address(es) found on the interface."
WTF? How am I able to connect to it via SSL, using that IP, then???
This is not specifically a Pi-Hole problem, it is a problem with the host platform for Pi-Hole (in your case it appears to be a Pi) not having an IP address that leads to the router.
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the interface.
[✗] No IPv6 address(es) found on the interface.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
Your Pi-Hole is configured to listen on 192.168.1.197, and if it receives traffic there, it is responding properly. You can confirm the IP setup of the Pi with this command from the Linux terminal:
ip addr
The second problem is that the lighttpd daemon is failed, and this is the server that provides the web page.
*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is failed
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
What are the outputs of the following from the Pi terminaL
sudo service lighttpd status
sudo systemctl status --full --no-pager lighttpd
A third potential problem is this section of your debug log - either the output is corrupted in the log, or you have some domains included in your setup file (which is not where they should be).
Check the following files: /etc/pihole/setupVars.conf and /etc/pihole/pihole-FTL.conf
*** [ DIAGNOSING ]: Setup variables
adjust.io
airbrake.io
appboy.com
appsflyer.com
apsalar.com
bango.combango.org
bango.net
basic-check.disconnect.me
bkrtx.com
bluekai.com
bugsense.com
burstly.com
chartboost.com
count.ly
crashlytics.coPIHOLE_INTERFACE=eth0
The OrangePi has an active IP address (192.168.1.197), and that's what I use to log in via SSH.
Also it has Internet connection because I could install the Pi_hole via Internet (plus updates for the Armbian).
ip addr shows:
root@orangepione:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether fa:43:59:59:ac:c3 brd ff:ff:ff:ff:ff:ff
inet6 fe80::eb52:780:a000:6b1f/64 scope link
valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 02:81:ec:28:5a:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.197/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::1714:7ec3:4a8e:dafc/64 scope link
valid_lft forever preferred_lft forever
So to it looks like just the PiHole that doesn't "see" that connection.
The other commands:
root@orangepione:~# sudo service lighttpd status
* lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-06-09 08:58:10 EDT; 5h 1min ago
Process: 1273 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, statu
Process: 1223 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, s
Main PID: 1273 (code=exited, status=255)
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Service hold-off time over, scheduling r
Jun 09 08:58:10 orangepione systemd[1]: Stopped Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 09 08:58:10 orangepione systemd[1]: Failed to start Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Unit entered failed state.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
lines 1-14/14 (END)
root@orangepione:~# sudo service lighttpd status
* lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-06-09 08:58:10 EDT; 5h 1min ago
Process: 1273 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, statu
Process: 1223 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, s
Main PID: 1273 (code=exited, status=255)
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Service hold-off time over, scheduling r
Jun 09 08:58:10 orangepione systemd[1]: Stopped Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 09 08:58:10 orangepione systemd[1]: Failed to start Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Unit entered failed state.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
root@orangepione:~# sudo systemctl status --full --no-pager lighttpd
* lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-06-09 08:58:10 EDT; 5h 2min ago
Process: 1273 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
Process: 1223 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
Main PID: 1273 (code=exited, status=255)
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Jun 09 08:58:10 orangepione systemd[1]: Stopped Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 09 08:58:10 orangepione systemd[1]: Failed to start Lighttpd Daemon.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Unit entered failed state.
Jun 09 08:58:10 orangepione systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Run pihole -r and make sure to choose the correct interface.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.