PM this log to me.
edit in nano and copy paste? or there is a better method ?
Use the command cat /var/log/pihole_debug.log
and copy that entire output into a message to me.
EDIT: below is wrong, previous posting with binary was the correct one for Pi Zero.
I noticed my mistake, I supplied you with the wrong binary.
Below one is the correct one:
sudo tee /etc/resolv.conf <<< $'nameserver 8.8.8.8'
sudo wget https://github.com/pi-hole/FTL/releases/download/v4.3.1/pihole-FTL-arm-linux-gnueabihf -O /usr/bin/pihole-FTL
sudo chmod +x /usr/bin/pihole-FTL
sudo service pihole-FTL restart
pihole status
i guess i will need a -r or a install again?
pi@raspberrypi:~ $ sudo chmod +x /usr/bin/pihole-FTL
pi@raspberrypi:~ $ sudo service pihole-FTL restart
Failed to restart pihole-FTL.service: Unit pihole-FTL.service not found.
pi@raspberrypi:~ $ pihole status
[β] DNS service is NOT running
pi@raspberrypi:~ $
Yes try repair pihole -r
with nameserver
hack.
Debug log after failed install
*** [ INITIALIZING ]
[i] 2019-12-03:00:30:09 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-ge41c4b5
*** [ DIAGNOSING ]: Web version
[i] Web: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-g38d8e77
*** [ DIAGNOSING ]: FTL version
[β] FTL: v4.3.1
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.53
*** [ DIAGNOSING ]: php version
[i] 7.3.11
*** [ DIAGNOSING ]: Operating system
[β] Raspbian GNU/Linux 10 (buster)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
[β] armv6l
*** [ DIAGNOSING ]: Networking
[β] IPv4 address(es) bound to the eth0 interface:
192.168.2.42/24 matches the IP found in /etc/pihole/setupVars.conf
[β] IPv6 address(es) bound to the eth0 interface:
fe80::7500:18d:a8dc:b0f8 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)
^ 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/setupV ars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 addre ss changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.2.1
* Pinging 192.168.2.1...
[β] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a k nown ad-serving domain
[β] Failed to resolve via localhost (127.0.0.1)
[β] Failed to resolve via Pi-hole (192.168.2.42)
[β] doubleclick.com is 172.217.13.142 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[β] lighttpd daemon is active
[β] pihole-FTL daemon is inactive
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.2.42/24
IPV6_ADDRESS=
PIHOLE_DNS_1=1.1.1.1
PIHOLE_DNS_2=1.0.0.1
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
*** [ DIAGNOSING ]: Dashboard and block page
[β] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Mon, 02 Dec 2019 19:30:19 GMT
Server: lighttpd/1.4.53
[β] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-----head of gravity.list------
-----tail of gravity.list------
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 313 Dec 3 00:23 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 234 Dec 3 00:23 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1387 Dec 3 00:23 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=1.1.1.1
server=1.0.0.1
interface=eth0
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3499 Dec 3 00:23 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "/pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.ht ml" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/h tml", "text/plain" )
mimetype.assign = ( ".png" => "image/png",
".jpg" => "image/jpeg",
".jpeg" => "image/jpeg",
".html" => "text/html",
".css" => "text/css; charset=utf-8",
".js" => "application/javascript",
".json" => "application/json",
".txt" => "text/plain",
".svg" => "image/svg+xml" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'let sencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1704 Dec 3 00:23 /etc/cron.d/pihole
23 4 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity >/va r/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker loc al
40 14 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remo te
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote rebo ot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 301 Dec 3 00:23 /var/log/lighttpd/error.log
2019-12-02 23:28:55: (server.c.1464) server started (lighttpd/1.4.53)
2019-12-03 00:23:56: (server.c.2059) server stopped by UID = 0 PID = 1
2019-12-03 00:23:58: (server.c.1464) server started (lighttpd/1.4.53)
2019-12-03 00:23:58: (server.c.1493) WARNING: unknown config-key: alias.url ( ignored)
*** [ DIAGNOSING ]: contents of /var/log
*** [ DIAGNOSING ]: contents of /dev/shm
*** [ DIAGNOSING ]: Locale
LANG=en_CA.UTF-8
*** [ DIAGNOSING ]: Pi-hole log
-----head of pihole.log------
It looks like you don't have your timezone set correctly. If you are in Canada, then no part of Canada should have a time earlier than 2019-12-02 16:30.
sudo dpkg-reconfigure tzdata
im in Canada,Quebec
we are gmt -5 at the moments
i will fix the timezone before the pihole -r
at the time of this its 14:58
I suspect that without an accurate time on the Pi, then the SSL connection for curl cannot be made.
i understand but i have put the right time zone. i'm sure of that. when it gives me the time after the modification its match my time. the local though i'm not sure :Locale
LANG=en_CA.UTF-8 waht the closest to what i think we am there was another en_CA but not utf
oh and the pihole -r didnt repaired
DNS stay offline
[i] Restarting services...
[β] Enabling pihole-FTL service to start on reboot...
[β] Restarting pihole-FTL service...
[β] Deleting existing list cache
[i] Pi-hole blocking is enabled
[β] DNS service is not running
[β] Restarting DNS service
[β] DNS resolution is not available
Run another debug log and upload it when prompted. If it cannot upload, then do the nameserver workaround and try again.
What is the output of date
And reboot when you change TZ!
Some services might still hold the old settings without a reboot.
EDIT: More TZ details:
timedatectl
Mon Dec 2 15:10:43 EST 2019
it the real time here match cell and pc
pi@raspberrypi:~ $ timedatectl
Local time: Mon 2019-12-02 15:11:36 EST
Universal time: Mon 2019-12-02 20:11:36 UTC
RTC time: n/a
Time zone: America/Montreal (EST, -0500)
System clock synchronized: no
NTP service: active
RTC in local TZ: no
and i made a system reboot
Weird it didnt sync.
What if you do below:
sudo timedatectl set-ntp true
And run below again:
timedatectl
no change
Is the daemon running/active ?
service systemd-timesyncd status
systemd-timesyncd: unrecognized service