AdGuard Home new installation on Home Assistant Green

Hello,

I just received the Home Assistant Green and I am trying to set up AdGuard Home for the first time. This is my first experience using Home Assistant so I am not sure what is going on and why AdGuard won’t block any adds.

I have everything installed and set the DNS settings in Home Assistant to the IP address for Home Assistant.

I then when and set the Home Assistant IP address in the DHCP settings of my router (TP Link Deco X75). I added the IP address of my router to the Client list in the AdGuard Settings. Did a reboot of AdGuard and then HA. I can see the HA IP address in the Setup guide for Adguard.

I can’t get any traffic to go through Home Assistant:

Is there anything else I could be missing?

Here is what I can see in the logs:

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: 4.8.15
You are running the latest version of this add-on.
System: Home Assistant OS 10.5 (aarch64 / green)
Home Assistant Core: 2023.9.3
Home Assistant Supervisor: 2023.09.2

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
[19:40:42] INFO: Starting AdGuard Home server…
2023/10/01 19:40:42.594967 [info] AdGuard Home, version v0.107.38
2023/10/01 19:40:42.603435 [info] tls: using default ciphers
2023/10/01 19:40:42.616045 [info] safesearch default: reset 253 rules
2023/10/01 19:40:42.624199 [info] safesearch client “Router”: reset 253 rules
2023/10/01 19:40:42.633980 [info] Initializing auth module: /data/adguard/data/sessions.db
2023/10/01 19:40:42.635559 [info] auth: initialized. users:0 sessions:0
2023/10/01 19:40:42.635690 [info] AdGuard Home updates are disabled
2023/10/01 19:40:42.635715 [info] web: initializing
2023/10/01 19:40:42.668604 [info] dnsproxy: cache: enabled, size 4096 b
2023/10/01 19:40:42.668671 [info] dnsproxy: max goroutines is set to 300
2023/10/01 19:40:42.669233 [info] AdGuard Home is available at the following addresses:
2023/10/01 19:40:42.669306 [info] go to http://127.0.0.1:45158
2023/10/01 19:40:42.669251 [info] clients: processing addresses
[19:40:43] INFO: Starting NGinx…
2023/10/01 19:40:43.604603 [info] dnsproxy: starting dns proxy server
2023/10/01 19:40:43.604719 [info] Ratelimit is enabled and set to 20 rps
2023/10/01 19:40:43.604744 [info] The server is configured to refuse ANY requests
2023/10/01 19:40:43.604760 [info] dnsproxy: cache: enabled, size 4194304 b
2023/10/01 19:40:43.604785 [info] dnsproxy: max goroutines is set to 300
2023/10/01 19:40:43.604841 [info] dnsproxy: creating udp server socket 192.168.68.77:53
2023/10/01 19:40:43.605083 [info] dnsproxy: listening to udp://192.168.68.77:53
2023/10/01 19:40:43.605119 [info] dnsproxy: creating udp server socket [fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.605291 [info] dnsproxy: listening to udp://[fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.605313 [info] dnsproxy: creating udp server socket 172.30.32.1:53
2023/10/01 19:40:43.605442 [info] dnsproxy: listening to udp://172.30.32.1:53
2023/10/01 19:40:43.605461 [info] dnsproxy: creating udp server socket 127.0.0.1:53
2023/10/01 19:40:43.605588 [info] dnsproxy: listening to udp://127.0.0.1:53
2023/10/01 19:40:43.605608 [info] dnsproxy: creating udp server socket [::1]:53
2023/10/01 19:40:43.605741 [info] dnsproxy: listening to udp://[::1]:53
2023/10/01 19:40:43.605780 [info] dnsproxy: creating tcp server socket 192.168.68.77:53
2023/10/01 19:40:43.605911 [info] dnsproxy: listening to tcp://192.168.68.77:53
2023/10/01 19:40:43.605931 [info] dnsproxy: creating tcp server socket [fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.606048 [info] dnsproxy: listening to tcp://[fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.606066 [info] dnsproxy: creating tcp server socket 172.30.32.1:53
2023/10/01 19:40:43.606162 [info] dnsproxy: listening to tcp://172.30.32.1:53
2023/10/01 19:40:43.606179 [info] dnsproxy: creating tcp server socket 127.0.0.1:53
2023/10/01 19:40:43.606269 [info] dnsproxy: listening to tcp://127.0.0.1:53
2023/10/01 19:40:43.606286 [info] dnsproxy: creating tcp server socket [::1]:53
2023/10/01 19:40:43.606385 [info] dnsproxy: listening to tcp://[::1]:53
2023/10/01 19:40:43.606667 [info] dnsproxy: entering udp listener loop on 127.0.0.1:53
2023/10/01 19:40:43.606848 [info] dnsproxy: entering udp listener loop on 192.168.68.77:53
2023/10/01 19:40:43.607010 [info] dnsproxy: entering udp listener loop on [fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.607124 [info] dnsproxy: entering udp listener loop on [::1]:53
2023/10/01 19:40:43.607154 [info] dnsproxy: entering udp listener loop on 172.30.32.1:53
2023/10/01 19:40:43.607345 [info] dnsproxy: entering tcp listener loop on [::1]:53
2023/10/01 19:40:43.607356 [info] dnsproxy: entering tcp listener loop on 192.168.68.77:53
2023/10/01 19:40:43.607451 [info] dnsproxy: entering tcp listener loop on [fd57:23a8:9a5f:44a9:5b06:47b2:b4a0:4624]:53
2023/10/01 19:40:43.607506 [info] dnsproxy: entering tcp listener loop on 172.30.32.1:53
2023/10/01 19:40:43.607514 [info] dnsproxy: entering tcp listener loop on 127.0.0.1:53
[19:40:44] 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
2023/10/01 19:42:20.581438 [info] safesearch client “Router”: reset 253 rules

Thanks!

Hmmm, my setup is;

  • have Adguard add-on
  • setup router to use Adguard dns server, so all traffic going through router will fly over Adguard.
  • i didn’t add any client to Adguard but i see only one client and it is just my router
1 Like

Thanks for pointing out my error! I removed my router IP from the client lists and then did a reboot and immediately I started seeing requests go through.

1 Like