AdGuard Home - Internet doesn't work

Installation
1

Hello Friends,

I recently migrated from Home Assistant Supervised to HASS OS.

After setting up the AdGuard Home add-on, I encountered an issue where the internet doesn’t work on the first boot (for example, after a power outage). I have to manually restart the AdGuard Home add-on, and only then does the internet start working.

I’m running HASS OS on a Raspberry Pi 4B. I’ve configured a static IP address of 192.168.1.5, with the gateway set to 192.168.1.1 and DNS set to 8.8.8.8.

On my router, I’ve set the DNS server to the Raspberry Pi’s IP (192.168.1.5), as I had done previously on Home Assistant Supervised—where everything worked without issues.

However, since switching to HASS OS, the internet doesn’t come up properly until I restart the AdGuard Home add-on manually.

Am I missing something in the configuration ? Any guidance would be greatly appreciated.

Thanks in advance,
Neha

2

Just checking, but do you have “Start on boot” and “Watchdog” enabled?

3

Yes both are enabled

4

Take a look at the log. What is it saying. If you don’t see it now, you may want to try a reboot or a cold start to see the log on start-up.

5

Maybe its a chicken and egg issue.
HA needs to contact a server on the internet to set time, before boosting up.
AdGuard can not startup until HA is running, maybe due to HA running in host mode.

6

Please find the log below

-----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 5.2.10
 You are running the latest version of this add-on.
 System: Home Assistant OS 15.2  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2025.6.3
 Home Assistant Supervisor: 2025.06.1
-----------------------------------------------------------
 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
[22:56:03] INFO: Starting AdGuard Home server...
2025/06/25 22:56:04.321610 [info] AdGuard Home, version v0.107.62
2025/06/25 22:56:04.361921 [info] tls_manager: using default ciphers
2025/06/25 22:56:04.378240 [info] safesearch: reset rules count=258
2025/06/25 22:56:04.396441 [info] Initializing auth module: /data/adguard/data/sessions.db
2025/06/25 22:56:04.405739 [info] auth: initialized.  users:1  sessions:3
2025/06/25 22:56:04.405893 [info] webapi: initializing
2025/06/25 22:56:04.566672 [info] dnsproxy: upstream mode is set mode=load_balance
2025/06/25 22:56:04.566781 [info] dnsproxy: cache enabled size=4096
2025/06/25 22:56:04.567700 [info] dnsproxy: max goroutines is set count=300
2025/06/25 22:56:04.568169 [info] dnsproxy: ratelimit is enabled rps=20 ipv4_subnet_mask_len=24 ipv6_subnet_mask_len=56
2025/06/25 22:56:04.568246 [info] dnsproxy: server will refuse requests of type any
2025/06/25 22:56:04.568276 [info] dnsproxy: upstream mode is set mode=load_balance
2025/06/25 22:56:04.568295 [info] dnsproxy: cache enabled size=4194304
2025/06/25 22:56:04.568332 [info] dnsproxy: max goroutines is set count=300
2025/06/25 22:56:04.570727 [info] addrproc: processing addresses
2025/06/25 22:56:04.571319 [info] webapi: AdGuard Home is available at the following addresses:
2025/06/25 22:56:04.571408 [info] go to http://127.0.0.1:45158
2025/06/25 22:56:04.571549 [info] starting plain server server=plain addr=127.0.0.1:45158
[22:56:04] INFO: Starting NGinx...
[22:56:05] 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
2025/06/25 22:56:08.022905 [info] dnsproxy: starting dns proxy server
2025/06/25 22:56:08.024380 [info] dnsproxy: creating udp server socket addr=172.30.32.1:53
2025/06/25 22:56:08.025043 [info] dnsproxy: listening to udp addr=172.30.32.1:53
2025/06/25 22:56:08.025150 [info] dnsproxy: creating udp server socket addr=127.0.0.1:53
2025/06/25 22:56:08.027061 [info] dnsproxy: listening to udp addr=127.0.0.1:53
2025/06/25 22:56:08.027177 [info] dnsproxy: creating udp server socket addr=[::1]:53
2025/06/25 22:56:08.027797 [info] dnsproxy: listening to udp addr=[::1]:53
2025/06/25 22:56:08.027867 [info] dnsproxy: creating tcp server socket addr=172.30.32.1:53
2025/06/25 22:56:08.028268 [info] dnsproxy: listening to tcp addr=172.30.32.1:53
2025/06/25 22:56:08.028345 [info] dnsproxy: creating tcp server socket addr=127.0.0.1:53
2025/06/25 22:56:08.028666 [info] dnsproxy: listening to tcp addr=127.0.0.1:53
2025/06/25 22:56:08.028745 [info] dnsproxy: creating tcp server socket addr=[::1]:53
2025/06/25 22:56:08.033302 [info] dnsproxy: listening to tcp addr=[::1]:53
2025/06/25 22:56:08.040051 [info] dnsproxy: entering udp listener loop addr=172.30.32.1:53
2025/06/25 22:56:08.040052 [info] dnsproxy: entering udp listener loop addr=127.0.0.1:53
2025/06/25 22:56:08.040364 [info] dnsproxy: entering listener loop proto=tcp addr=172.30.32.1:53
2025/06/25 22:56:08.040669 [info] dnsproxy: entering listener loop proto=tcp addr=127.0.0.1:53
2025/06/25 22:56:08.043189 [info] dnsproxy: entering udp listener loop addr=[::1]:53
2025/06/25 22:56:08.046752 [info] dnsproxy: entering listener loop proto=tcp addr=[::1]:53
7

Any fix, any solution ? Please advise.

8

Really no idea. But as a work-around, you could create an automation that reloads the adguard add-on after a start of HA

9

I would recommend, for the machine, (home assistant), that you are using for AdGaurd, use a static ip configuration and set the DNS to the DNS your ISP offer or one of the free DNS services. This will allow Home Assistant to start without any issues if AdGuard hasn’t started as yet.

There are some free DNS providers like OpenDNS and Cloudflare that will give you basic adware/malware support if that is needed for your Home Assistant machine.

If you choose to setup use a static setup, got to System then Network then Configure network interfaces then select IPv4

10

I am doing it like this only…

11

Using static ip with dns 8.8.8.8 and 1.1.1.1 but still internet wont work until i restart the AdGuard addon.