AdGuard Home's service blocking isn't working

Hello everyone,

I recently embarked on the Home Assistant adventure with a Raspberry Pi 5. I recently installed the AdGuard Home add-on on Home Assistant. I also configured a static IP address in Home Assistant:

I changed the DNS settings of my Freebox Ultra.

But when I run the test on the AdGuard website: AdGuard – Le bloqueur de publicité le plus performant du monde!
Here’s the test result (Doesn’t work).

I feel like AdGuard isn’t working properly. For instance, I’ve blocked some services in the filters, but when I visit them, there’s no blocking. The blocking used to work, but it didn’t last long.
No error here:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 5.0.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.5  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2024.2.2
 Home Assistant Supervisor: 2024.02.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-adguard: starting
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-adguard successfully started
s6-rc: info: service adguard: starting
s6-rc: info: service adguard successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[01:03:37] INFO: Starting AdGuard Home server...
2024/02/23 01:03:37.319853 [info] AdGuard Home, version v0.107.44
2024/02/23 01:03:37.321485 [info] tls: using default ciphers
2024/02/23 01:03:37.325211 [info] safesearch default: reset 253 rules
2024/02/23 01:03:37.385878 [info] Initializing auth module: /data/adguard/data/sessions.db
2024/02/23 01:03:37.386125 [info] auth: initialized.  users:0  sessions:0
2024/02/23 01:03:37.386163 [info] AdGuard Home updates are disabled
2024/02/23 01:03:37.386172 [info] web: initializing
2024/02/23 01:03:37.417709 [info] dnsproxy: cache: enabled, size 4096 b
2024/02/23 01:03:37.417742 [info] dnsproxy: max goroutines is set to 300
2024/02/23 01:03:37.417852 [info] dnsproxy: cache: disabled
2024/02/23 01:03:37.418023 [info] AdGuard Home is available at the following addresses:
2024/02/23 01:03:37.418038 [info] go to http://127.0.0.1:45158
2024/02/23 01:03:37.418093 [info] clients: processing addresses
2024/02/23 01:03:37.711188 [info] dnsproxy: starting dns proxy server
2024/02/23 01:03:37.711233 [info] Ratelimit is enabled and set to 20 rps, IPv4 subnet mask len 24, IPv6 subnet mask len 56
2024/02/23 01:03:37.711238 [info] The server is configured to refuse ANY requests
2024/02/23 01:03:37.711242 [info] dnsproxy: cache: enabled, size 4194304 b
2024/02/23 01:03:37.711251 [info] dnsproxy: max goroutines is set to 300
2024/02/23 01:03:37.711265 [info] dnsproxy: creating udp server socket 192.168.1.182:53
2024/02/23 01:03:37.711388 [info] dnsproxy: listening to udp://192.168.1.182:53
2024/02/23 01:03:37.711399 [info] dnsproxy: creating udp server socket [2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.711454 [info] dnsproxy: listening to udp://[2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.711460 [info] dnsproxy: creating udp server socket 172.30.32.1:53
2024/02/23 01:03:37.711496 [info] dnsproxy: listening to udp://172.30.32.1:53
2024/02/23 01:03:37.711502 [info] dnsproxy: creating udp server socket 127.0.0.1:53
2024/02/23 01:03:37.711544 [info] dnsproxy: listening to udp://127.0.0.1:53
2024/02/23 01:03:37.711550 [info] dnsproxy: creating udp server socket [::1]:53
2024/02/23 01:03:37.711585 [info] dnsproxy: listening to udp://[::1]:53
2024/02/23 01:03:37.711594 [info] dnsproxy: creating tcp server socket 192.168.1.182:53
2024/02/23 01:03:37.711641 [info] dnsproxy: listening to tcp://192.168.1.182:53
2024/02/23 01:03:37.711647 [info] dnsproxy: creating tcp server socket [2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.711692 [info] dnsproxy: listening to tcp://[2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.711697 [info] dnsproxy: creating tcp server socket 172.30.32.1:53
2024/02/23 01:03:37.711730 [info] dnsproxy: listening to tcp://172.30.32.1:53
2024/02/23 01:03:37.711735 [info] dnsproxy: creating tcp server socket 127.0.0.1:53
2024/02/23 01:03:37.711770 [info] dnsproxy: listening to tcp://127.0.0.1:53
2024/02/23 01:03:37.711774 [info] dnsproxy: creating tcp server socket [::1]:53
2024/02/23 01:03:37.711810 [info] dnsproxy: listening to tcp://[::1]:53
2024/02/23 01:03:37.711874 [info] dnsproxy: entering udp listener loop on 127.0.0.1:53
2024/02/23 01:03:37.711957 [info] dnsproxy: entering udp listener loop on 192.168.1.182:53
2024/02/23 01:03:37.712021 [info] dnsproxy: entering udp listener loop on [::1]:53
2024/02/23 01:03:37.712027 [info] dnsproxy: entering udp listener loop on [2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.712100 [info] dnsproxy: entering udp listener loop on 172.30.32.1:53
2024/02/23 01:03:37.712110 [info] dnsproxy: entering tcp listener loop on 192.168.1.182:53
2024/02/23 01:03:37.712143 [info] dnsproxy: entering tcp listener loop on [2a01:e0a:ec:5530:2cca:c9d8:2b4d:bbc0]:53
2024/02/23 01:03:37.712163 [info] dnsproxy: entering tcp listener loop on [::1]:53
2024/02/23 01:03:37.712185 [info] dnsproxy: entering tcp listener loop on 172.30.32.1:53
2024/02/23 01:03:37.712191 [info] dnsproxy: entering tcp listener loop on 127.0.0.1:53
[01:03:37] INFO: Starting NGinx...
[01:03:37] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started 

I’ve already searched through YouTube and the forum, and I’ve restarted Home Assistant, AdGuard Home, and my internet box several times, but without success.

I can’t seem to identify the source of the problem. Do you have any suggestions for resolving this situation?