Lighttpd has gone bonkers: No web UI, pihole -r does not fix, service is active (exited), and more

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

Expected Behaviour:

  1. Web interface, of course.
  2. sudo pihole -r (re?) installs lighttpd.
  3. sudo pihole -up would fix or update the system.
  4. sudo apt-get remove lighttpd would remove it.
  5. sudo apt-get install lighttpd would install it.

Actual Behaviour:

  1. No web interface!
  2. sudo pihole -r selecting repair option returns this:
  [i] Existing PHP installation detected : PHP version 7.2.13-1+0~20181207100540.13+stretch~1.gbpf57305
  [i] Repair option selected
  [✓] Disk space check
  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... up to date!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [i] Checking for lighttpd (will be installed)
  [✓] Checking for php7.2-common
  [✓] Checking for php7.2-cgi
  [✓] Checking for php7.2-sqlite3

and then does not actually install lighttpd. I get to the "installing packages" console screen, hangs at 0% for a few seconds, and kicks back to console, no fix.

  1. The command returns much the same as the -r option, adding this at the top:
  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
  [i] FTL:		update available
  [i] FTL out of date, it will be updated by the installer.

And at the bottom:

Unable to complete update, please contact Pi-hole support

And here I am! :grinning:

  1. The console command returns this:
Package 'lighttpd' is not installed, so not removed
  1. sudo apt-get install lighttpd returns this:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 apache2 : Depends: apache2-utils (= 2.4.25-3+deb9u6) but it is not going to be installed
           Recommends: ssl-cert but it is not going to be installed
 apache2-bin : Depends: libaprutil1 (>= 1.5.0) but it is not going to be installed
               Depends: libaprutil1-dbd-sqlite3 but it is not going to be installed or
                        libaprutil1-dbd-mysql but it is not going to be installed or
                        libaprutil1-dbd-odbc but it is not going to be installed or
                        libaprutil1-dbd-pgsql but it is not going to be installed or
                        libaprutil1-dbd-freetds but it is not installable
               Depends: libaprutil1-ldap but it is not going to be installed
 libssl1.1 : Breaks: lighttpd (< 1.4.49-2) but 1.4.45-1 is to be installed
 php7.2-cli : Depends: php7.2-readline but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Looking at this error message again, the libssl1.1 breaks lighttpd part is concerning, and may be the source of my woes. However, I have not yet looked into this, and for all I know it's a dependency of the nextcloud installation.

Other info:

I am running the pi-hole dual-style with LAN and VPN, inside a nextcloudpi system image. Absolutely everything is working like a charm, except for the lighttpd service and web interface, which was working in the past, along with everything else. From the start I changed the port in /etc/lighttpd/lighttpd.conf to be 8087, my preferred alternative, since nextcloudpi is already using 80. I recently also copied the contents over to /etc/lighttpd/external.conf, and commented out the last lines, as I read somewhere that it may help. It did not.

Result of sudo service lighttpd status -l

● lighttpd.service - LSB: Start the lighttpd web server.
   Loaded: loaded (/etc/init.d/lighttpd; generated; vendor preset: enabled)
   Active: active (exited) since Sun 2019-01-06 21:35:40 UTC; 31min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 629 ExecStart=/etc/init.d/lighttpd start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/lighttpd.service

Jan 06 21:35:40 NextCloudPi systemd[1]: Starting LSB: Start the lighttpd web server....
Jan 06 21:35:40 NextCloudPi systemd[1]: Started LSB: Start the lighttpd web server..

Before I tinkered around and got the service into this state, the previous command returned a result that the service was "masked". I issued commands to unmask it, and now this is the result. No changes after several reboots.

Hopefully this isn't too much info, but as a semi-noobie, this problem has really thrown me for a loop. I love this pi-hole stuff, and if I can get the web interface working again without a full pi-hole re-install, that'd be great! Thanks in advance.

Debug Token:

xbgn7wxjfp

Edit because I figured out how to format the code bits a little nicer, and I figured maybe the weird errors from trying to install lighttpd manually might shed some light on the situation.

from what i can see in your post apache2 is installed. this will not work with pi-hole unless you modify it there are a few guides floating around on how to do this. the other option is to remove apache from the system and retry a lighttpd install

Hey, thanks for the reply!

I've had lighttpd and apache working together in the past. I have modified it as I mentioned in the post (configured custom port for lighttpd). Is this what you meant, or should I keep looking for more modifications?

Apache is being used to run the website for the nextcloud instance. Therefore I can't uninstall it without breaking nextcloud, as far as I'm aware.

whatever configuration changes you would have made to lighttpd are reverted when you update or repair. I'm not sure why lighttpd is not installing properly and you may have better results with google on that one

Yes, I had to change it a couple times after updates and such, but the functionality came back each time. For some reason, this time it's all borked. The config file is still set the way I need it, with the chosen port. I will have to go back to the drawing board, I suppose. Google/ddg usually helps solve all my linux problems but this time I've landed in a rut, not much out there by way of this problem. Thanks for the help, I will keep plugging away.

The issue lies in your packages. You have unmet dependencies which need to get fixed before you can install new packages.

Figures as much from the error messages when I try to install lighttpd. Any easy way to fix broken dependencies? I'm googlin' around right now, I just tried all of the following:

sudo apt-get update
sudo apt-get dist-upgrade
sudo dpkg --configure -a
sudo apt-get install -f

all with standard results, and for the last bit, the results:

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Should I try manually fixing all the broken dependencies listed in the error message after sudo apt-get install lighttpd?

Also, not sure if it's relevant, but I was able to install lm-sensors and remove it just now, before I learned that rpi uses a different method to get cpu temp.

Google is your best bet for fixing the package issue.

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