pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster) Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
Post Reply
zorro
Posts: 5
Joined: Mon Apr 19, 2021 11:38 am

pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by zorro »

For now 2 days I tried to install pihole on PI 3 (DietPi_RPi-ARMv8-Buster) without any success. I did this already on Pi 2 and on Odroid C2 without any problems:

Code: Select all

Checking URL: https://www.internic.net/domain/named.root
                              │  - Command: curl -ILfvm 10 https://www.internic.net/domain/named.root
                              │  - Exit code: 28
                              │  - DietPi version: v7.0.2 (MichaIng/master) | HW_MODEL: 3 | HW_ARCH: 3 | DISTRO: 5
                              │  - Image creator: DietPi Core Team
                              │  - Pre-image: Raspberry Pi OS Lite (64-bit)
                              │  - Error log:
                              │ * Expire in 0 ms for 6 (transfer 0x55aeea4c30)
                              │ * Expire in 10000 ms for 8 (transfer 0x55aeea4c30)
                              │ * Expire in 1 ms for 1 (transfer 0x55aeea4c30)
                              │   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                              │                                  Dload  Upload   Total   Spent    Left  Speed
                              │ ^M  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Expire in 0 ms for 1 (transfer
                              │ 0x55aeea4c30)
                              │ * Expire in 2 ms for 1 (transfer 0x55aeea4c30)
                              │ * Expire in 0 ms for 1 (transfer 0x55aeea4c30)

                                (...)

                                * Closing connection 0
                              │ curl: (28) Resolving timed out after 10000 milliseconds
                              │
                              │                        Retry          : Re-run the last command that failed                 ↑
                              │                        DietPi-Config  : Edit network, APT/NTP mirror settings etc           ▮
                              │
                              │
                              │                                  <Ok>                                      <Exit>
This is what I did:
1) Downloaded new Image from DietPi-Website, written it to SDRAM and double checked it (dcfldd ...)
2) Inserted SDRAM into Pi 3, started PI 3, updated successfully!, assigned static IP ...
3) Launched diepi-software, selected unbound and pihole, installation started (unbound without any problems, pihole cf. above!)
4) Selected "Retry : Re-run the last command that failed" yielded the same result.
5) I did not find any helpful hints in the logs (journalctl -f ...)

Are the problems (which?) between my ears, have some links changed ...?
Any ideas or hints are really appreciated.
Thank you very much!
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by Joulinar »

did you try to install PiHole without unbound? The step you are failing is the unbound config where the system is trying to download unbound root server information from https://www.internic.net/domain/named.root

You have issues to resolve the host name correctly.

Code: Select all

curl: (28) Resolving timed out after 10000 milliseconds
Maybe you can try to change DNS server on your local device pointing to one of the global DNS provider like Quad9, Cloudflare or Google DNS
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
zorro
Posts: 5
Joined: Mon Apr 19, 2021 11:38 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by zorro »

Yes, I tried to install with and without unbound. No change! :-(

What can be the reason for this resolv problem:
- All "apt update/upgrade" went perfect
- I use the DNS given by my provider (did'nt change nothing!)
- I did a clean and successful installation of pihole and unbound in a virtualbox DiePi installation on my linux workstation.
- All use the same FritzBox! and hence the same DNS system.
Any ideas?
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by Joulinar »

Are you able to open the Domain on you desktop computer? Usually if you install Pihole without unbound, the file should not be downloaded
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
zorro
Posts: 5
Joined: Mon Apr 19, 2021 11:38 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by zorro »

The Pi uses

Code: Select all

root@DietPi:~# cat /etc/resolv.conf
nameserver 9.9.9.9
nameserver 149.112.112.112
and I will try to change this.
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by Joulinar »

This is global Quad9 DNS and should be totally fine
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
zorro
Posts: 5
Joined: Mon Apr 19, 2021 11:38 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by zorro »

> Are you able to open the Domain on you desktop computer?
Which Domain do you mean?
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by Joulinar »

The one which is failing https://www.internic.net/domain/named.root

This is the command you have posted above

Code: Select all

curl -ILfvm 10 https://www.internic.net/domain/named.root
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
zorro
Posts: 5
Joined: Mon Apr 19, 2021 11:38 am

Re: pihole not installable (Pi 3, DietPi_RPi-ARMv8-Buster)

Post by zorro »

Problem solved.
I shoudn't change the default DHCP network settings ;-).
Thank you for your kind support
Post Reply