Please follow the below template, it will help us to help you!
Expected Behaviour:
Default web admin page appears after installation
Actual Behaviour:
Default web admin page almost blank with just a few text headings (see attached screenshot)
You have Apache serving the pages, we ship with lighttpd and only support that server
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Mon, 15 Jul 2019 03:33:40 GMT
Server: Apache/2.4.38 (Debian)
Last-Modified: Sun, 14 Jul 2019 07:54:14 GMT
ETag: "29cd-58d9f7328daba"
Accept-Ranges: bytes
Content-Length: 10701
Vary: Accept-Encoding
Content-Type: text/html
How do I change that? I never deliberately installed Apache, and used the install script as is without modification.
We don't install Apache either, it's not a part of our script. Another application perhaps? Is there anything else installed on this server?
Ah, in hindsight I think I may have selected the web server option when I was installing Debian Buster last night.
Anyway so I purged apache from the system, uninstalled and then reinstalled Pi-hole. Now I get the error:
Failed to start pihole-FTL.service: Unit pihole-FTL.service not found.
When I try pihole restartdns. Any ideas?
UPDATE: rebooted. Service didn't start automatically as it should. Had to start it manually. It's running, but there's absolutely zero web admin page. Browser loads nothing.
Any ideas? I'm kinda surprised because from my reading of the forums this issue was addressed by v4.3.1's Buster support, so this shouldn't be happening.
Can you do a new debug run since you've made substantial changes that make the previous one outdated.
1 Like
Sorry for the delay. Somehow while going through uninstalling and reinstalling I killed my network connection. Took multiple reboots to get it back. Here's the new debug log: https://tricorder.pi-hole.net/u2l7aywmj2
Some more details from when I try to manually start the pihole service:
$ pihole status
[✗] DNS service is NOT running
$ sudo service pihole-FTL restart
Failed to restart pihole-FTL.service: Unit pihole-FTL.service not found.
$ sudo pihole restartdns
[✗] Failed to start pihole-FTL.service: Unit pihole-FTL.service not found.
Probably the best would be to start over again with a fresh image. In this debug log I see that lighttpd is not working, and pihole-FTL is not working.
That's what I did this morning to get that log. I completely uninstalled Pi-hole - as well as Apache - last night. This morning I even downloaded the script and ran it locally so that curl issues wouldn't cause problems.
Also, even when I did get pihole-FTL running, the web interface was dead.
My guess is something is going wrong during the installation. Do you think uninstalling and then reinstalling as su might help?
No, running as su will not help as the script already runs under sudo privs.
I meant starting completely from a fresh install of the operating system, not trying to re-install on a system that has been modified already. Even with uninstalling there are files and system changes that have been made that need to be reverted.
That's a very extreme suggestion for fixing an application issue. OS reinstallation should be limited to OS problems, not problems with applications. If it can be shown that the OS is malfunctioning in some way, then I'll consider that, but right now the problems I'm experiencing are definitely limited to pi-hole and pi-hole only, and support threads say Buster is supported. Everything else network related works just fine.
There's nothing exotic about this Debian installation. The only non-default thing in the DNS stack is dnscrypt-proxy; otherwise it's just regular Debian Buster with KDE, unattended-upgrades, and TeamViewer and Resilio Sync running in the background.
If I reinstalled the only thing I'd change is unselecting the web server option. Since I already removed Apache2 and am still having difficulties, it's unlikely reinstalling would change anything.
Can you think of anything that would be preventing lighttpd and pihole-FTL from running after installation?
There could be a number of things. Let's first check which processes are running on ports used by Pi-Hole. What is the output of this command from the Linux terminal:
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:67 \|:80 \|:471'
I ran pihole -r and now I get:
$ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
Also, subsequently:
$ sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 1165/pihole-FTL
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1165/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 1165/pihole-FTL
tcp6 0 0 :::53 :::* LISTEN 1165/pihole-FTL
udp 0 0 0.0.0.0:5353 0.0.0.0:* 565/avahi-daemon: r
udp 0 0 0.0.0.0:53 0.0.0.0:* 1165/pihole-FTL
udp6 0 0 :::5353 :::* 565/avahi-daemon: r
udp6 0 0 :::53 :::* 1165/pihole-FTL
I tried manually starting lighttpd and got:
$ sudo /etc/init.d/lighttpd start
[....] Starting lighttpd (via systemctl): lighttpd.serviceJob for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.
$ sudo systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-07-16 10:18:04 CDT; 46s ago
Process: 2943 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, sched
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: Stopped Lighttpd Daemon.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Start request repeated too quickly.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: Failed to start Lighttpd Daemon.
$ sudo journalctl -xe
Jul 16 10:18:03 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit lighttpd.service has entered the 'failed' state with result 'exit-code'.
Jul 16 10:18:03 DELLOPTIPLEX390-1 systemd[1]: Failed to start Lighttpd Daemon.
-- Subject: A start job for unit lighttpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit lighttpd.service has finished with a failure.
--
-- The job identifier is 2286 and the job result is failed.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Service RestartSec=100ms expired, sched
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Scheduled restart job, restart counter
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit lighttpd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: Stopped Lighttpd Daemon.
-- Subject: A stop job for unit lighttpd.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit lighttpd.service has finished.
--
-- The job identifier is 2364 and the job result is done.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Start request repeated too quickly.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: lighttpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit lighttpd.service has entered the 'failed' state with result 'exit-code'.
Jul 16 10:18:04 DELLOPTIPLEX390-1 systemd[1]: Failed to start Lighttpd Daemon.
-- Subject: A start job for unit lighttpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit lighttpd.service has finished with a failure.
--
-- The job identifier is 2364 and the job result is failed.
Jul 16 10:18:50 DELLOPTIPLEX390-1 sudo[2949]: judah : TTY=pts/1 ; PWD=/home/judah ; USER=root ; COMM
Jul 16 10:18:50 DELLOPTIPLEX390-1 sudo[2949]: pam_unix(sudo:session): session opened for user root by (
Jul 16 10:19:48 DELLOPTIPLEX390-1 sudo[2949]: pam_unix(sudo:session): session closed for user root
Jul 16 10:20:01 DELLOPTIPLEX390-1 CRON[3005]: pam_unix(cron:session): session opened for user root by (
Jul 16 10:20:01 DELLOPTIPLEX390-1 CRON[3006]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole update
Jul 16 10:20:01 DELLOPTIPLEX390-1 CRON[3005]: pam_unix(cron:session): session closed for user root
Jul 16 10:22:35 DELLOPTIPLEX390-1 sudo[3021]: judah : TTY=pts/1 ; PWD=/home/judah ; USER=root ; COMM
Jul 16 10:22:35 DELLOPTIPLEX390-1 sudo[3021]: pam_unix(sudo:session): session opened for user root by (
So it looks like lighttpd is crashing. I feel like we're making some progress as to the root cause here. Any ideas?
You should start/stop this process using its service command, not via a direct call to the executable (as you discovered).
Have you checked the referenced debian support link for the systemd message?
Please upload a fresh debug log and post the new token.
When I Googled how to start lighttpd that command was the only one that came up. I didn't know it was a service. Anyway, I tried the usual service restart command and got:
$ sudo systemctl start lighttpd.service
Job for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.
It's unfortunately just a general support page with links to IRC, mailing lists, etc.
You have a number of problems in this debug log. Snippets posted below:
IPv4 networking isn't working. IPv6 has multiple FE80 addresses assigned. Neither lighttpd nor pihole-FTL is running. Your gravity list is empty.
You can chase individual problems for the next few weeks, but my advice would be to do what Dan recommended: do a fresh install of Buster, ensure that is clean, then reinstall Pi-Hole. After Pi-Hole is working, that add additional software or packages to the Debian install. This will identify any OS or software changes that are causing Pi-Hole problems.
I have Buster installed on a Zero W with Pi-Hole and unbound running as well. There are zero problems on that device, so going back to the basics is a good starting point. You have made a number of software changes to your Buster install, and any of them could be causing problems. Eliminate them all.
[✓] IPv6 address(es) bound to the enp4s0 interface:
fe80::600c:83e5:c608:d049 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
fe80::e214:3e2f:b846:5939 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
[i] Default IPv4 gateway: 192.168.0.1
192.168.0.1
* Pinging 192.168.0.1
192.168.0.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve via localhost (127.0.0.1)
[✗] Failed to resolve via Pi-hole (192.168.0.139)
[✓] doubleclick.com is 172.217.0.14 via a remote, public DNS server (8.8.8.8)
*** [ 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.
*** [ DIAGNOSING ]: Gravity list
-----head of gravity.list------
-----tail of gravity.list------
-rw-r--r-- 1 pihole pihole 0 Jul 17 00:00 /var/log/pihole-FTL.log
-----head of pihole-FTL.log------
-----tail of pihole-FTL.log------
1 Like
Probably because I unselected all the default lists, but of course that doesn't cover the other issues.
OK, fair enough. I was alarmed at that suggestion right off the bat but yeah it does seem a lot of stuff is broken for some reason. I downloaded the Buster live image last night in preparation because the this whole thing started from using the netinstall in the 1st place.
Fun fact: I run Windows 10, (a Free)BSD( fork), and multiple Linux distros across 10 machines, and this is the 1st time I've had to reinstall an OS from scratch to fix a problem since 2006/7. Every other issue I've ever had has been fixable in the same installation. Also my 1st time using Debian, so that might be it.
Thanks for your assistance. Reinstallation it is!
UPDATE: Reinstalled from scratch using just the KDE live CD ISO and everything appears to be working.
Lessons learned:
- Keep the base OS image as simple as you can manage
- Use the Debian live CD installer, not netinstall
- Don't select the webserver option during Debian installation
Thanks all for your assistance.
I figured out why this is the case. If you use KDE, ensure the machine is configuring the network connection with an IPv4 address and not an IPv6 one. To check and fix that, do the following:
- Right-click the network connection icon in the system tray
- Click Configure Network Connections...
- In the Connections - System Settings Module window that pops up, in the list on the left, click the wired network connection via which machine is connected to the LAN
- Under the Wired tab on the right, check the Allow auto-negotiation option
- Click Apply
- Under the IPv6 tab on the right, change the value of the Method dropdown to Ignored
- Click Apply
- Click OK
- Reboot the machine
This should allow the OS to autonegotiate and IPv4 address for the network connection.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.