I have set up your newest Pi-Hole 6.4 directly through the setup script on a Raspberry Pi 5 with the Raspberry PI OS.
I have subscribed to multiple blacklists and allowlists. One allow list is explicitly allowing facebook.com in an ABP-style domain.
Expected Behaviour:
I expect Facebook to be working, since it is explicitly allowed in a subscribed allowlist.
Actual Behaviour:
I cannot access the page.
When using dig and DNS through HTTPS, I receive this return:
However, when I am manually adding “@@||facebook.com^” as an allowed regex domain, facebook.com becomes available. Why doesn’t the subscribed allowlist get prioritized? I would prefer the “Subscribed allowlists” to be working over “Subscribed denylist” as intended (allow over block). Priority is further clarified here: Domain Database - Pi-hole documentation
The relevant subscribed allowlist is processed as follows:
Not related to your issue, your screenshots would indicate your Pi-hole's DNS server is publically accessible via port 853, and your debug log could suggest you may run nginx as DNS-over-TLS proxy in front of Pi-hole?
Make sure that port 53 is blocked for inbound public traffic in such a case, or you may risk to run an open resolver.
As to your observation:
Could you please share those lines from your allowlists that are supposed to allow accessing facebook.com?
The issue is:
Pi-hole will use the group with ID=0 and apply it to every client there doesn't have a group explicitly assigned. The other groups will be used only by Clients that are assigned to them (but there is no clients in your group management).
As a result, you Pi-hole is using all lists assigned to group ID=0 (Block), but is not applying the lists assigned to the other group.
If you want your allowlists applied to every client, you need to assign these lists to the group with ID=0.
Note: you should rename that group back to "Default", because adding allowlists to a group called "Block" will create a lot of confusion.
Yet you configured no client to be associated with that group.
And you only ever would have to add specific clients to groups if you'd wanted them to be filtered differently.
In your case, you should probably just re-assign your subscribed allowlists with Pi-hole's Default group (group_id 0), so all your clients would benefit from your allowlists.