My google foo is broken.
Does anyone have a working(!) bash script that queries a pihole 6 (very important: 6) API for statistics? For instance, for blocked queries.
I do not get it 🙁

#pihole #pi-hole #piholev6

I shouldn't rush that much to upgrade my Pi-Hole 🥧🕳️ to the never v6 version after 1-2 day after it released in February 18th, just to end up brooking my existing setup. I had to start over since I was dumb enough to not make a backup of my existing working setup, I don't know what I expected. While the update was nearly fished the gravity updated failed and I had to stop the it with CTRL-C after waiting for hours to complete, it was stuck for some reason. After rebooting my pi the pihole service still started up but slowed down my pi and got completely unresponsive. I had run Bullseye on my Pi Zero W v1.1 board and either way I still wanted to upgrade to Bookworm. I had an older backup of my pi's sdcard with Bullseye and pihole v5 on it that I could flash back to use while I finish setting up the new image with Bookworm and pihole v6. I know I could avoid complicating things if I had another sdcard that I could use for the new image, not having to copy back and fourth different images while making lots of backups frequently of the new image after working on it for a couple of hours.
The only thing that made less painful doing it this was using pishrink that spared me hours whenever I needed to copy back the new image making it way faster then copying back 32 GB that takes a long time. I'm can't be happier that I found this nice tool that speed up significantly copying the images and swapping between the old perfectly working one and the new one until the new one was set up fully. ☺️
It took me days regardless to finish the new image because of lack of time to sit down and work on it until it's done, only doing small steps at a time. Now everything is working fine, I'm running the latest pihole version on bookworm for just about two weeks. 😃
But probably I had to start from an fresh new install, because I tried upgrading from bullseye to bookworm and it wasn't end up well, probably there was lots changes between the two.

#piholev6 #piholev5 #bullseye #bookworm #pizero #pishrink

Update auf #pihole v6 erledigt. Natürlich lighttpd abgeschaltet. Lief ohne Probleme durch. 🤗

#piholev6 #armbian #lighttpd

https://pi-hole.net/

@c0mpl3x Also of note - it appears that today's update from 6.0.3 to 6.0.4 nukes this setting (as well as disabling the newly installed TLS server with the selfsigned cert ) so something else to keep an eye out for.

Adding the "no-0x20-encode" back in fixes the issue

#piholev6

Betreibe einen #pihole seit mehreren Jahren. Upgrade #piholev6 ohne Probleme.
Hardware: NanoPi Neo
OS: #DietPi und #unbound
Die neue Version ist wie gehabt flott und bisher zuverlässig. Bin begeistert !

@c0mpl3x

And then there was the inexplicably odd and seemingly random failures to resolve legitimately good addresses.

Turns out this was a known issue - although a bit of digging was needed. I was using clouflared as a custom DNS provider (since AT&T seemed to be intercepting DNS queries even after opting out of their stupid "service") and apparently cloudflared does not react well to their new nixed case queries.

Adding "no-0x20-encode" to misc.dnsmasq_lines does seem to resolve that issue as well/

Seems to be functioning as expected at the moment, but will keep an eye out for other smallish issues as they will undoubtedly crop up.

https://discourse.pi-hole.net/t/v6-post-release-fixes-and-findings/76480

#piholev6

@c0mpl3x First item is that I was using the integrated piHole DHCP server - and on upgrade that was disabled and DHCP reservations gone.
Not too big of a deal I could spin enable a DHCP server elsewhere and start to see what else needed attention while I re-entered the reservations,

Unfortunately - V6 has a bit of a . . . challenging interface in comparison to the previous version, so will likely be leaving the DHCP server external from the pihole for the time being.

This is an issue that the devs are aware of - perhaps painfully so - althoug I don't expect that it's going to be a priority since I expect that not a lot of folks actually use that functionality

https://discourse.pi-hole.net/t/v6-post-release-fixes-and-findings/76480

#piholev6

@c0mpl3x Was watching out for these items - however - my upgrade today was was a bit more . . . interesting.

#piholev6

Freie Netze Muenchen e.V. (5.1.66.255) tut auch als upstream dns.

#piholev6 #pihole6

Ja interessant:

dns3.digitalcourage.de mit dem Port 853 tut hier als custom dns nicht, der alte dns2.digitalcourage.de mit 853 aber schon. Hm, was übersehe ich?

Weil der pihole selbst kein #DoT kann?

#piholev6 #pihole6

@benknispel
Ich tue bei der Testinstallation, an der ich jetzt gerade hier sitze, noch mit custom DNS upstream server rum. Mit Cloudflare aus der "Vorauswahlliste" tuts.

#piholev6 #pihole6

NTP option neuerdings in Pihole findet sich unter

Settings > All Settings > NTP > ntp.ipv4/6.activate

Kann man auch nen andern Lokalen (Router z.B.) eintragen, der NTP Server ist ("Punkt" ntp.sync.server).

#piholev6 #pihole6

@benknispel

Web UI 403 Forbidden After Pi-hole 6.0.2 Update > möglicherweise alter Webserver "im Weg"

für mich eben tat es
sudo systemctl stop lighttpd.service
sudo systemctl disable lighttpd.service
sudo systemctl restart pihole-FTL.service
möglicherweise / bisher

https://github.com/pi-hole/pi-hole/issues/5948#issuecomment-2674966397

#piholev6 #pihole6

@benknispel Hier zwei Sachen bisher (Updateinstallationen):
Die custom dns unsichtbar nach update, also es wird gesagt es gibt welche sie werden aber nicht angezeigt.

Webinterface-PW "weg", vllt. weils ein anderer Webserver ist.

#piholev6 #pihole6