[SOLVED] - PiHole 4.0 4.1 - Question(s)

Hello,

I have a hard coded version of pihole still running on my Raspberry Pi. I see that PiHole 4.0 is released. Does this mean everything is back up and running from previous instances where Dnsmasq was not working well.

I feel like I need to do a fresh install on a fresh SD card as I am not sure if my current version will update properly with the update command.

Can anyone assist, it has been a little bit since I have touched pihole

Current info

Pi-hole Version vDev (HEAD, v3.2.1-0-ge602008) Web Interface Version vDev (HEAD, v3.2.1-0-g31dddd8) FTL Version vDev (v2.13.2 , v2.13.2 )

Thanks

run the following command to get back to the master branch and 4.1
pihole checkout master

Starting with V4 of Pi-Hole, dnsmasq is embedded in pihole-FTL and dnsmasq does not run as a separate process.

Awesome. I will try that later tonight or tomorrow. Would there be a point to make a SD 1:1 backup before running the master command or do you think I will be OK?

Sweet! I have been looking forward to an update for a while. Love the pi-hole team !

Backups never hurt, but the transfer to master should go smoothly.

You guys rule. Thanks for the information. I will mark the topic as 'solved' once I get everything rocking. I will follow up too!
Pumped to get this going, hope I can tomorrow (day off)

OK.
SD card backed up. Going to try using the same card and the update command you said. (fingers crossed). I will post any results if there are questions or something breaks

OK so that broke something

_**Please note that changing branches severely alters your Pi-hole subsystems**_
_**  Features that work on the master branch, may not on a development branch**_
_**  This feature is NOT supported unless a Pi-hole developer explicitly asks!**_
_**  Have you read and understood this? [y/N]**_
_**[i] Shortcut "master" detected - checking out master branches...**_
_**  [i] Pi-hole core**_
_**  [✓] Switching to branch: 'master' from 'refs/heads/master'**_
_**  [i] Already up-to-date.**_
_**  [i] Web interface**_
_**  [✓] Switching to branch: 'master' from 'refs/heads/master'**_
_**  [i] Already up-to-date.**_
_**  [✓] Detected ARM-hf architecture (armv7+)**_
_**  [✓] Installing FTL**_
_** $ pihole -up**_
_**  [i] Checking for updates...**_
_**  [i] Pi-hole Core:     up to date**_
_**  [i] FTL:              update available**_

_**  [i] FTL out of date**_

_**  [i] FTL Checks...**_

_**  [i] Downloading and Installing FTL...curl: (22) The requested URL returned error: 404 Not Found**_
_**  [✗] Downloading and Installing FTL**_
_**  Error: URL https://github.com/pi-hole/FTL/releases/download/v4.1/ not found**_

Current PiHole state:

**Pi-hole Version**  v4.1  **Web Interface Version**  v4.1  **FTL Version**  vDev (master , vDev-d42bcb7 )

### FTL Information

The FTL service is offline!

I have ran
pihole -r
here is the output

[i] Existing PHP installation detected : PHP version 5.6.33-0+deb8u1
  [i] Repair option selected
  [✓] Disk space check
  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... 159 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [i] Checking for sqlite3 (will be installed)
  [✓] Checking for libcap2-bin
  [i] Checking for dns-root-data (will be installed)
  [i] Checking for resolvconf (will be installed)
  [✓] Checking for lighttpd
  [✓] Checking for php5-common
  [✓] Checking for php5-cgi
  [✓] Checking for php5-sqlite
  [✓] Enabling lighttpd service to start on reboot...
  [✓] Checking for user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...

  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [✗] Downloading and Installing FTL
  Error: Unable to get latest release location from GitHub
  [✗] FTL Engine not installed
  [✓] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service...
  [✓] Enabling lighttpd service to start on reboot...
  [i] Restarting services...
  [✓] Enabling pihole-FTL service to start on reboot...
  [✓] Starting pihole-FTL service...
  [✓] Deleting existing list cache
  [i] Pi-hole blocking is enabled
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 159551
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 136324
  [i] Number of whitelisted domains: 10
  [i] Number of blacklisted domains: 4
  [i] Number of regex filters: 1
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [i] Pi-hole blocking will be enabled
  [i] Enabling blocking
  [✓] Reloading DNS service
  [✓] Pi-hole Enabled

  [i] The install log is located at: /etc/pihole/install.log
Update Complete!

  Current Pi-hole version is v4.1
  Current AdminLTE version is v4.1
  Current FTL version is vDev-d42bcb7

OK so I rebooted after the repair and SSH into the pi
ran
pihole -up
and here is the output

 [i] Existing PHP installation detected : PHP version 5.6.33-0+deb8u1
  [i] Performing unattended setup, no whiptail dialogs will be displayed
  [✓] Disk space check
  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... 159 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for lighttpd
  [✓] Checking for php5-common
  [✓] Checking for php5-cgi
  [✓] Checking for php5-sqlite

  [✓] Enabling lighttpd service to start on reboot...
  [✓] Checking for user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...

  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [✓] Downloading and Installing FTL
  [i] FTL can now resolve DNS Queries without dnsmasq running separately
  [✓] Stopping dnsmasq service...
  [✓] Disabling dnsmasq service...
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
  [✓] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service...
  [✓] Enabling lighttpd service to start on reboot...
  [i] Restarting services...
  [✓] Enabling pihole-FTL service to start on reboot...
  [✓] Starting pihole-FTL service...
  [✓] Deleting existing list cache
  [i] Pi-hole blocking is enabled
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 159551
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 136324
  [i] Number of whitelisted domains: 10
  [i] Number of blacklisted domains: 4
  [i] Number of regex filters: 1
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

  [i] The install log is located at: /etc/pihole/install.log
Update Complete!

  Current Pi-hole version is v4.1
  Current AdminLTE version is v4.1
  Current FTL version is v4.1

Pihole Current State:

**Pi-hole Version**  v4.1  **Web Interface Version**  v4.1  **FTL Version**  v4.1

So I think I got it, guess it took

  1. pihole checkout master
  2. reboot
  3. pihole -r
  4. reboot
  5. pihole -up
  6. reboot
  7. Success ???

I think I am good to go, are there any other settings I should be checking ?

It looks like success.

There are a number of new features in V4.1 compared to your previous version. The documentation is a good read. Follow the menus on the left of the referenced page.

https://docs.pi-hole.net/ftldns/

Awesome!
Thanks. I will do some reading... I already see improvement testing various news (ad) sites. Thanks for all the help. I think I am going to donate to the cause, this app is so dam good. Community is even better !

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