Pihole GUI Down

Ads are still being blocked, but I can't access the GUI anymore. I have rebooted the pihole twice, but instead of the GUI I just get this text displayed...

Total queries (- clients)

---

Queries Blocked

---

Percent Blocked

---

Domains on Blocklist

---

Queries over last hours

Clients (over time)

Query Types

Queries answered by

Query Types (over time)

Upstreams (over time)

Top Permitted Domains

Domain Hits Frequency

Top Blocked Domains

Domain Hits Frequency

Top Clients (total)

Client Requests Frequency

Top Clients (blocked only)

Client Requests Frequency

Can you please provide a debug code ?

Use pihole -d from the command line and paste the provided token here.

https://tricorder.pi-hole.net/vu39strzmb!

I also just updated and ran a repair, but nothing changed. In Chrome I get this...

<?php /* * Pi-hole: A black hole for Internet advertisements * (c) 2017 Pi-hole, LLC (https://pi-hole.net) * Network-wide ad blocking via your own hardware. * * This file is copyright under the latest version of the EUPL. * Please see LICENSE file for your rights under this license. */ $indexpage = true; require "scripts/pi-hole/php/header.php"; require_once("scripts/pi-hole/php/gravity.php"); function getinterval() { global $piholeFTLConf; if(isset($piholeFTLConf["MAXLOGAGE"])) { return round(floatval($piholeFTLConf["MAXLOGAGE"]), 1); } else { return "24"; } } ?>

Total queries (- clients)

---

Queries Blocked

---

Percent Blocked

---

Domains on Blocklist

---

Queries over last <?php echo getinterval(); ?> hours

<?php // If the user is logged in, then we show the more detailed index page. // Even if we would include them here anyhow, there would be nothing to // show since the API will respect the privacy of the user if he defines // a password if($auth){ ?>

Clients (over time)

Query Types

Queries answered by

<?php // Determine if "Query Types (over time)" should be shown $queryTypesOverTime = false; if(isset($setupVars['DASHBOARD_SHOW_QUERY_TYPES_OVER_TIME'])) { if($setupVars['DASHBOARD_SHOW_QUERY_TYPES_OVER_TIME']) { $queryTypesOverTime = true; } }

// Determine if "Forward Destinations (over time)" should be shown
$forwardDestsOverTime = false;
if(isset($setupVars['DASHBOARD_SHOW_FORWARD_DESTS_OVER_TIME']))
{
if($setupVars['DASHBOARD_SHOW_FORWARD_DESTS_OVER_TIME'])
{
$forwardDestsOverTime = true;
}
}
?>

<?php if($forwardDestsOverTime || $queryTypesOverTime) { ?>
<?php if($queryTypesOverTime) { ?>

Query Types (over time)

<?php } if($forwardDestsOverTime) { ?>

Upstreams (over time)

<?php } ?>
<?php } ?> <?php if($boxedlayout) { $tablelayout = "col-md-6"; } else { $tablelayout = "col-md-6 col-lg-6"; } ?>

Top Permitted Domains

Domain Hits Frequency

Top Blocked Domains

Domain Hits Frequency

Top Clients (total)

Client Requests Frequency

Top Clients (blocked only)

Client Requests Frequency
<?php } ?> <?php require "scripts/pi-hole/php/footer.php"; ?>

what's the output of php -version ?

PHP 7.0.33-0+deb9u3 (cli) (built: Mar 8 2019 10:01:24) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.33-0+deb9u3, Copyright (c) 1999-2017, by Zend Technologies

Looks like the web interface is botched.

I see you have lighttpd installed and using port 80 but your header is identifying it as apache (maybe some leftovers from a previous apache install?)

*** [ 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: Wed, 24 Apr 2019 18:03:34 GMT
Server: Apache/2.4.25 (Debian)
Last-Modified: Sat, 02 Feb 2019 11:08:52 GMT
[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Date: Wed, 24 Apr 2019 18:03:34 GMT
Server: Apache/2.4.25 (Debian)
Last-Modified: Mon, 04 Feb 2019 03:16:48 GMT

You also seem to have several errors in your /etc/pihole/setupVars.conf

You have .88 and .253

Everything else looks fine ...

Thanks. Any suggestions on how to resolve these issues? I would've thought running a repair would do the trick. Also, why was it working fine before for months and then all-of-a-sudden stop working?

** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is failed
[✓] pihole-FTL daemon is active

Check the lighttpd daemon and see why it's failing.

sudo systemctl status lighttpd.service

● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset:
   Active: failed (Result: exit-code) since Wed 2019-04-24 11:02:22 PDT; 5h 32mi
  Process: 6067 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (
  Process: 6057 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.co
 Main PID: 6067 (code=exited, status=255)

Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Main process exited, code=
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Unit entered failed state.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Failed with result 'exit-c
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Service hold-off time over
Apr 24 11:02:22 hostname systemd[1]: Stopped Lighttpd Daemon.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Start request repeated too
Apr 24 11:02:22 hostname systemd[1]: Failed to start Lighttpd Daemon.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Unit entered failed state.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Failed with result 'exit-c
lines 1-16/16 (END)...skipping...
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-04-24 11:02:22 PDT; 5h 32min ago
  Process: 6067 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
  Process: 6057 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 6067 (code=exited, status=255)

Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Main process exited, code=exited, status=255/n/a
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Unit entered failed state.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Apr 24 11:02:22 hostname systemd[1]: Stopped Lighttpd Daemon.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Start request repeated too quickly.
Apr 24 11:02:22 hostname systemd[1]: Failed to start Lighttpd Daemon.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Unit entered failed state.
Apr 24 11:02:22 hostname systemd[1]: lighttpd.service: Failed with result 'exit-code'.

I think apache is fighting lighttpd.

If you don't need/use it,remove it ...

You're a genius. That did the trick. Thank you!

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.