Cannot access WebUI

gil80 · October 19, 2020, 3:33pm

Expected Behaviour:

log in to WebUI via 192.168.1.2/admin or pi.hole/admin as I was able to until an hour ago

Actual Behaviour:

ERR_CONNECTION_REFUSED

I ran pihole -r twice for each of the options to repair/reconfigure pihole

pihole -c shows it's running and blocking.

Debug Token:

https://tricorder.pi-hole.net/7zx44k5owl

pi@raspberrypi:~ $ sudo service lighttpd restart
pi@raspberrypi:~ $ sudo service pihole-FTL restart
pi@raspberrypi:~ $ sudo service lighttpd status -l

● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-10-20 02:35:10 AEDT; 7s ago
  Process: 4234 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
  Process: 4241 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
 Main PID: 4241 (code=exited, status=255/EXCEPTION)

Oct 20 02:35:10 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Oct 20 02:35:10 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Oct 20 02:35:10 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Oct 20 02:35:10 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Oct 20 02:35:10 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Oct 20 02:35:10 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
pi@raspberrypi:~ $
pi@raspberrypi:~ $ sudo service pihole-FTL status -l
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated)
   Active: active (exited) since Tue 2020-10-20 02:35:15 AEDT; 20s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4265 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Oct 20 02:35:14 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 20 02:35:14 raspberrypi pihole-FTL[4265]: Not running
Oct 20 02:35:14 raspberrypi su[4283]: (to pihole) root on none
Oct 20 02:35:14 raspberrypi su[4283]: pam_unix(su:session): session opened for user pihole by (uid=0)
Oct 20 02:35:15 raspberrypi pihole-FTL[4265]: FTL started!
Oct 20 02:35:15 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pi@raspberrypi:~ $

pi@raspberrypi:~ $ lighttpd -v
lighttpd/1.4.53 (ssl) - a light and fast webserver

pi@raspberrypi:~ $ lighttpd -t
2020-10-20 02:38:01: (server.c.1073) No configuration available. Try using -f option.

The only thing that comes to mind is that I probably messed up user permissions when I tried to clone a repo and got permission denied.

gil80 · October 20, 2020, 12:01am

I think I got most of it sorted but there's still an issue which I'd like help with please.

pi@raspberrypi:/var/log $ sudo systemctl status lighttpd -l

● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-10-20 10:57:25 AEDT; 44s ago
  Process: 4837 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 4844 (lighttpd)
    Tasks: 6 (limit: 2065)
   CGroup: /system.slice/lighttpd.service
           ├─4844 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
           ├─4854 /usr/bin/php-cgi
           ├─4855 /usr/bin/php-cgi
           ├─4856 /usr/bin/php-cgi
           ├─4857 /usr/bin/php-cgi
           └─4858 /usr/bin/php-cgi

Oct 20 10:57:25 raspberrypi systemd[1]: Starting Lighttpd Daemon...
Oct 20 10:57:25 raspberrypi lighttpd[4837]: 2020-10-20 10:57:25: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
Oct 20 10:57:25 raspberrypi systemd[1]: Started Lighttpd Daemon.

This line: raspberrypi lighttpd[4837]: 2020-10-20 10:57:25: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)

How to solve this please?

gil80 · October 20, 2020, 12:10am

Nope.
Spoke too soon.

pi@raspberrypi:/etc/lighttpd $ sudo systemctl status lighttpd.service

● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset:
 enabled)
   Active: failed (Result: exit-code) since Tue 2020-10-20 11:08:42 AEDT; 16s ag
o
  Process: 7109 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.co
nf (code=exited, status=255/EXCEPTION)

Oct 20 11:08:42 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100
ms expired, scheduling restart.
Oct 20 11:08:42 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job,
 restart counter is at 5.
Oct 20 11:08:42 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Oct 20 11:08:42 raspberrypi systemd[1]: lighttpd.service: Start request repeated
 too quickly.
Oct 20 11:08:42 raspberrypi systemd[1]: lighttpd.service: Failed with result 'ex
it-code'.
Oct 20 11:08:42 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.

DanSchaper · October 20, 2020, 12:22am

Run

sudo usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf

And post the output.

gil80 · October 20, 2020, 12:23am

sudo: usr/sbin/lighttpd: command not found

DanSchaper · October 20, 2020, 12:24am

sudo /usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf

Sorry, left off a slash.

gil80 · October 20, 2020, 12:35am

2020-10-20 11:24:16: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 28 pos: 1 parser failed somehow near here: mod_alias
Thanks. That command helped me to figure out what was wrong.

the mod_alias was missing from lighttpd.conf and when I added it in, I forgot to place a comma (,) at the end of the line above it.

So now it's working, but two remaining things that I'm not sure about:

-rw-r--r-- 1 root root 44 Oct 20 02:55 /etc/pihole/local.list 192.168.1.2 raspberrypi 192.168.1.2 pi.hole
Is there a command that can check the required permissions are correct for running Pihole? I'm afraid I've done something with permissions which got me to this situation in the first place.

I've attached a new debug log:
https://tricorder.pi-hole.net/ug9s9cgqe9

DanSchaper · October 20, 2020, 12:37am

Yeah, run Pi-hole.

DanSchaper · October 20, 2020, 12:40am

You have some kind of script that is adding whitelists and adlists and everything is pretty borked.

Just nuke it all, start from scratch, get it working with stock everything. Don't futz with it. Then, if you need it, add more stuff.

This is going to end up being a deeper rabbit hole than it already is and you're reaching the limit on the support burden you're placing on us.

gil80 · October 20, 2020, 1:25am

understood.
thank you for the support.

system · November 10, 2020, 1:25am

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