Changes to /etc/pihole/pihole.conf overwritten when I start pihole-FTL

Help
1

Version information:
Pihole Core v6.0, FTLv6.0, and Web interface v6.0
OS: 64-bit Debian GNU/Linux 12 (bookworm)
kernel: 6.6.74+rpt-rpi-v8 (aarch64), date: 2025-01-27 06:19:55 PM CET (+01:00)
hardware: Raspberry Pi 3 Model B Rev 1.2 revision a02082, aarch64, ARM Cortex-A53, 4 cores/threads

Expected Behaviour:

I want to make permanent configuration changes by editing /etc/pihole/pihole.toml. Specifically, I want to add entries in the hosts option. For this reason, I either edit the file manually, or overwrite it with an edited copy. I expect pihole to either immediately apply these configuration changes, or require a restart to apply them.

Actual Behaviour:

If I change the file while pihole is running, my changes are immediately reverted: the file content is changed back to what it was before I made the changes. The changes are not applied.

If I stop pihole-FTL, I can change the file without it immediately being reverted. However, as soon as I start pihole-FTL, the file is reverted and my changes are undone. They are not applied.

If I add entries through the UI, they are added to the file; such changes are permanent.

Debug Token:

For security reasons, I do not want to upload anything to the cloud.

2

Perhaps this is a Docker install, or your file system is running in read-only mode, by intention or not?

An uploaded debug log would be accessible only by trusted members of the Pi-hole team, and it will automatically be deleted after 48 hours.

4

The file system is writeable. I can make the changes as long as pihole isn't running. As soon as I start pihole, the changes are reverted.

5

Please check /var/log/pihole/FTL.log for any errors being reported regarding your config file.

What filesystem is it? Is it local or remote? What is the partition format (Ext4, vfat, ...)? This may be relevant, too.

6

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