New Pi-hole Installation Method And Sneak Peak At Front End Feature

In an effort the make it easier to install the Pi-hole, I have revamped the automated install command (in a separate branch of the project).  It’s not official yet as I am hoping some of you will be willing to test it out before I push/merge the changes.

Easier-to-remember Install Command

The first change is an installation command that can be entered via memory.  The current install command is long and ugly and requires you to either type or paste a long URL.  To that end, you can install any new Pi-hole with this command:

curl -L | bash

Automated Installer Beta: Installation Command

The new installer is streamlined and pretty.  Another nice feature is that it will help you set up a static IP address so you do not need to do this manually before running the installer.  If you want to try out the new installer (still in beta), install a fresh image of Raspbian Jessie and then run this command (notice the installation branch in the URL):

curl -s | bash


The installer will walk you though the setup and is pretty straightforward.  I also designed it so the user only needs to be around at the beginning of the installer and once the progress bar starts, no more human intervention is needed.  That is one thing that always bugged me about installers: they would start a progress bar and then stop halfway through to ask you another question.

Take a look at some of the screenshots below to visualize the experience.

pi-hole-instal1pi-hole-instal2pi-hole-instal-ip1pi-hole-ip-conflict pi-hole-new-install

One cosmetic bug is when running the installer over ssh is when the device reboots at the end, it mangles the dialog a little bit so the user might not actually recognize right away that the device restarted.  But once they do, you can just log back into the Pi at the new IP address.


Fun Front-end Feature (Sneak Peak)

Three weeks ago, I hinted at a “pong-like” front-end feature for the Pi-hole.  It is still in the works, but here is something more concrete.  You can view ads blocked in real-time using Logstalgia.  Just take a look at how many queries get blocked at

6 Replies to “New Pi-hole Installation Method And Sneak Peak At Front End Feature”

      1. It almost worked!

        Some are minor nits but for completeness:

        The first dialog of the installer asks which network and my pi only has one, and there is no asterisk in the box, wasn’t sure how to select it… but I guess it’s going to be the default

        When I answered, no, don’t use the existing dhcp address, I was prompted for subnet and gateway as expected but the confirmation at the end of that vignette only showed the typed ip address, then “Subnet: (blank)”

        The IP did not appear to have been changed. My etc/network/interfaces says only:
        iface eth0 inet manual (no additional ip,route,bcast info for eth0)

        The end of the installation did not restart my pi

        I was left with a couple of straggling commands

        kill usage etc (seems a kill command wasn’t formatted correctly?)

        cat: /tmp/piholeIP no such file or directory found (maybe that’s right?)

        The message at the end of the installer said the log is in /var/log/phole.log (typo I think you meant /pihole)

        It’s unclear to me if pihole must have it’s static ip set before running the installer, or if it can be set after. In the absence of certainty I’ve been reimaging my sd card every time because I hate to have stuff all over not knowing if some is duplicate or conflicting or whatever if I just did a reinstall

        This is newb, but I would appreciate a file in the home directory which shows where I can find the various working parts and useful commands. Here’s what I have in my “where_pihole_stuff_is.txt”:

        the script is in:
        the whitelist.txt should be placed in:
        the log is in:
        to watch what’s being blocked:
        tail /var/log/pihole.log
        older versions used daemon.log

        1. I fixed:

          -the asterisk in the interface selection (this should also fix the IP not being set)
          -the /tmp/piholeIP not found
          -the restart at the end
          -the typo for /etc/pihole/install.log

          As for the subnet showing blank, I have noticed that for some reason, the size of that window isn’t always correct so it cuts off some of the text. So it was probably there, just not visible. I’ll look into that one.

          You do not need a static address before running the installer as it will now ask you to set one up. This should help reduce the complexity and steps required to install it.

          I will also look into the where_pihole_stuff_is file. Thanks for the help and feedback!

Leave a Reply