Problem accessing admin page

Please follow the below template, it will help us to help you!

Expected Behaviour:

Problem accessing the admin page.

Actual Behaviour:

Can't get to the admin page, dnsmasq and lighttpd failed.
Whenever I try to access it with http://pi.hole/admin or with the IP address, I get:

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

Debug Token:

65a2ipjijb

Something is either preventing lighttpd from listening on port 80, or another error is preventing it from starting.

Your debug log doesn't show which ports are in use, so please run these commands from the Pi-Hole host terminal and post the results:

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471’

sudo service lighttpd status

First command:

 sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471’
        tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      10773/pihole-FTL
        tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      10773/pihole-FTL
        tcp6       0      0 ::1:4711                :::*                    LISTEN      10773/pihole-FTL
        tcp6       0      0 :::53                   :::*                    LISTEN      10773/pihole-FTL
        udp        0      0 0.0.0.0:53              0.0.0.0:*                           10773/pihole-FTL
        udp6       0      0 :::53                   :::*                                10773/pihole-FTL

Second command:

sudo service lighttpd status
Redirecting to /bin/systemctl status lighttpd.service
● lighttpd.service - Lightning Fast Webserver With Light System Requirements
   Loaded: loaded (/usr/lib/systemd/system/lighttpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-11-02 17:45:07 EDT; 1h 12min ago
  Process: 12747 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
 Main PID: 12747 (code=exited, status=255)

Nov 02 17:45:07 pi-hole systemd[1]: Started Lightning Fast Webserver With Light System Requirements.
Nov 02 17:45:07 pi-hole systemd[1]: Starting Lightning Fast Webserver With Light System Requirements...
Nov 02 17:45:07 pi-hole lighttpd[12747]: 2018-11-02 17:45:07: (configfile.c.1462) commaned "cat external.conf 2>/dev/null" exited non-zero: 1
Nov 02 17:45:07 pi-hole lighttpd[12747]: 2018-11-02 17:45:07: (configfile.c.1277) source: /etc/lighttpd/lighttpd.conf line: 94 pos: 1 parser failed somehow near here: (EOL)
Nov 02 17:45:07 pi-hole systemd[1]: lighttpd.service: main process exited, code=exited, status=255/n/a
Nov 02 17:45:07 pi-hole systemd[1]: Unit lighttpd.service entered failed state.
Nov 02 17:45:07 pi-hole systemd[1]: lighttpd.service failed.

Try:

sudo touch /etc/lighttpd/external.conf

sudo service lighttpd restart

And check again:

sudo service lighttpd status -l

Ps. did you copy/paste that status output ?
Am asking because "commaned" is spelled wrong :smiley: ... I think

Nice the console is now showing! :smile: Thank you...

dnsmasq daemon is still failed though:

**Outpout of service dnsmasq status -l:**
Redirecting to /bin/systemctl status  -l dnsmasq.service
● dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-11-03 08:14:56 EDT; 10s ago
  Process: 17790 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=2)
 Main PID: 17790 (code=exited, status=2)

Nov 03 08:14:56 pi-hole systemd[1]: Started DNS caching server..
Nov 03 08:14:56 pi-hole systemd[1]: Starting DNS caching server....
Nov 03 08:14:56 pi-hole dnsmasq[17790]: dnsmasq: failed to create listening socket for port 53: Address already in use
Nov 03 08:14:56 pi-hole systemd[1]: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 03 08:14:56 pi-hole systemd[1]: Unit dnsmasq.service entered failed state.
Nov 03 08:14:56 pi-hole systemd[1]: dnsmasq.service failed.

And yeah, I copy/pasted the outpout so I think there's a little typo :stuck_out_tongue:

The dnsmasq part was replaced by Pi-hole's own version of the dnsmasq source code so you wont need to run dnsmasq anymore as a separate process/daemon:

https://docs.pi-hole.net/ftldns/dns-resolver/

Whats output for below one ?

pi@noads:~ $ pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
1 Like

Two beautiful green checks! :slight_smile:
Thank you guys for all the help, really appreciated.

2 Likes

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.