First thing first I have both Pi-hole and Squid on my Raspberry PI
Everything working thing except for my web-interface which stoped worked but the Pi hole was still filtering
The web interface is displaying text only
<?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.
I have no issue with webmin (squid)
Something happen today and I had no internet at all from the PI
I had to edit sudo nano /etc/resolv.conf and add 208.67.222.222 instead.
I installed Pi-hole again (still no web interface)
if I change resolv.conf with 127.0.0.1, no internet again.
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
*** [ INITIALIZING ]
[i] 2017-12-13:22:21:19 debug log has been initiated.
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enxb827ebf6ab73 interface:
10.0.4.70/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the enxb827ebf6ab73 interface:
fe80::21c1:8ec4:3d3:1a3d does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
*** [ DIAGNOSING ]: Ports in use
[10000] is in use by miniserv.
is in use by
[139] is in use by smbd
is in use by
[22] is in use by sshd
[3128] is in use by squid
[445] is in use by smbd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[53] is in use by dnsmasq
[25] is in use by master
[3306] is in use by mysqld
[4711] is in use by pihole-FTL
[53] is in use by dnsmasq
[953] is in use by named
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve ad.doubleclick.net.21724.9075.302br.net via localhost (127.0.0.1)
[✗] Failed to resolve ad.doubleclick.net.21724.9075.302br.net via Pi-hole (10.0.4.70)
[✓] doubleclick.com is 10.192.168.148 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is failed
[✗] lighttpd daemon is failed
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Server: nginx/1.10.3
Date: Wed, 13 Dec 2017 22:22:06 GMT
Content-Type: text/html
Content-Length: 940
Last-Modified: Wed, 13 Dec 2017 20:36:08 GMT
Connection: keep-alive
ETag: "5a318f38-3ac"
Accept-Ranges: bytes
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 403 Forbidden
Server: nginx/1.10.3
Date: Wed, 13 Dec 2017 22:22:06 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 3513139 Dec 10 02:10 /etc/pihole/gravity.list
-----head of gravity.list------
10.0.4.70 0.0.0.0
10.0.4.70 0000mps.webpreview.dsl.net
10.0.4.70 0001.2waky.com
-rw-r--r-- 1 www-data www-data 680 Dec 10 19:17 /var/log/lighttpd/error.log
2017-12-10 18:47:06: (log.c.217) server started
2017-12-10 18:47:06: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2017-12-10 19:17:11: (log.c.217) server started
2017-12-10 19:17:11: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2017-12-10 19:17:12: (log.c.217) server started
2017-12-10 19:17:12: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2017-12-10 19:17:12: (log.c.217) server started
2017-12-10 19:17:12: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2017-12-10 19:17:10: (log.c.217) server started
2017-12-10 19:17:10: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 30858 Dec 13 20:27 /var/log/pihole-FTL.log
[2017-12-13 00:00:02.165] NOTICE: pihole.log has been flushed
[2017-12-13 00:00:02.165] Resetting internal data structure
[2017-12-13 00:00:02.165] Queries in memory before flushing: 13624
[2017-12-13 00:00:02.546] Gravity list entries: 106854
[2017-12-13 00:00:02.547] Blacklist entries: 17
[2017-12-13 00:00:02.548] No wildcard blocking list present
[2017-12-13 00:00:02.548] Reading from /var/log/pihole.log.1 (rw-r--r--)
[2017-12-13 00:00:02.548] Notice: Increasing forwarded struct size from 0 to 4 (328.00 B)
[2017-12-13 00:00:02.553] New forward server: 208.67.220.220 resolver2.opendns.com (0/4)
[2017-12-13 00:00:02.553] Notice: Increasing overTime struct size from 0 to 100 (3.56 KB)
[2017-12-13 00:00:02.558] New forward server: 208.67.222.222 resolver1.opendns.com (1/4)
[2017-12-13 00:00:02.558] Notice: Increasing queries struct size from 0 to 10000 (323.61 KB)
[2017-12-13 00:00:02.559] Notice: Increasing domains struct size from 0 to 1000 (343.61 KB)
[2017-12-13 00:00:02.559] Notice: Increasing clients struct size from 0 to 10 (343.79 KB)
[2017-12-13 00:00:02.559] New client: 127.0.0.1 localhost (0/10)
[2017-12-13 00:00:02.568] New client: 10.0.4.90 (1/10)
[2017-12-13 00:00:03.358] Notice: Increasing overTime struct size from 100 to 200 (362.14 KB)
[2017-12-13 00:00:03.991] Reading from /var/log/pihole.log (rw-r--r--)
[2017-12-13 04:39:59.579] Notice: Increasing queries struct size from 10000 to 20000 (687.93 KB)
[2017-12-13 09:12:19.780] Notice: Increasing overTime struct size from 200 to 300 (692.16 KB)
[2017-12-13 10:47:42.622]
[2017-12-13 10:47:42.639] FTL branch: (no branch)
[2017-12-13 10:47:42.639] FTL hash: v2.11.1
[2017-12-13 10:47:42.639] FTL date: 2017-10-08 12:35:40 -0700
[2017-12-13 10:47:42.639] FTL user: pihole
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 1941506 Dec 13 15:00 /var/log/pihole.log
-----head of pihole.log------
Dec 13 00:00:02 dnsmasq[449]: query[PTR] 220.220.67.208.in-addr.arpa from 127.0.0.1
Dec 13 00:00:02 dnsmasq[449]: cached 208.67.220.220 is resolver2.opendns.com
Dec 13 00:00:02 dnsmasq[449]: query[PTR] 222.222.67.208.in-addr.arpa from 127.0.0.1
Dec 13 00:00:02 dnsmasq[449]: cached 208.67.222.222 is resolver1.opendns.com
Dec 13 00:00:02 dnsmasq[449]: query[PTR] 90.4.0.10.in-addr.arpa from 127.0.0.1
Dec 13 00:00:02 dnsmasq[449]: config 10.0.4.90 is NXDOMAIN
Dec 13 00:00:04 dnsmasq[449]: query[PTR] 90.4.0.10.in-addr.arpa from 127.0.0.1
Dec 13 00:00:04 dnsmasq[449]: config 10.0.4.90 is NXDOMAIN
Dec 13 00:00:09 dnsmasq[449]: query[PTR] 62.4.0.10.in-addr.arpa from 127.0.0.1
Dec 13 00:00:09 dnsmasq[449]: config 10.0.4.62 is NXDOMAIN
Dec 13 00:00:09 dnsmasq[449]: query[A] yaycork.ie from 127.0.0.1
Dec 13 00:00:09 dnsmasq[449]: forwarded yaycork.ie to 208.67.220.220
Dec 13 00:00:09 dnsmasq[449]: forwarded yaycork.ie to 208.67.222.222
Dec 13 00:00:09 dnsmasq[449]: query[AAAA] yaycork.ie from 127.0.0.1
Dec 13 00:00:09 dnsmasq[449]: forwarded yaycork.ie to 208.67.220.220
Dec 13 00:00:10 dnsmasq[449]: reply yaycork.ie is 104.27.152.222
Dec 13 00:00:10 dnsmasq[449]: reply yaycork.ie is 104.27.153.222
Dec 13 00:00:10 dnsmasq[449]: reply yaycork.ie is 2400:cb00:2048:1::681b:98de
Dec 13 00:00:10 dnsmasq[449]: reply yaycork.ie is 2400:cb00:2048:1::681b:99de
Dec 13 00:00:11 dnsmasq[449]: query[A] www.facebook.com from 127.0.0.1
You need to let lighttpd have access to port 80 on the same IP that you set Pi-hole to use. Then, you can navigate to http://pi.hole/admin (or use the IP address) to go to the web interface.
You said you have apache (but I don't see it in the log), where is that running? If you are trying to access the web interface through it without setting up PHP then the page will not render correctly (it will just show text as you've seen).