Could not install Pi-hole on fresh Raspberry Pi OS (32-bit) Lite

Help
1

HI!

Could not install Pi-hole on fresh Raspberry Pi OS (32-bit) Lite:

[✓] Checking apt-get for upgraded packages... up to date!

[i] Installer Dependency checks...
[✓] Checking for dhcpcd5
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail
[✓] Checking for dnsutils

[✗] Unsupported OS detected
** Redirecting...

  This check can be skipped by setting the environment variable PIHOLE_SKIP_OS_CHECK to true
  e.g: export PIHOLE_SKIP_OS_CHECK=true

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="RaspbianForums - Raspbian"
BUG_REPORT_URL="RaspbianBugs - Raspbian"

OS LITE should be officially supported or not?

thx and cheers

2

Buster is supported. We'll have to look and see why this message is appearing. What platform is the OS running on?

3

The check requires the ability to pull the latest support information.

Can you dig TXT versions.pi-hole.net and post the output?

4

pi@raspberrypi:~ $ dig TXT versions.pi-hole.net

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> TXT versions.pi-hole.net
;; global options: +cmd
;; connection timed out; no servers could be reached
pi@raspberrypi:~ $

5

Raspberry Pi 2 Model B Rev 1.1

6

What DNS server is the Pi-hole host using? This will be shown in /etc/resolv.conf or in an nslookup.

7

pi@raspberrypi:~ $ sudo cat /etc/resolv.conf

Generated by resolvconf

nameserver 192.168.0.1

8

I assume that's your router. What DNS is the router using?

9

I tried it locally with the provided information from above /etc/os-release. The detection works. So it's more likely a connection/network issue as mentioned above.

chrko@ThinkPad-X230:~$ cat ./os 
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

chrko@ThinkPad-X230:~$ ./test 
Raspbian GNU/Linux 10 (buster)
Raspbian
10
  [✓] Supported OS detected
10

DNS 172.18.150.65 , 172.18.150.66 from Entel Chile

but I also tried 8.8.8.8 and 1.1.1.1 no luck! :confused:

11

WTF I´m doing wrong: (with DNS 8.8.8.8 and 1.1.1.1) instead of provider DNS 172.18.150.65 , 172.18.150.66 ???

root@raspberrypi:~# sudo curl -sSL https://install.pi-hole.net | bash

[✓] Root user check

    .;;,.
    .ccccc:,.
     :cccclll:.      ..,,
      :ccccclll.   ;ooodc
       'ccll:;ll .oooodc
         .;cll.;;looo:.
             .. ','.
            .',,,,,,'.
          .',,,,,,,,,,.
        .',,,,,,,,,,,,....
      ....''',,,,,,,'.......
    .........  ....  .........
    ..........      ..........
    ..........      ..........
    .........  ....  .........
      ........,,,,,,,'......
        ....',,,,,,,,,,,,.
           .',,,,,,,,,'.
            .',,,,,,'.
              ..'''.

[✓] Update local cache of available packages
[✓] Disk space check

[✓] Checking apt-get for upgraded packages... up to date!

[i] Installer Dependency checks...
[✓] Checking for dhcpcd5
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail
[✓] Checking for dnsutils

[✗] Unsupported OS detected
Redirecting...

  This check can be skipped by setting the environment variable PIHOLE_SKIP_OS_CHECK to true
  e.g: export PIHOLE_SKIP_OS_CHECK=true
  By setting this variable to true you acknowledge there may be issues with Pi-hole during or after the install
  If that is the case, you can feel free to ask the community on Discourse with the Community Help category:
  https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/

root@raspberrypi:~#

12

What does dig -t txt versions.pi-hole.net show for output?

13

root@raspberrypi:~# dig -t txt versions.pi-hole.net

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -t txt versions.pi-hole.net
;; global options: +cmd
;; connection timed out; no servers could be reached
root@raspberrypi:~# dig -t txt versions.pi-hole.net

That is strange. I tried also different DNS server. Any idea?
Is there any other possibility to install pi-hole?
Thank you for your help
cheers

BTW: my IP is just in case if there is a "geo blocking"

14

Does dig -t txt versions.pi-hole.net @8.8.8.8 work? And what is the DNS server set in /etc/dhcpcd.conf?

15

same at 8.8.8.8:

root@raspberrypi:~# dig -t txt versions.pi-hole.net

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -t txt versions.pi-hole.net
;; global options: +cmd
;; connection timed out; no servers could be reached

root@raspberrypi:~# /etc/dhcpcd.conf
-bash: /etc/dhcpcd.conf: Permission denied

sudo nano /etc/dhcpcd.conf 

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private

# Example static IP configuration:
#interface eth0
#static ip_address=192.168.0.10/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1

# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
16

How are you connecting? Does this device have any internet capability or an IP address?

Can you ping 8.8.8.8 and ping google.com?

17
Your output doesn't seem to match the command Dan has asked you to execute - it's specifically missing the public DNS server, both in the command and the reply. (click for quotes)

Please rerun

dig -t txt versions.pi-hole.net @8.8.8.8

and post the full output.

18

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.