Recently upgraded to v6 and need to replace an older Raspberry Pi with a new one and wanted to start with a fresh install and config import but can't get the export from the existing installation.
Expected Behaviour:
After clicking the Export button on the Teleporter settings page, when using a modern browser, an archive of the configuration should download.
Tried Chrome 133.0.6943.142 and Firefox 136.0 on Windows 11. Also tried to create the archive via CLI.
Pi-hole is running on a model 3+ rev 1.3 running Raspberry Pi Lite (64-bit) - Debian 12
Dedicated to Pi-hole, fully patched.
Pi-hole is running versions: Core [v6.0.5], FTL [v6.0.4], Web interface [v6.0.2]
Actual Behaviour:
Button temporarily goes green when pressing but nothing happens.
FTL.log shows:
ERROR SQLite3: no such table: disk.aliasclient in "CREATE TABLE "aliasclient" AS SELECT * FROM disk."aliasclient";" (1)
WARNING Failed to create aliasclient in in-memory database: no such table: disk.aliasclient
WARNING API: Failed to create FTL database for heap ZIP archive! (key: compression_error)
running 'sudo pihole-FTL --teleport' gives this:
Failed to create aliasclient in in-memory database: no such table: disk.aliasclient
Failed to create Teleporter ZIP file: Failed to create FTL database for heap ZIP archive!
I am not @dpaulson, but experienced the same behaviour after the update to version 6 and each subsequent update.
Removing the 16KB /etc/pihole/pihole-FTL.db while pihole-FTL.service [n.b. There is no pihole.service] was stopped and starting [n.b. Not stop again] the service created a 88KB file and fixed the failed Teleporter export.
$ ls -lh /etc/pihole/pihole-FTL.db
-rw-r----- 1 pihole pihole 16K Jun 4 2024 /etc/pihole/pihole-FTL.db
$ sudo systemctl status pihole-FTL.service
● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-03-04 15:53:59 EST; 31min ago
Process: 685 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Main PID: 701 (pihole-FTL)
Tasks: 18 (limit: 768)
CPU: 40.798s
CGroup: /system.slice/pihole-FTL.service
└─701 /usr/bin/pihole-FTL -f
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.832 EST [701M] INFO: FTL user: pihole
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.832 EST [701M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.874 EST [701M] INFO: Wrote config file:
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.874 EST [701M] INFO: - 153 total entries
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.875 EST [701M] INFO: - 141 entries are default
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.875 EST [701M] INFO: - 12 entries are modified
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.875 EST [701M] INFO: - 0 entries are forced through environment
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.895 EST [701M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
Mar 04 15:53:59 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.895 EST [701M] INFO: PID file does not exist or not readable
Mar 04 15:54:02 ns1 pihole-FTL[701]: 2025-03-04 15:53:59.895 EST [701M] INFO: No other running FTL process found.
$ sudo systemctl stop pihole-FTL.service
$ sudo rm -v /etc/pihole/pihole-FTL.db
removed '/etc/pihole/pihole-FTL.db'
$ sudo systemctl start pihole-FTL.service
$ sudo systemctl status pihole-FTL.service
● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-03-04 16:26:39 EST; 9s ago
Process: 1999 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Main PID: 2012 (pihole-FTL)
Tasks: 16 (limit: 768)
CPU: 3.023s
CGroup: /system.slice/pihole-FTL.service
└─2012 /usr/bin/pihole-FTL -f
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.205 EST [2012M] INFO: FTL user: pihole
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.205 EST [2012M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.215 EST [2012M] INFO: Wrote config file:
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.215 EST [2012M] INFO: - 153 total entries
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.215 EST [2012M] INFO: - 142 entries are default
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.215 EST [2012M] INFO: - 11 entries are modified
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.215 EST [2012M] INFO: - 0 entries are forced through environment
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.219 EST [2012M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
Mar 04 16:26:39 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.219 EST [2012M] INFO: PID file does not exist or not readable
Mar 04 16:26:45 ns1 pihole-FTL[2012]: 2025-03-04 16:26:39.219 EST [2012M] INFO: No other running FTL process found.
$ ls -lh /etc/pihole/pihole-FTL.db
-rw-r----- 1 pihole pihole 88K Mar 4 16:26 /etc/pihole/pihole-FTL.db
Thanks, I was hung up on the failure to stop the pihole.service error I was receiving. @Bucking_Horn 's updated post with pihole-FTL works so I marked it as the solution.