Try to update the pihole system with sudo pihole -up
can´t update, always the following error:
sudo pihole -up
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: Something has gone wrong, cannot reach download server
Do you have your Pi configured to use Pi-hole for DNS? If so, that won't work during updates as FTL will be unavailable. At least temporarily (though permanently is better, IMO), configure a public DNS for your Pi's network.
IIRC that can only happen later on in the process so either it was a temporary issue or something else is wrong ?!
Could be, but the error seemed to have occured only on the FTL check...so I was suspicious.
Are you still seeing the same issue? Or it was just a temporary network glitch?
Have the problem since month. Yes, pihole is my dns server.
sorry, in my fritzbox there ist a DNS server (8.8.8.8) registered. So pihole is not my DNS Server, in my pi-hole there is my fritz box selected as my DSN Server.
Any ideas?
We can try to get more information on how it is failing.
Run sudo bash -x /opt/pihole/update.sh and post the end of the command.
If that doesnt show any debug information around the error, try posting the output of sudo bash -x /etc/.pihole/automated\ install/basic-install.sh --repair --unattended
Thank you! here are both outputs:
+ [[ v6.5 != \v\6\.\5 ]]
+ return 1
+ web_update=false
+ echo -e ' [i] Web Interface:\tup to date'
[i] Web Interface: up to date
+ local funcOutput
++ get_binary_name
++ local l_binary
++ local machine
+++ uname -m
++ machine=aarch64
++ local 'str=Detecting processor'
++ printf ' %b %s...' '[i]' 'Detecting processor'
++ [[ aarch64 == \a\a\r\c\h\6\4 ]]
++ printf '%b %b Detected AArch64 (64 Bit ARM) architecture\n' '\r' '[✓]'
++ l_binary=pihole-FTL-arm64
++ echo pihole-FTL-arm64
[✓] Detected AArch64 (64 Bit ARM) architecture
pihole-FTL-arm64'
+ local binary
+ binary=pihole-FTL-arm64
+ FTLcheckUpdate pihole-FTL-arm64
+ case $? in
+ echo -e ' [i] FTL:\t\tSomething has gone wrong, cannot reach download server'
[i] FTL: Something has gone wrong, cannot reach download server
+ exit 1
[i] FTL Checks...
[✓] Detected AArch64 (64 Bit ARM) architecture
'
[✓] Detected AArch64 (64 Bit ARM) architecture
+ FTLcheckUpdate pihole-FTL-arm64
+ local ftlLoc
++ command -v pihole-FTL
+ ftlLoc=/usr/bin/pihole-FTL
+ local ftlBranch
+ [[ -f /etc/pihole/ftlbranch ]]
+ ftlBranch=master
+ local binary
+ binary=pihole-FTL-arm64
+ local remoteSha1
+ local localSha1
+ [[ master != \m\a\s\t\e\r ]]
+ [[ -n /usr/bin/pihole-FTL ]]
+ local FTLversion
++ /usr/bin/pihole-FTL tag
+ FTLversion=v6.5
+ local FTLlatesttag
++ curl -s https://api.github.com/repos/pi-hole/FTL/releases/latest
++ jq -sRr 'fromjson? | .tag_name | values'
+ FTLlatesttag=
+ '[' -z '' ']'
+ printf ' %b Failed to retrieve latest FTL release metadata\n' '[✗]'
[✗] Failed to retrieve latest FTL release metadata
+ return 3
+ case $? in
+ exit 1
I suggest you use code blocks to share the output, this wil make it much more readable.
They can either be added via [+] > Preformatted text in the UI (you need to be on an empty line)
or by typing:
```
type or paste code here
```
Those characters are backticks `, not the apostrophe ‘.
The UI may render them strange, but both lines contain the same character (six backticks across two lines)
Your Pi has an issue reaching the GitHub API. Let’s investigate further with curl -v https://api.github.com/repos/pi-hole/FTL/releases/latest.
You may also try dig api.github.com, dig api.github.com @1.1.1.1 and curl -v -4 https://api.github.com/repos/pi-hole/FTL/releases/latest
This was the solution! Thank you!!!!!
Glad that it’s working again.
My most recent commands are meant to help troubleshoot how your Pi has issues connecting to GitHub, they do not change anything on the machine. But seeing it work now, confirms our previous suspicion that it might be a temporary network issue.