Has anyone here tried the new pihole with pixelserv-tls?
If you had made your question clear like the previous post, you won't have to ask the second time in a different thread. I think it's not a taboo to discuss all sorts of adblock scripts/daemons on this forum, even though individuals might have their own preferences. lol
So let's try to do this again...
How-To make pixelserv-tls work with Pi-Hole
This question has been asked multiple times. Seems either very few pihole users on this forum or perhaps no one is desperate enough to take a serious look. I want to set it right and spend some time googling i.e. only the last 10 minutes or so. Hence, the answer below might not be fully correct and/or requires a dedicated pihole user to experiment and provide feedback.
With the release of 4.0 in their FTL, pihole seems to have added a new config variable known as "BLOCKINGMODE" in pihole-FTL.conf. First, you have to set it to "IP-NODATA-AAAA". That's the easy part.
Pihole uses lighttpd (users optionally possible to use ngnix) for serving the Dashboard as well as HTTP ads when you use the above mentioned BLOCKING mode. So natively they do not provide a configuration to change the IPv4 address that blocked domains will resolve to (more on this later).
Luckily Pihole currently only uses port 80 for HTTP since they haven't been able to figure out HTTPS..yet. This implies that lighttpd will be listening on port 80 while port 443 is free. However,
pixelserv-tls will require both port 80 and 443 for best performance.
Option 1. You could simply run
pixelserv-tls on the same interface (as well as IPv4 address) as Pihole but only listen on 443. This will complete your loop of HTTPS ads i.e. HTTP ads served by Pihole's lighttpd. HTTPS ads served by
pixelserv-tls. Not recommended.
Option 2. Change Pihole's lighttpd config to listen on a different port for HTTP e.g. 8080. This implies you'll be accessing Pihole's Dashboard with an URL like http://<pihole IP>:8080/admin. The lighttpd config traditionally is in /etc/lighttd/lighttpd.conf but pihole might have changed that. I couldn't find a reference for it but instead I stumbled on the one for nginx
HERE.
In option 2, both port 80 and 443 then can be used by
pixelserv-tls. That's great since it can do a better and faster job than lighttpd & nginx. Recommended option.
Option 3. Make a feature request to allow users easily change HTTP port and/or the IPv4 address for blocked domains. For people, compiling their own PiHole shall be easy to change but I haven't looked at the code nor tried. Such feature request might be a little uphill struggle as it's not in PiHole's immediate interest.
At the moment, I believe option 2 is doable and will work. As said before if you or anyone else tried. Let us know how it goes. Personally I'm not a pihole user.
EDIT:
The above information may be outdated. The latest info can be found in this Wiki:
HOW-TO Setup pixelserv-tls for Pi-Hole.