Check the list cache again

Oct 13, 2025 by recoveryshake.com 148 views

When adlist removed from WebUI the corresponding list info is not removed from /etc/pihole/listsCache/

As a user of the popular ad-blocking tool, Pi-hole, you may have encountered a frustrating issue where the list information is not removed from the /etc/pihole/listsCache/ directory even after removing the list from the WebUI. This issue can lead to unnecessary storage space consumption and potential performance issues. In this article, we will delve into the details of this problem, explore the expected behavior, and provide a step-by-step guide to reproduce the issue.

Before we dive into the issue, let's take a look at the versions of the Pi-hole components involved:

Core

Version: v6.0.5-13-g387ec3a3 (Latest: null)
Branch: development
Hash: 387ec3a3 (Latest: 387ec3a3)

Web

Version: v6.0.2-51-g0e41aaa4 (Latest: null)
Branch: development
Hash: 0e41aaa4 (Latest: 0e41aaa4)

FTL

Version: vDev-464b2df (Latest: null)
Branch: development
Hash: 464b2dfc (Latest: 464b2dfc)

The issue is being reported on the following platform:

OS and version: Ubuntu 24.04.2
Platform: Raspberry Pi 4 Model B Rev 1.1

When a list is removed from the WebUI, the corresponding list information should be removed from the /etc/pihole/listsCache/ directory. This is the expected behavior, and it ensures that the list cache remains up-to-date and efficient.

Unfortunately, the actual behavior is different from the expected behavior. When a list is removed from the WebUI, the corresponding list information is not removed from the /etc/pihole/listsCache/ directory. This can lead to unnecessary storage space consumption and potential performance issues.

To reproduce the issue, follow these steps:

Go to the Pi-hole WebUI: Navigate to https://pi.hole/admin/groups/lists in your web browser.
Add a few lists: Click on the "Add" button to add a few lists to your Pi-hole setup.
Update gravity: Click on the "Update Gravity" button to update the gravity settings.
Check the list cache: Use the ls command to check the contents of the /etc/pihole/listsCache/ directory. You should see the newly added list information.
Remove the lists: Go back to the Pi-hole WebUI and click on the "Remove" button to remove the newly added lists.
Update gravity again: Click on the "Update Gravity" button again to update the gravity settings.
Check the list cache again: Use the ls command to check the contents of the /etc/pihole/listsCache/ directory again. You should still see the list information for the lists that were just removed.

If you are experiencing this issue, you can provide a debug token to help the Pi-hole developers diagnose the problem. To generate a debug token, run the following command:

pihole -d

This will generate a debug token that you can share with the Pi-hole developers.

If you have any screenshots that can help illustrate the issue, please add them here.

If you have any additional context about the problem, please add it here.

In conclusion, the issue where the list information is not removed from the /etc/pihole/listsCache/ directory even after removing the list from the WebUI is a frustrating problem that can lead to unnecessary storage space consumption and potential performance issues. By following the steps outlined in this article, you can reproduce the issue and provide a debug token to help the Pi-hole developers diagnose the problem. We hope that this article has been helpful in understanding the issue and providing a solution.
When adlist removed from WebUI the corresponding list info is not removed from /etc/pihole/listsCache/ - Q&A

In our previous article, we explored the issue where the list information is not removed from the /etc/pihole/listsCache/ directory even after removing the list from the WebUI. In this article, we will provide a Q&A section to help answer some of the most frequently asked questions about this issue.

A: The expected behavior is that the corresponding list information should be removed from the /etc/pihole/listsCache/ directory.

A: The actual behavior is that the corresponding list information is not removed from the /etc/pihole/listsCache/ directory.

A: This issue is happening because of a bug in the Pi-hole WebUI. The bug is causing the list information to not be removed from the /etc/pihole/listsCache/ directory even after the list is removed from the WebUI.

A: To reproduce this issue, follow these steps:

Go to the Pi-hole WebUI and add a few lists.
Update gravity.
Check the list cache to see the newly added list information.
Remove the lists from the WebUI.
Update gravity again.
Check the list cache again to see if the list information is still present.

A: Unfortunately, there is no fix for this issue yet. However, you can try the following workarounds:

Manually remove the list information from the /etc/pihole/listsCache/ directory.
Use the pihole -d command to generate a debug token and share it with the Pi-hole developers.

A: To prevent this issue from happening in the future, you can try the following:

Regularly clean up the /etc/pihole/listsCache/ directory to remove any unnecessary list information.
Use the pihole -d command to generate a debug token and share it with the Pi-hole developers to help them diagnose and fix the issue.

A: No, this issue is not specific to your Pi-hole setup. It is a bug that affects all Pi-hole users.

A: If you are experiencing this issue, you can try the following:

Check the Pi-hole documentation and forums for any known solutions or workarounds.
Reach out to the Pi-hole community for help and support.
Share your debug token with the Pi-hole developers to help them diagnose and fix the issue.