| 1 | ### Understand the alert |
| 2 | |
| 3 | This alert monitors if Pi-hole's ability of blocking unwanted domains is active. If you receive this alert, it means that your Pi-hole's ad filtering is currently disabled. |
| 4 | |
| 5 | ### Troubleshoot the alert |
| 6 | |
| 7 | 1. Check the status of Pi-hole |
| 8 | |
| 9 | To check the current status of Pi-hole, run the following command: |
| 10 | ``` |
| 11 | pihole status |
| 12 | ``` |
| 13 | This command will show if Pi-hole is active or disabled. |
| 14 | |
| 15 | 2. Re-enable Pi-hole |
| 16 | |
| 17 | If Pi-hole is disabled as per the status, you can re-enable it by running the following command: |
| 18 | |
| 19 | ``` |
| 20 | pihole enable |
| 21 | ``` |
| 22 | |
| 23 | 3. Confirm Pi-hole is enabled |
| 24 | |
| 25 | After running the previous command, run `pihole status` again to confirm that Pi-hole is now enabled and blocking unwanted domains. |
| 26 | |
| 27 | 4. Check for errors or warnings |
| 28 | |
| 29 | If Pi-hole is still not enabled, take a look at the logs for any errors or warnings: |
| 30 | |
| 31 | ``` |
| 32 | cat /var/log/pihole.log | grep -i error |
| 33 | cat /var/log/pihole.log | grep -i warning |
| 34 | ``` |
| 35 | |
| 36 | 5. Rebuild the blocklist |
| 37 | |
| 38 | If you still face issues, you can try rebuilding the blocklist by running: |
| 39 | |
| 40 | ``` |
| 41 | pihole -g |
| 42 | ``` |
| 43 | |
| 44 | 6. Update Pi-hole |
| 45 | |
| 46 | If the problem persists, consider updating Pi-hole to the latest version: |
| 47 | |
| 48 | ``` |
| 49 | pihole -up |
| 50 | ``` |
| 51 | |
| 52 | ### Useful resources |
| 53 | |
| 54 | 1. [Pi-hole Official Documentation](https://docs.pi-hole.net/) |