pihole-ftl-setup: lists fail to add — type sent in JSON body instead of query parameter

[MaxWolf-01]

Description

The pihole-ftl-setup service fails to add blocklists configured via services.pihole-ftl.lists. The Pi-hole v6 API expects the type parameter (allow/block) as a query parameter, but the setup script sends it in the JSON body.

Error

Adding list: {"address":"https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/pro.txt","comment":"Hagezi Pro","enabled":true,"type":"block"}
Error: {
  "key": "bad_request",
  "message": "Invalid request: Specify type parameter (should be either \"allow\" or \"block\")",
  "hint": null
}

The service exits with status 1, gravity has 0 domains, and nothing is blocked.

Root cause

In pihole-ftl-setup-script.nix, the addList function calls:

local result=$(PostFTLData "lists" "$payload")

This POSTs to /api/lists with type in the JSON body. The Pi-hole v6 API expects type as a query parameter: /api/lists?type=block.

PostFTLData (from Pi-hole's api.sh) sends the second argument as --data-raw, so type ends up in the body where the API doesn't look for it.

Suggested fix

In pihole-ftl-setup-script.nix:

1. Extract type from the payload before sending
2. Append it as a query parameter: PostFTLData "lists?type=${type}" "$payload_without_type"

Or adjust makePayload to exclude type from the JSON and pass it separately.

Steps to reproduce

services.pihole-ftl = {
  enable = true;
  settings.dns.upstreams = [ "1.1.1.1" ];
  lists = [{
    url = "https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/pro.txt";
    type = "block";
    enabled = true;
    description = "test";
  }];
};

services.pihole-web = {
  enable = true;
  ports = [ "8053s" ];
};

After nixos-rebuild switch:

systemctl status pihole-ftl-setup.service  # failed
journalctl -u pihole-ftl-setup.service     # shows the error above

Metadata

• NixOS version: unstable (nixos-26.05)
• pihole-ftl: 6.4.1
• pihole: 6.1.4
• Module file: nixos/modules/services/networking/pihole-ftl-setup-script.nix
• Maintainer: @averyvigolo

[MaxWolf-01]

Additional bug: pihole / pihole-ftl version mismatch causes broken gravity database

The pihole package is version 6.1.4 while pihole-ftl is 6.4.1. This causes a schema mismatch:

• pihole -g (v6.1.4) creates gravity.db with old-style view names: vw_whitelist, vw_blacklist, vw_regex_whitelist, vw_regex_blacklist
• pihole-FTL (v6.4.1) expects new-style names: vw_allowlist, vw_denylist, vw_regex_allowlist, vw_regex_denylist

Verified against upstream: current pi-hole master's gravity.db.sql uses the new names.

Result: FTL starts but can't query the gravity database:

ERROR: SQLite3: no such table: vw_allowlist in "SELECT id from vw_allowlist WHERE domain = ? AND group_id IN (0);" (1)
ERROR: gravityDB_open("SELECT(... vw_allowlist ...)") - SQL error prepare: SQL logic error

Blocking doesn't work at all even though gravity has 189k domains loaded.

The fix is to update the pihole package to match pihole-ftl, or at least to a version that creates the new-style view names.

[azban]

This updates to 6.4: https://github.com/NixOS/nixpkgs/pull/498231/changes