Hello Community,
I just wanted to make sure whether my Pi-hole is updated. Here is the log
pi@raspberrypi:~ $ pihole -up
[i] Checking for updates...
fatal: unable to access 'https://github.com/pi-hole/pi-hole.git/ ': Could not resolve host: github.com
[i] Pi-hole Core: up to date
fatal: unable to access 'https://github.com/pi-hole/AdminLTE.git/ ': Could not resolve host: github.com
[i] Web Interface: up to date
[i] FTL: Something has gone wrong, contact support
[?] Everything is up to date!
It says Pi-Hole is updated but FTL needs an update. It Throws an error message stating something wrong with FTL.
Any pointers or logs needed?
Thanks in Advance
jfb
November 18, 2019, 10:08pm
2
Please send us the token generated by
pihole -d
or do it through the Web interface:
Method 1: Generate a debug token via the Web interface
Log in to your Pi-hole's Web interface
Navigate to Tools > Generate debug log
Click the Generate debug log button
Send us the debug token
[debug]
Method 2: Use the command line to generate a debug token
Login into your Pi-hole's command line
Enter pihole -d
Provide us with the debug token that is generated after the debug script completes
Alternative: Securely sending us additional information
Preferred Method
If there is additiโฆ
If you cannot upload the log, then please do these steps:
This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
sudo nano /etc/resolv.conf
edit nameserver 127.0.0.1
to nameserver 9.9.9.9
or your preferred third party DNS service, save and exit
Run pihole -d
and upload the debug log
Debug.txt (460.3 KB)
Here is the debug log
Please do let me know if you need anything.
jfb
November 19, 2019, 12:19am
4
Your debug log shows you are on the most recent version.
This is odd in your debug log:
[i] Default IPv4 gateway: #transmit
#transmit
* Pinging #transmit
#transmit...
ping: #transmit
#transmit: Name or service not known
[?] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
You may also want to check your regex entries - there are some errors shown in /var/log/pihole-FTL.log
[2019-11-18 04:07:39.060 7091] Skipping empty regex filter on line 1
[2019-11-18 04:07:39.060 7091] ERROR compiling regex on line 3: Invalid preceding regular expression (13)
[2019-11-18 04:07:39.064 7091] ERROR compiling regex on line 11: Invalid range end (11)
Let's look at why your Pi cannot connect to the Pi-Hole servers. From your Pi terminal, run the following commands and post the output here:
dig tricorder.pi-hole.net
dig github.com
pi@raspberrypi:~ $ dig github.com
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> github.com
;; global options: +cmd
;; connection timed out; no servers could be reached
pi@raspberrypi:~ $
pi@raspberrypi:~ $ dig tricorder.pi-hole.net
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> tricorder.pi-hole.net
;; global options: +cmd
;; connection timed out; no servers could be reached
1 Like
jfb:
pihole-FTL.log
I think I found the problem.
The PI is connected both Wired and Wireless to my router. I have disabled the Wired interface and reset the dns service.
Boom! That fixed the issue.
pi@raspberrypi:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[?] Everything is up to date!
@jfb : Thanks for all the great responses. Appreciate it.
1 Like
system
Closed
December 10, 2019, 12:53am
8
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.