Lighttpd running and connexions aren't allowed

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. :cloud_with_rain: 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 ... :sunny: finally access the web console from any browser. :small_orange_diamond: 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.

Now I figured how to input code in here :sun_with_face:

To summarize:
I had a pihole container working in docker, no console access.
Cleaned everything up (stoped and rm docker + container)
and now run pihole on Raspbian without desktop and access
the console from a browswer.
Still unable to proceed with upgrades without manualy changing the router's DNS to 8.8.8.8.

I ran this in command line

pi@Sensornet:~ $ pihole -g
sudo: unable to resolve host Sensornet: Temporary failure in name resolution
[✗] DNS resolution is currently unavailable
[i] Time until retry: 101

MEANWHILE I REPOINTED THE ROUTER'S DNS TO 8.8.8.8 AND THEN:

[✓] DNS resolution is now available

[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range

[✓] Preparing new gravity database
[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: Retrieval successful
[i] Received 57260 domains

[i] Target: https://mirror1.malwaredomains.com/files/justdomains
[✓] Status: No changes detected
[i] Received 26854 domains

[✓] Storing downloaded domains in new gravity database
[✓] Building tree
[✓] Swapping databases
[i] Number of gravity domains: 84114 (84071 unique domains)
[i] Number of exact blacklisted domains: 4
[i] Number of regex blacklist filters: 1
[i] Number of exact whitelisted domains: 0
[i] Number of regex whitelist filters: 0
[✓] Flushing DNS cache
[✓] Cleaning up stray matter

[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

BUT NO CONSOLE UNTIL I RESET THE ROUTER TO PI'S STATIC IP,
THEN I RAN -d:

pi@Sensornet:~ $ pihole -d

BUT, PiHole will not send a token since:

[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log

Where we're at now:
I'm kind of back with the same issue allthough I now access the web console.
Docker will wait until this is figured out. This means I was wrong including docker in my request for help, I honestly didn't know then.
I'm reading on DNS and DHCP, must have missed something.
Other reading suggestions or more investigating steps would be awesome.
Is there something usefull I can extract from that log?
Is there something usefull you guys want from that log?

If I read that right you switched from docker to regular install?

Just to make sure I understood this right you were getting "DNS resolution is currently unavailable" and retries until you pointed your router back to google?

I believe the indicates the pi's DNS maybe miscofigured, it has to point to an outside DNS like google, not your router, to avoid an infinite loop that cannot self start.

Pi-hole DNS -> Outside world
Router DNS -> Pi-hole
Other non-Pi-hole computers -> Router DNS

Thx dignic,
Yes for config change.
Reverted to regular install to reduce potential issues.
Will try your suggestions today, and still read more on this.
Being new in this Linux world is a lot of fun allthough solving issues can be challenging
Thx again

So I checked:

Which was the configuration I last set.
Then, tried to update gravity list through web console and failed.
Tried to update in command line:

pi@Sensornet:~ $ sudo pihole -g
sudo: unable to resolve host Sensornet: Temporary failure in name resolution
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available

Thus:
Pi-hole DNS -> Outside world
Router DNS -> Pi-hole
Other non-Pi-hole computers -> Router DNS
Wasn't where I should look eventhough info points that way!
And can conclude there is no infinite loop.

At this point I still have to modify the router for upgrades and maintenance on Pi-Hole (Sensornet in my case):
Pi-hole DNS -> Outside world
Router DNS -> Pi-hole (altered to outside world only when updating!!)
Other non-Pi-hole computers -> Router DNS

I noticed ivp6 isn't enabled on both router and Pihole.
I'm not convinced I have to enable ivp6 for now.
Am I wrong?

I will investigate :sun_with_face: