Hello,
Thanks for this great software!
I've installed Pihole on my ORPI Zero just for the test and initially it works like charm, but after the first reboot it stops working. That is my debug token 2yocevrugz - any ideas?
Thanks!
Do you have the eth0 interface connected? The dns server is trying to connect on that interface, but can't find it:
Feb 04 05:57:22 orangepizero systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Feb 04 05:57:22 orangepizero dnsmasq[528]: dnsmasq: syntax check OK.
Feb 04 05:57:23 orangepizero dnsmasq[565]: dnsmasq: unknown interface eth0
Feb 04 05:57:23 orangepizero dnsmasq[565]: unknown interface eth0
Feb 04 05:57:23 orangepizero dnsmasq[565]: FAILED to start up
@Mcat12 yes the interface is connected, I'm able to ssh to the device after all.
Try sudo service dnsmasq restart. If that works, then for some reason it can't find the interface during startup before dnsmasq is started.
I have an Orange Pi Zero straight from the factory and will now prepare an armbian Ubuntu 16.04.1 to try to reproduce the issue.
I even cannot install Pi-hole:
::: Checking for existing repository...
::: Cloning https://github.com/pi-hole/pi-hole.git into /etc/.pihole... done!
:::
::: Checking for existing repository...
::: Cloning https://github.com/pi-hole/AdminLTE.git into /var/www/html/admin... done!
:::
::: Stopping dnsmasq service... done.
:::
::: Stopping lighttpd service... done.
::: Using Google DNS servers.
RTNETLINK answers: File exists
pi@orangepizero:~$
Oddly enough it worked on the second try (where I was using bash -x now).
Debug token after fresh installation: p66ebdi53z
Interesting:
::: IP Address Information
::: IPv6 addresses located
::: Pinging default IPv6 gateway: ping: unknown iface
Gateway Responded.
::: Pinging Internet via IPv6: ping: unknown iface
Query responded.
The Orange Pi did not manage to get working IPv6 connectivity and generated only a link-local address (not important for this test and most likely an armbian issue). However, there is a valid scope global IPv6 address in my setupVars.conf so IPv6 connectivity seems to be broken only partially.
Now I restarted the Orange Pi Zero
Debug token after reboot: 1z7s2q45rx
same problem with IPv6 as shown above
However, I cannot confirm the problem with dnsmasq:
pi@orangepizero:~$ sudo service dnsmasq status
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: active (running) since Sat 2017-02-04 22:17:45 UTC; 4min 22s ago
Process: 739 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS)
Process: 673 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
Process: 641 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 737 (dnsmasq)
CGroup: /system.slice/dnsmasq.service
└─737 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpk
Feb 04 22:17:40 orangepizero systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Feb 04 22:17:40 orangepizero dnsmasq[641]: dnsmasq: syntax check OK.
Feb 04 22:17:45 orangepizero dnsmasq[739]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
Feb 04 22:17:45 orangepizero systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
@Wizzi_Lalev Comparing our debug logs, I realize that we have everything now quite similar with one single difference that might be important! Where did you get this image? Have you tried using an image that was not marked as dev ?
My OS information log
BOARD=orangepizero BOARD_NAME="Orange Pi Zero" VERSION=5.25 LINUXFAMILY=sun8i BRANCH=default <---------------------------- ARCH=arm IMAGE_TYPE=stable DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
Your OS information
BOARD=orangepizero BOARD_NAME="Orange Pi Zero" VERSION=5.25 LINUXFAMILY=sun8i BRANCH=dev <---------------------------- ARCH=arm IMAGE_TYPE=stable DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
@DL6ER Thanks for your efforts, initially I've started with the dev package from Armbian - I know it is risky but newer kernel is always better - sort of.... 
After few more try/error rounds I've decided to start from scratch using the legacy kernel and here the things start to become more interesting.
So:
OS version: Debian Jessie Server (legacy kernel) - this image was downloaded directly from the Armbian site like the previous one
Board: Orange Pi Zero
As many of the users here, my local network is based on WIFI router - which is managing my DHCP, so after a fresh install of Armbian, full package update and simple root password change I've started with assigning a static IP to the board. My primary router is located at 192.168.1.1, it's DHCP pool is defined as follows: 192.168.1.50-255. So using nmtui I've set the following configuration to ORPi's eth0 interface:
IPaddress (IPv4): 192.168.1.3/24
Default Gateway: 192.168.1.1
DNS 1: ISP primary DNS
DNS 2: ISP secondary DNS
All of these configurations are saved and the system was rebooted. After the reboot newly assigned IP address was used for SSH connection (please note that the pihole is not installed at this point). There was working ping and internet access!
Next step was to install PiHole using:
curl -sSL https://install.pi-hole.net | bash
This command was executed as root user (just in case) and I've got very similar result as you
::: Stopping lighttpd service... done.
::: Using Google DNS servers.
RTNETLINK answers: File exists
So the command was executed again and the package was installed successfully.
Here is good place to mention one more strange thing!
There was a screen with message saying that my current configuration using DHCP assigned address (this is the strange part - because the IP address of the board is static) is not optimal and may cause problems. After that I was asked to verify the IP address (192.168.1.3/24) and to choose DNS servers - at this step I've confirm the IP address and the both DNS servers were added as custom (again my ISP DNS serves) and voala the package was installed and the admin panel was accessible.
At this point I've decided that one reboot will be nice and once the board was back online and the SSH connection was re-established something very strange was added to my "greeting" header
___ ____ _ _____
/ _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___
| | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \
| |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) |
\___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/
|___/
Welcome to ARMBIAN 5.25 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i
System load: 0.36 Up time: 1 min
Memory usage: 10 % of 494Mb IP: 192.168.1.3,192.168.1.3
CPU temp: 39°C
Usage of /: 4% of 29G
Last login: Sun Feb 5 01:15:44 2017 from 192.168.1.76
Do you notice the IP address? Quick check with nmtui shows 2 eth0 connections - first one is the manual configuration done by me few minutes earlier (this connection is set to "Auto connect") and the second one almost the same but without DNS records and without "Auto connect" selected....
More interesting is that the [ - ] lighttpd service is not running but the [ + ] dnsmasq service is OK.
I'm using *nix based systems for more than 10 years and this situation is driving me crazy 
Any ideas?
P.S. Excuse my English - it's not perfect...
EDIT:
After few more restarts I've noticed that I have 3 eth0 records in nmtui.... Something is very wrong - let's fix it
Okay, I now read:
That might be the major difference to my test, since I used the Pi-hole installer for setting a static IP address.
I wiped out the SD card and started afresh - I still use the Ubuntu image, start with no Pi-hole installed and no static address set so far. I did the following now:
After the reboot, I see the very same problem you were seeing (two IP addresses):
pi@orangepizero:~$ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
inet 192.168.2.178/32 brd 192.168.2.178 scope global eth0
inet 192.168.2.178/24 brd 192.168.2.255 scope global eth0
After a second reboot, the double IPs on the welcome screen issue are gone and everything seems functional:
pi@orangepizero:~$ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
inet 192.168.2.178/24 brd 192.168.2.255 scope global eth0
Afterwards, I installed Pi-hole using the installer script. Everything went smooth, so I went for another reboot. lighttpd and dnsmasq started successfully and I was able to use the Pi-hole as usual.