Pi Hole web interface site can't be reached

[pihole_noob]

Expected Behaviour:

Should display web interface

Actual Behaviour:

Showing error "Site Can't be reached" on Chrome but I can connect via Putty

Steps Taken:

I'm using my RPi 3 with dietpi and am following the steps here to setup PiHole:

Quick and Easy Pi-hole Setup

I've already checked similar posts and most of them are resolved when using pihole -r. However mine still doesn't.

I checked this post in Discourse: DNS not listening

pihole status show DNS not listening

but the issue I get is that sudo apt install libc6:amd64 shows unable to locate package

I'd also like to point out that I encountered an error message during installation of PiHole that says:

"Raspbian is supported but version 11 is currently unsupported "

Any help is highly appreciated.

Debug Token:

https://tricorder.pi-hole.net/FXQmwWWG/

[yubiuser]

So you used dietpi-config to install Pi-hole?

@MichaIng I thought I've read your installer already included the necessary changes to install Pi-hole on Raspbian 11?

---

Neither pihole-FTL nor the web interface are working right now.

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  0
[i] dig response:  "Raspbian=9,10 Ubuntu=16,18,20 Debian=9,10 Fedora=32,33 CentOS=7,8"
[✓] Distro:  Raspbian
[✗] Version: 11
[✗] Error: Raspbian is supported but version 11 is currently unsupported (https://docs.pi-hole.net/main/prerequisites/)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  via localhost (127.0.0.1)
[✗] Failed to resolve  via Pi-hole (192.168.100.5)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is failed
[✗] pihole-FTL daemon is inactive

*** [ DIAGNOSING ]: Pi-hole-FTL full status
   ● pihole-FTL.service - LSB: pihole-FTL daemon
     Loaded: loaded (/etc/init.d/pihole-FTL; generated)
     Active: inactive (dead)
       Docs: man:systemd-sysv-generator(8)

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 0 Sep  3 01:17 /var/log/lighttpd/error.log
   -----head of error.log------

   -----tail of error.log------

*** [ DIAGNOSING ]: contents of /var/log

*** [ DIAGNOSING ]: contents of /dev/shm

*** [ DIAGNOSING ]: Pi-hole diagnosis messages

*** [ DIAGNOSING ]: Locale
    LANG=C.UTF-8

*** [ DIAGNOSING ]: Pi-hole log

   -----head of pihole.log------

---

What happens if you run

pihole restartdns

Do you see any content afterwards in /var/log/pihole-FTL.log?

[pihole_noob]

I ultimately gave up on dietpi and used Buster because of the unsupported OS error. It currently works for me right now but I'll have to figure out why pihole -g gives me a "DNS resolution is currently unavailable " error.

Thanks for your time!

[MichaIng]

dietpi-software's Pi-hole install supports Bullseye for a long time, also as it sets the flag to ignore the OS error (so we're able to test things early). So OP used the official installer.

The official installer should btw work just fine on Bullseye with:

apt install lighttpd-mod-deflate
export PIHOLE_SKIP_OS_CHECK=true
curl -sSfL https://install.pi-hole.net | bash

Lighttpd will show a warning about deprecated "compress" directives, but will use deflate as fallback, which is not shipped with Lighttpd core package anymore but is hence installed as separate package.

Opposed to this solution, next Pi-hole release has the compress directives removed from its Lighttpd config, so data is transferred uncompressed. But not relevant for a low traffic single user admin panel, where you're not bound to SEO or traffic rates, and where the other way round the little CPU time for compression is negligible .

[Sincere_Glasses_25]

These methods may help:

1. Check if the pi is on
2. check if your pi has a software update
3. Check on your pi, are there alerts?, is is connected?, has it lost complete access to WIFI?
   4.Try to reinstall the raspberry pi OS and reinstall pi-hole

If these don't work, YIKES! you have to talk to someone else, this happened to me and I waited like 2 months and it started working again, hope this helps!