Thanks, this is perfect! This is already sufficient to fix it but I'd to understand where it comes from. Please also enter
p conf_item
and show us the result
Ah, yeah, I forgot you will need to do switch frame to the relevant one first, like:
f 1
p conf_item
See you tomorrow.
Sorry ... we will also need
p *conf_item
after the others...
Hey, no problem. I am very happy to give back!!! You just have to have a little patience, I am 67 and not firm (understatement of the year!!) with this stuff. I am giving my best and as long as I can help, ask away!!!!
Thanks indeed very much for your help, without it it'd have been close to impossible to find this regression.
The bugfix is here and technical details are therein:
As soon as this is merged, there should be no crashes and more and, furthermore, similar crashes are avoided by construction in the future. Thank you for helping up making Pi-hole better for everyone!
and, btw, Grüße aus dem Ahrtal 
1 Like
Zurück aus Mannheim!!!!
When the fix is on-line, please let me know. I will try the update then as per the website!!!
You can already check out the fix when using
pihole checkout ftl fix/config_crash
instead of the corresponding ftl development-v6 command.
Not aware, that I used that at all....
These are the only 3 commands I used, besides the once you asked me to use.
echo "development-v6" | sudo tee /etc/pihole/ftlbranch
pihole checkout core development-v6
pihole checkout web development-v6
Regards
Oh, yeah, sorry, it'd have been this one becoming
echo "fix/config_crash" | sudo tee /etc/pihole/ftlbranch
but we already merged the bugfix a split second ago to the regular branch so everything should work with the commands you have above unaltered in about half an hour from now.
I will set up my Proxmox and try it later. You will get feedback....
1 Like
Perfect!!! Worked as expected!!! All my gravity list are still there and I could update them.
Changed the pw and that messed me up. My new pw would not work and the old one was gone. After closing the cointainer down and restarting it, my new pw worked. Is that normal op?
Thanks for the fix. Not filtering with PI6 at the moment, just wanted it up and running.
Regards
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
This list is updated in PI5 no problem, PI6 throws an error....
The password change should have been picked up immediately, how did you change it?
I did just try with this list and everything seems to work fine over here:
I'm keeping an eye on it, could you give me the output of
pihole-FTL --config dns.blocking.mode
?
Just returning NULL. I am not routing my traffic through PI6 at the moment...
As the log-in screen of PI suggests....
Change only took place after restarting the container.
Running PI6 now (18,4% blocked) and tried again. Still getting NULL for the above command.
NULL is perfectly fine, in fact, it is even teg standard setting. I'll look at the other issue as soon as possible but time is limited tonight.
No problem!! Did not know, that NULL is good!!!!