I did it, same result as before.
[i] Branch change has been cancelled
Type a Z instead of a Y when it asks if you are sure please
same result. I also tried the local (root) terminal (not ssh).
Another option would be to type a Y into notepad or other text editor and paste it into the terminal
I took yours 
same result
and a small "y" ... same result
1 Like
We can't replicate the behavior on our side.
What I would recommend is a fresh system install with locale set to English from the start.
Then install Pi-hole via curl and when done, update to 4.0 with the instructions above.
i will do it
- I deleted the existing installation
pihole uninstall - I checked the
locale - I checked
nano /etc/resolv.confand changed to 8.8.8.8 url -sSL https://install.pi-hole.net | bash- I checked
nano /etc/resolv.confand changed to 8.8.8.8
ZBOX ~ # echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
ZBOX ~ # pihole checkout core release/v4.0
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] y
[i] Branch change has been cancelled
same result...
I meant a system as in Operating System fresh install.
I believe that there are some issues related to the way the OS is mapping your keyboard keys.
I executed the same thing you did and on my side, it takes the Y every time.
All of us are getting the same installer from the same source.
Install the OS in English (if it's not too much) and then try installing Pi-hole.
Ok, I will try it. But not this evening.
Keep us updated.
This is a strange behavior that we've never seen before.
hope it helps...
I installed Mint 18.3 fresh in native english language.
ZBOX ~ # locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=
ZBOX ~ # nano /etc/resolv.conf
ZBOX ~ # echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
ZBOX ~ # pihole checkout core release/v4.0
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] y
[i] Branch change has been cancelled
ZBOX ~ # pihole -v
Pi-hole version is v3.3.1 (Latest: v3.3.1)
AdminLTE version is v3.3 (Latest: v3.3)
FTL version is vDev-a1b2fa0 (Latest: v3.0)
mind trying it with the -x flag so we can see what exactly fails?
pihole checkout core release/v4.0 -x
ok... here we are...
ZBOX ~ # pihole checkout core release/v4.0 -x
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] y
[✓] Fetching branches from https://github.com/pi-hole/pi-hole.git
[i] 32 branches available for Pi-hole Core
[✓] Switching to branch: 'release/v4.0' from 'refs/heads/master'
[i] Already up-to-date.
[i] Running installer to upgrade your installation
[✓] Root user check
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
[i] Testing for port 53 availability...
Port 53 is in use by dnsmasq.
In order for the installer to proceed, dnsmasq needs to be disabled.
Please re-run the installer with the following command:
curl -sSL https://install.pi-hole.net | bash -s -- --skip-DNS-port-check
ZBOX ~ # sudo /etc/.pihole/automated\ install/basic-install.sh --skip-DNS-port-check
[✓] Root user check
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
[i] Testing for port 53 availability...
Port 53 is in use by dnsmasq.
--skip-DNS-port-check flag was used. The installer will disable dnsmasq after dependencies and packages
have been downloaded, and replace dnsmasq with FTLDNS.
[i] Existing PHP installation detected : PHP version 7.0.30-0ubuntu0.16.04.1
[i] Update option selected
[✓] Disk space check
[✓] Update local cache of available packages
[✓] Checking apt-get for upgraded packages... up to date!
[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
[✓] Check for existing repository in /etc/.pihole
[✓] Update repo in /etc/.pihole
[✓] Check for existing repository in /var/www/html/admin
[✓] Update repo in /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 php7.0-common
[✓] Checking for php7.0-cgi
[✓] Checking for php7.0-sqlite3
[✓] Enabling lighttpd service to start on reboot
[✓] 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 x86_64 architecture
[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
[✓] man pages installed and database updated
[i] Checking if dnsmasq is enabled
[✓] Disabling dnsmasq from restarting when Network manager starts/restarts
[✓] Restarting Network manager
[i] Checking if dnsmasq is still running
dnsmasq still active, this is most likely due to the fact that dnsmasq
was loaded via a non convetional method. This might cause future conflicts with FTLDNS
ZBOX ~ # pihole -v
Pi-hole version is v3.3-404-g384b588 (Latest: v3.3.1)
AdminLTE version is v3.3 (Latest: v3.3)
FTL version is v3.0 (Latest: v3.0)
systemctl status dnsmasq
ZBOX ~ # systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: inactive (dead) since Thu 2018-07-26 21:00:57 CEST; 7min ago
have a look to nano /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
[ifupdown]
managed=false
You're on version/4.0 now. The version display shows the right version for the beta. v3.3-404-g384b588 means version 3.3 plus 404 commits, git hash g384b588. Note from the attached image that release/v4.0's latest commit is that same hash 384b588.
ok, but DNS-resolution still stoped
I believe, there is a release mismatch
ZBOX ~ # pihole -v
Pi-hole version is v3.3-404-g384b588 (Latest: v3.3.1)
AdminLTE version is v3.3 (Latest: v3.3)
FTL version is v3.0 (Latest: v3.0)
We'll need a new debug token since you've changed code now.
debug token: 19j3enz14t
probably the upload fails, because DNS-resolution still broken
I could send you the log file