Unable to access Pi-Hole webGUI

    I installed Pi-Hole a year ago or so via Docker and it has been working fine, but for some reason I am no longer able to access the webGUI of Pi-Hole. I don't know when the problem began because I haven't opened the GUI in a while but it did work before.


    When I try to open 192.168.0.3/admin I get this error:

    Code
    This site can’t be reached
192.168.0.3 refused to connect.
ERR_CONNECTION_REFUSED


    And if I log in to the Pi-Hole container and list the open ports there is indeed no open http port:

    Code
    lsof -i -P -n | grep LISTEN
pihole-FT 528 root    5u  IPv4 27823662      0t0  TCP *:53 (LISTEN)
pihole-FT 528 root    7u  IPv6 27823664      0t0  TCP *:53 (LISTEN)
pihole-FT 528 root   10u  IPv4 27822681      0t0  TCP 127.0.0.1:4711 (LISTEN)

    Hmm I took a peek inside pihole-FTL.log just now and it seems that there is a recurring issue where "FTL" crashes with 254 second intervals?


    Code
    [2020-09-21 10:37:05.662 534M] Shutting down...
[2020-09-21 10:37:05.662 534M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-09-21 10:37:05.662 534M] ---------------------------->  FTL crashed!  <----------------------------
[2020-09-21 10:37:05.662 534M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-09-21 10:37:05.662 534M] Please report a bug at https://github.com/pi-hole/FTL/issues
[2020-09-21 10:37:05.662 534M] and include in your report already the following details:
[2020-09-21 10:37:05.662 534M] FTL has been running for 254 seconds

    Ok so I figured a reinstall would be easier and faster than trying to troubleshoot the issue and I did the reinstall by following this guide found here on OMV forums: HOWTO-PiHole.pdf


    However, it did not help. The pihole container is still restarting with 254 second intervals. This is a snippet of what I can see in the Container log:


    Code
    ::: Testing pihole-FTL DNS: FTL started!
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Docker start setup complete
[✗] DNS resolution is currently unavailable

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden