I'd like to know how to proceed with the following:
I've proudly installed PiHole with Docker, using a tutorial on docker-compose, however never managed to log in the web interface.
Yet, PiHole and Docker are running. I even managed to complete updates.
Initially tried several methods (including the 3 ways shown on this site) to log in web interface with different browsers, wanted to add elements to my blacklist, never managed to do that! Looked through every tutorial I could find, read all info and find myself a bit lost and still not able to log my
PiHole admin console.
I used dhcpcd.conf to induce a static IP which I had my router's DNS point towards and this seems to create issues as
Initial issue: I have to remove my PiHole IP and point the router's DNS to 8.8.8.8 in order to allow connections for updates, other connexions as well. Then PiHole isn't a network angel anymore during that time.
I read that the console needs lighttpd, wich I didn't have.
So, I have a docker-composed a lighttpd container
which will not start because what I believe is a bridging issue,
this seems consistent with the fact that I must alter my router to proceed with upgrades.
I then curled an new pihole, installed everything (php, lighttpd and the whole nine yards),
still wouldn't connect. Then, I realized I had never asked to stop PiHole in docker and,
Yep!, I had two PiHoles and their DNS service running. Thus, I can run pihole both from the Pi OS and from docker simultaneously or separately (tested 3 cases of both) and operate them from command line and still never use the console ! lighttpd runs from piOS but still not from docker.
My Pi OS has no desktop and is quite fast for a 3B+, accessing from the web console would make PiHole more efficient and fun.
Refusing to connect issue remains with or without docker and lighttpd.
Even if ports are defined in docker-compose, no change.
Therefore my understanding is : some type of netwrok bridging somewhere in a *.conf file might have to be set to solve this lighttpd container not working in docker? Not sure, still would not explain why
I must still redirect the router from PiHole to 8.8.8.8 when need upgrades or use docker-compose! Will remove docker since the hardware's dedicated. I'll still user docker elsewhere.
Meanwhile I'm reading what I can find how to crawl my way out of this.
I've never used forums in my life, where should I head now?
Late update. After stoping and removing docker and pihole container in command line. I did the native install with curl, reset my pihole admin password, made sure my router pointed towards pihole and ... finally access the web console from any browser. So I typed the new password and started pihole’s dhcp server, after having stoped the router’s dhcp. The lesson I learned is that docker is more touchy than expected. I still dont understand all the reasons behind not being able to network through docker.