New installation fails

Help
19

The dev branch as Dan said, is under heavy testing and it's not meant to be used as an end/stable product by the users.

You were prompted by this at branch switching:
image

What I would recommend is switching to the FTLDNS branch by following these steps:

First you need to edit your /etc/resolve.conf in order for your DNS resolution to work.

Edit the file with sudo nano /etc/resolv.conf and change 127.0.0.1 to 1.1.1.1 or any public DNS you like.

  1. start from scratch.
    Install the stable version with curl -sSL https://install.pi-hole.net | bash

  2. IF you want to switch to FTLDNS after you installed the master, use the same commands specified in the guides:

echo "FTLDNS" | sudo tee /etc/pihole/ftlbranch
pihole checkout core FTLDNS
pihole checkout web FTLDNS

Due to the nature of your environment and the presence of Network Manager, after FTLDNS is installed, you need to make sure that Network Manager does NOT enable dnsmasq (at reboot) before FTLDNS. In order to achieve that, you need to edit

/etc/NetworkManager/NetworkManager.conf

And comment out or delete the line that has dns=dnsmasq.

Then you need to restart NetworkManager in order for the new settings (without dnsmasq as resolver) to be applied:

sudo systemctl reload-or-restart NetworkManager

If after reboot, your /admin/ interface is showing Lost Connection To Api and DNS resolution is not working, then that means that FTLDNS is offline.

Check to see if dnsmasq is running with

sudo systemctl status dnsmasq

It should say
image

If dnsmasq is active you need to stop it and restart FTLDNS in order for the DNS resolution to work properly.

sudo systemctl stop dnsmasq
sudo systemctl restart pihole-FTL.service

Once you have done this, you need to find out why dnsmasq is starting.

If you don't use dnsmasq in your own setup, it is safe to uninstall it if you so chose to do so.

sudo apt remove dnsmasq however since it's a dependency of Network Manager, it MIGHT be re-installed if your environment is set-up for auto updates and it will break FTLDNS again.

If you did everything right, dnsmasq shouldn't be a problem once on FTLDNS and the disable method above.

2 Likes