Graphs1090 broken by PiHole 6

FlightAware ADS-B Flight Tracking
1

I run graphs1090 and my PiHole on the same Pi… Its been working fantastically for a year.
I recently updated PiHole to version 6, failed to notice that that it no longer uses lighttpd, ands its removed as part of the update.

I’m now struggling to get graphs1090 back.

I have reinstalled lighttpd with the following:

sudo apt install lighttpd -y

checked its running with:

sudo systemctl status lighttpd

The output is:

lighttpd.service - Lighttpd Daemon
     Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
     Active: **active (running)** since Tue 2025-02-25 21:49:01 GMT; 1s ago
    Process: 10301 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
   Main PID: 10310 (lighttpd)
      Tasks: 3 (limit: 1595)
        CPU: 3.528s
     CGroup: /system.slice/lighttpd.service
             ├─10310 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
             ├─10313 /bin/sh -c /usr/share/lighttpd/create-mime.conf.pl
             └─10314 /usr/bin/perl -w /usr/share/lighttpd/create-mime.conf.pl

I note its “Active”
but after a few moments its goes to this:

ilghttpd.service - Lighttpd Daemon
     Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
     Active: **activating (start-pre)** since Tue 2025-02-25 21:58:40 GMT; 1s ago
Cntrl PID: 15121 (lighttpd)
      Tasks: 3 (limit: 1595)
        CPU: 1.471s

It seem to swap between the two :frowning:

What happens is when access http://192.168.1.x/graphs1090/

It redirects to the pihole login page…

I think PiHole is hogging port 80:


░░ A start job for unit lighttpd.service has finished successfully.
Feb 25 22:40:39 FlightRadar lighttpd[30402]: 2025-02-25 22:40:37: network.c.369) can't bind to socket: 0.0.0.0:80: Address already in use
Feb 25 22:40:39 FlightRadar systemd[1]: lighttpd.service: Main process exited, code=exited, status=255/EXCEPTION
░░ An ExecStart= process belonging to unit lighttpd.service has exited.
Feb 25 22:40:39 FlightRadar systemd[1]: lighttpd.service: Failed with result 'exit-code'.
░░ The unit lighttpd.service has entered the 'failed' state with result 'exit-code'.
Feb 25 22:40:39 FlightRadar systemd[1]: lighttpd.service: Consumed 3.675s CPU time.
░░ The unit lighttpd.service completed and consumed the indicated resources.
Feb 25 22:40:39 FlightRadar systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 622.
░░ Automatic restarting of the unit lighttpd.service has been scheduled, as the result for
░░ Subject: A stop job for unit lighttpd.service has finished
░░ A stop job for unit lighttpd.service has finished.

Any suggestions -Thansk

2

Think i Fixed my own issue…
For those that find this post:

modify:
sudo nano /etc/lighttpd/lighttpd.conf

Look for the line that specifies the server port usually 80

change it to a new port: 8088 for example

save the changes…

for me that worked, both are no accessible on respective pots

:

3

Interesting, seems kinda heavy handed for PiHole to remove lighttpd just because it’s not going to be using it. Is that a reason for having containers – in order to minimize problems like this?

Edit: To be accurate, Pihole doesn’t remove lighttpd, it just disables it when it upgrades to version 6.

4

pihole -up
Gives the option of not disabling lighttpd as part of the upgrade process:

Screenshot 2025-02-26 at 11.54.50
Screenshot 2025-02-26 at 11.54.50994×578 47.4 KB

If you select No, the pihole login is available at [ip of Pi]:8080/admin/

1 Like
5

You are correct, I forgot about that dialog. So they were considerate in the update.

2 Likes
6

YES!
It does a damn good job for separating, testing, keeping the system clean, being quickly back on business in case of hardware failures, and so on, …

I am running PiHole in docker, as well as the full utrafeeder stack for ADS-B.
I learned docker in my spare time some month before, to join PiHole and Home Assistant to one single hardware, and I did never regret it.
In the meantime I am running 15 containers on two Raspberries and other four or five on my NAS.

The only complicated part has been understanding the virtual lan interface, which was required by PiHole because I am using all the DHCP features of PiHole. And by HA because I am using some ESPhome feature. But lately, it was not really complicated. I only had a node in my brain.

1 Like