Install stops after 2seconds of showing blue progress bar screen

Expected Behaviour:

Easy peasy fresh install of pihole.
unistall pihole > reboot > install pihole > happy me

Actual Behaviour:

Uninstalled Pihole > reboot > install pihole > nope.
Tried running the install with "curl -sSL https://install.pi-hole.net | bash" and it just stops after showing the first blue screen with progress bar for only 2 seconds and then sends me back to the command line.

Debug Token:

N/A as pihole isn't installed anymore.

Running on a RPi 2 with OSMC, which is up-to-date.
I really hope to get this working again because my ISP is sending me a new Modem/Router-combo in which I can't change the DNS anymore (yeah thanks guys..) so I wanted a fresh Pihole running to handle the dhcp and dns.

Thanks in advance.

Run sudo apt install iproute2 and sudo apt install git then run the pi-hole install command again.

I think when you removed it, you deleted some dependencies (git and iproute2) that might have been needed by the system too and that messed up some things.

The installer script calls git as part of the install process.

1 Like

Allright, thanks this seemed to help me a lot!
After trying to "sudo apt install iproute2" it told me

Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

after doing that iproute2 installed and it said git was already the latest version.
Looks like the install went fine, thank you!
But now I get the big "Lost connection to API" message on the dashboard.

I ran "pihole -d"

debug token: 4ur82tg2ww

Run a pihole -r and re-configure.

Okay, I already did that actually before I ran pihole -d but that didn't do much then.
Ran apt-get update and apt-get dist-upgrade just to be sure and then ran pihole -r again, reconfigured and like magic it is working again somehow :smiley:

Thank you for the help.

This command only runs a series of tests and prompts the user for debug log upload.

Glad it works now :slight_smile:

I ran pihole -r before I ran pihole -d but I didn't went through the reconfigure option but the other option (always choosing the easy way out LOL), so that might have been the problem for me thinking running pihole -r before didn't do much :zipper_mouth_face:

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