- cross-posted to:
- selfhosted@lemmy.world
- pihole@sh.itjust.works
- cross-posted to:
- selfhosted@lemmy.world
- pihole@sh.itjust.works
my only complaint about it is the lack of clear “hey this is going to be a major update” on the webUI. I did the update command and was met with a different UI. Which wasn’t difficult to figure out, and I have to blame myself for not actually checking the patch notes first, but I wasn’t expecting a major update from the webUI as it only said “new version available run this command to upgrade”
the upgrade as a whole is all and all a great improvement
Nice!
Upgrade went smoothly on docker, with some neat new additions. There’s new filter options in the query log. There’s a bunch of new metrics under Settings > System (enable ‘advanced’ in the top right). And overall there seems to be many more settings available under System > All Settings. For example you can easily set the TTL for blocked responses (this was a setting burried in config files before, I was looking for it like 2 weeks ago).
If you don’t use/set a password in pihole, or you set one via .env variables; you’ll probably have to reset it with the command:
sudo docker exec <container_name> sudo pihole setpassword <your password here>
(empty for no password)
/edit; seems that was a temporary solution.
These env variables have changed:
Was:
webpassword=<your password>
DNS1=<upstream1>
DNS2=<upstream2>
Now:
FTLCONF_dns_upstream=<upstream1;upstream2>
FTLCONF_webserver_api_password=<your password here>
The exception to this is environment variables. You can start the container with the old variables in place but don’t expect them to work! It is recommended to read the docker section of our docs page before upgrading.
Important to know
Big improvement IMO. It’s using less resources on my old RPi 3 and the UI is much nicer to read. My only gripe is that it seemed to break my Homarr integration which I’ll try tinkering with at some point.
EDIT: The api seems to have changed entirely and is something I gotta wait for Homarr to fix.
It did change. One of the many changes listed. It’s using a different web server, I forget now, but moved away from the previous one.
Lighttpd ran into a dns issue mid update. And it dif not complet and left the aformentioned webserver running.
Removed with apt and voilla.
Would anyone be willing to offer their opinion on a comparison with Adguard Home?
Last week I was upgrading an old pi hole installation and ultimately decided to switch for awhile. Found the wild card blocking on Adguard to be quite nice for the pop ups that point out you’re using an ad blocker.
But really the more technical details are a bit out of my wheel house, so if anyone could weigh in perhaps if with this new version one of them has clearly pulled ahead or they are so similar it doesn’t really matter?
I used them in parallel for a while before switching to AdGuard. The key features that mattered to me were support for upstream DNS servers via DoH, detailed query logs, and wildcard domain rewriting. Also a better looking UI is a plus.
Welp here’s hoping something pops up to replace gravity sync soon, can’t really upgrade until it does.
I just found https://github.com/mattwebbio/orbital-sync but it’s not apparent if it’s compatible with v6 yet
I’m using orbital-sync, it’s not currently compatible with v6; but that’s what they’re working on now.
Hopefully not too long.