No blockpage after upgrade to v4.0

Please follow the below template, it will help us to help you!

Expected Behaviour:

After I run an upgrade from v3.3 to v4.0 today, pi-hole isnt showing the blockpage anymore on blocked sites.
The Web Interface is installed and works well.

Actual Behaviour:

pi-hole answers all blocked queries with IP 0.0.0.0.
I have already run pihole -r > Repair and pihole-r > Reconfigure, but pihole still answers with 0.0.0.0 instead of the pihole's IP.

Debug Token:

3wlneh96g5

This is expected behavior, see

Pi-hole has used IP-based blocking since it’s inception. With 4.0, we introduce several different choices of blocking methods. And after much discussion internally, we decided to change the default blocking mode to NULL blocking.

The main reason for this is that it eliminates the need for iptables rules currently needed for slow-loading pages. Having to make these adjustments post-install is a hassle for new and experienced users alike, plus NULL blocking provides the same end result without the negative side effects. A result of this change is that the block page will no longer work (unless you choose to use an IP blocking mode).

NULL blocking is just the new default, and there are several different blocking modes you can choose from, so use the one that fits your needs the best.

1 Like

Thank you for the very fast reply.

For testing, I added line BLOCKINGMODE=IP-NODATA-AAAA
to file pihole-FTL.conf and run pihole -g,
and now I get the blockpage again.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.