After update of Pi-Hole it doesn't work anymore 
I wished I've never start the last Update. After some reading I foud out that my OS is to old. Why the Update starts when the OS is to old?
How ever, now it is like it is and I hope someone can help me to get back the old Version which worked fine for me.
best regards
Revert to latest working release
cd /etc/.pihole
sudo git fetch --tags
sudo git reset --hard v5.11.4
cd /var/www/html/admin
sudo git fetch --tags
sudo git reset --hard v5.13
pihole checkout ftl v5.16.3
it shoud work, dont update pihole until you update your OS
Thank you for your answer.
After pihole checkout ftl v516.3 I got the following error:
pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL)
The GUI seems to be the old one, but FTL is not running
To solve this
modify line 171 of /opt/pihole/piholeCheckOut.sh to read oldbranch="$(pihole-FTL -b || echo master)
and run the checkout command again.
source: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found
Seems to be another problem with certificates
pihole checkout ftl v5.16.3
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL)
[✓] Branch v5.16.3 exists
[i] Switching to branch: "v5.16.3" from "master"
[i] Downloading and Installing FTL...curl: (60) SSL certificate problem: certificate has expired
More details here: curl - SSL CA Certificates
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
[✗] Downloading and Installing FTL
Error: URL https://ftl.pi-hole.net/v5.16.3/pihole-FTL-armv7-linux-gnueabihf not found
solution here:
Found a valid 'DigiCert High Assurance EV Root CA' certificate from https://curl.se and store it into the ca-store this seems to have fixed the trust of github.com and githubusercontent.com again
or
Adding -k to curl in /opt/pihole/gravity.sh fixes the gravity downloading
or better way:
I was able to solve this just by adding the insecure flag (-k) to the curl command within the pi-hole installation script bash-script.sh.
The second and preferred way to fix this is by running wget -O /etc/ssl/certs/cacert.pem https://curl.haxx.se/ca/cacert.pem && export SSL_CERT_FILE=/etc/ssl/certs/cacert.pem && echo 'SSL_CERT_FILE=/etc/ssl/certs/cacert.pem' | sudo tee -a /etc/environment
src: pi-hole won't install · Issue #494 · hoobs-org/HOOBS · GitHub
No Chance, the Certificate is outdated I I try to update it, I have no rights for that...
Where I find the bash-script.sh.?
--2022-09-10 15:48:45-- https://curl.haxx.se/ca/cacert.pem
Auflösen des Hostnamens »curl.haxx.se (curl.haxx.se)« … 151.101.2.49, 151.101.66.49, 151.101.130.49, ...
Verbindungsaufbau zu curl.haxx.se (curl.haxx.se)|151.101.2.49|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 301 Moved Permanently
Platz: https://curl.se/ca/cacert.pem [folgend]
--2022-09-10 15:48:45-- https://curl.se/ca/cacert.pem
Auflösen des Hostnamens »curl.se (curl.se)« … 151.101.193.91, 151.101.1.91, 151.101.65.91, ...
Verbindungsaufbau zu curl.se (curl.se)|151.101.193.91|:443 … verbunden.
FEHLER: Dem Zertifikat von »curl.se« wird nicht vertraut.
FEHLER: Das Zertifikat von »curl.se« ist abgelaufen.
Consider keeping your OS up to date.
By now, with all those manipulations you've applied in the meantime, you've probably messed up your system beyond a sane, comprehensible state.
I'd recommend to backup your settings via Pi-hole's teleporter and start afresh from a a current OS.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.