I only set 2 DNS servers during installation, that's it. I didn't mess with the gateway. I'm only confused about the setup changing my network interface or anything like that. The update / upgrade stuff worked before, why wouldn't it work anymore after the PiHole installation?
Furthermore, the pihole command can't be found. That's weird since I just installed PiHole.
@jacob.salmela I downloaded the script and executed your commands, but this didn't work either. The pihole command still isn't available and the install log is still empty.
@jacob.salmela So.. somehow I made it work. I tried so many different installation variations, formatted the sd card and reflashed it countless times, and now it somehow worked. Don't ask me why it works now.
So as you can see, the installation always stopped at a random point of the script. This time it stopped before I executed "sudo nano /etc/resolve.conf":
The fix is to just execute sudo bash basic-install.sh as often as possible until the pi went through the whole script.
I don't know why it stops here and there, but it took me hours of formatting and reflashing until I realized it's only a random stop. Now, it works and I can finally access the portal.
It's good, that you can already limit the problem. But can you reproduce it? I mean, I did a fresh installation / flash of Stretch lite onto the sd card and only made the necessary update as well as upgrade. I didn't touch any config settings of the pi. So why would it have problems with dependencies or the script would stop in between? Is Stretch still too new?
There shouldn't be any conflicts since I haven't installed or touched anything else and Stretch was completely new installed..
Try reinstalling with the latest (April) release of Raspbian Stretch. Maybe the APT mirrors that your install decided to use were bad, or gave different packages. Or maybe your network is set up differently.
so finally I got it working. I had to re-execute the installation script couple of times, until it reached the end.
Now it works. However, the setup that a user posted here doesn't work for me.
Every time, I follow this user's guide, I get an DNS_PROBE_FINISHED_NO_INTERNET error.
When I set these settings, my Chrome browser gives me an ERR_NETWORK_CHANGED and afterwards a DNS_PROBE_FINISHED_NO_INTERNET error.
What I found out is that the "problem" already starts with changing the DNS server under General Config: If I have my initial values set and only change the DNS server from 1.1.1.1 to my 192.168.1.114, I get this DNS_PROBE_FINISHED_NO_INTERNET error. However, I can access websites via their single IP, this works. But something like vimeo.com doesn't work.
After lots of try & error, I found a solution. This config now seems to work and blocks adds (using Edge browser):
System > General Setup > DNS Server Settings > DNS servers: 1.1.1.1 (gateway: none; nothing else changed)
Services > DNS Forwarder > Disabled
Services > DNS Resolver > General Settings > Enabled
Services > DHCP Server > Enabled
Services > DHCP Server > Servers > DNS servers: 192.168.1.114 (Pihole IP)
This does the trick, somehow.
I don't know if this config makes sense because now I have two DNS resolvers working on the network. But the funny thing is: when I turn off the Pi, my Internet connection is gone.
