Found a pihole shallalist project is it compatible?

Hi Guys,

I was beginning to setup my rpi4 with pihole and came across what looked like a really good project GitHub - rumbero71/pihole-shallalist: PiHole as a parental filter using Shalla's blacklist hasn't been updated since 2017, but thought i'd roll the dice and try it and worked through each step....anyway, it's not working i'm half thinking it is not compatible with latest pihole realease + unbound recursive dns.

Any ideas??

on ubuntu server 20.04.1 latest, rpi4 8GB can ssh in etc just can't reach pihole webui does not respond....was basically an experiment too as really wanted to try pihole + shallalist with recursive dns going through vpn for encryption etc

also i was trying to take ownership of a folder and contents i used chown -R (user i wanted to own it) is this correct??

Nothing has changed in a long time towards what types of lists are acceptable. You can just run

pihole -g

on your Pi-hole and watch the output. It will tell you how much of the lists it downloaded made it into your Pi-hole. It will also complain about possible uncompatible domains.

More information about the adlists should also become available on the web interface in a future release, see

Can you check the output of sudo service lighttpd status ?
Do you have another webserver running on the same machine?

Yes.

It times out trying to reach the gui....in a way if i fail, i learn that's only a good thing

not sure what to try really atm i followed the guide to the letter....

You mean the shalla one? As it is already three years old, their scripts may indeed not work anymore. We released Pi-hole v5.0 on May 10, 2020 which modified a lot of the underlying machinery to be much more powerful, memory-efficient and customizable. As their scripts are older, they likely don't work any longer. Maybe they failed somewhere in between and now nothing is working as expected any more.

Try if

pihole -r

(chose Repair) can bring you back to a working state.

root@RaspberryPi:~# sudo service lighttpd status ?
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled> Active: failed (Result: exit-code) since Sat 2021-02-06 10:17> Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/light>● lighttpd.service - Lighttpd Daemon ● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2021-02-06 10:17:07 UTC; 34min ago
Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Feb 06 10:17:07 RaspberryPi systemd[1]: Stopped Lighttpd Daemon. Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Start request repeated too quickly. Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Feb 06 10:17:07 RaspberryPi systemd[1]: Failed to start Lighttpd Daemon. ~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-10/10 (END)...skipping...
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-02-06 10:17:07 UTC; 34min ago
Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-02-06 10:17:07 UTC; 34min ago
Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)

Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Feb 06 10:17:07 RaspberryPi systemd[1]: Stopped Lighttpd Daemon.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Start request repeated too quickly.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Feb 06 10:17:07 RaspberryPi systemd[1]: Failed to start Lighttpd Daemon.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-10/10 (END)...skipping...
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled> Active: failed (Result: exit-code) since Sat 2021-02-06 10:17> Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/light>
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Schedule>Feb 06 10:17:07 RaspberryPi systemd[1]: Stopped Lighttpd Daemon.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Start re>Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Failed w>Feb 06 10:17:07 RaspberryPi systemd[1]: Failed to start Lighttpd D>~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-10/10 (END)...skipping...
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled> Active: failed (Result: exit-code) since Sat 2021-02-06 10:17> Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/light>
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Schedule>Feb 06 10:17:07 RaspberryPi systemd[1]: Stopped Lighttpd Daemon.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Start re>Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Failed w>Feb 06 10:17:07 RaspberryPi systemd[1]: Failed to start Lighttpd D>~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-02-06 10:17:07 UTC; 34min ago
Process: 557 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)

Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Feb 06 10:17:07 RaspberryPi systemd[1]: Stopped Lighttpd Daemon.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Start request repeated too quickly.
Feb 06 10:17:07 RaspberryPi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Feb 06 10:17:07 RaspberryPi systemd[1]: Failed to start Lighttpd Daemon.

pihole -r

So basically a factory reset?

Sort of. It tries to repair based on your given configuration. So nothing should be lost. If the configuration is broken (due to shalla interaction), you may need to go the Reconfigure instead of Repair path. This is a factory-reset.

I did think i was being ambitious trying that rumbero pihole project, did look pretty neat if it worked that is, like you said a lot of under the hood code changes more than likely made it incompatible

Still unreachable....going to have to reconfigure it, thinking could i still have the shallalist on a cronjob

Don't suppose you developers might consider a fork of that rumbero project in some way??

I don't see anyone of us having the time for such an endeavor. In the end, we are all only volunteers and - with Pi-hole being free from top to bottom, we all have to make our money in other jobs. A lot of stuff (like per-client blocking control) is already available in Pi-hole natively by now.

If shallalist blocklist support with downloading and being able to choose categories from pihole gui could be added i'm sure a lot would donate for that functionality...I definitely would

The issue is more the amount of time. Foir myself (and I also know for the others of the team), the donations aren't something mandatory. I enjoy working on this very nice project. Even when we appreciate them, because they allow us to buy some new testing equipment like new Raspberry Pis, etc. the donations unfortunately don't really change how much time I have with a full-time job and a family around me. Sorry.

I appreciate and understand that, Thanks for your help

the reset didnt help still cant get to gui...going to have to nuke the ubuntu install could that be because i didnt add a default blocklist when offered?

No, not at all. They are entirely optional.

Sorry to hear this but I was kinda afraid that'd be the solution in the end. There were just too many massive incompatible changes. Sorry.

Just one of them things, nature of tech never straightforward or simple

im expecting worse with trying to setup opnsense!

This post was flagged by the community and is temporarily hidden.

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