I’ve been trying Privoxy out and I have to say I’m pleasantly surprised. Squid is a bit much for most of us and it’s not of much benefit to run a local cache since most things are either HTTPS or cached by the browser - anyone who follows me on Twitter will know of my embarrassing D’OOP with Privoxy and the Firefox cache. Well, if we can’t laugh at our own screw ups, we can’t laugh at others.
It plays well with (and adds to the functionality of) PiHole that most excellent ad-blocker and catches things that PiHole doesn’t.
It’s pretty easy to add privoxy to DietPi as is with:
apt install privoxy
you’re pretty much set save for fixing the address of the DietPi server in the config (/etc/privoxy/config) file and switching the address to that of your Pi - which should be static for ease of use and to avoid DNS lookups. It defaults to localhost which isn’t a lot of use unless you’re installing it to a single machine.
listen-address 192.168.0.100:8118
Now the gotcha!
Others probably can answer this, but I’ve found Privoxy was invariably unable to start at boot even though the service is enabled. This might be unique to the way my install, but it’s worth checking after a routine re-start.
service privoxy status
service privoxy start
or the lazy man’s way: :mrgreen:
service privoxy restart
https://www.privoxy.org/
One last thing, if you do find yourself using Eep (i2p) sites, you’ll need to add a passthrough your i2p daemon like this (running on the same Pi in this case):
forward .i2p localhost:4444