Useful or not, from you.
addon-adguard-home AdGuard doesn't listen on right interface anymore.

Problem/Motivation

AdGuard not listening on LAN IP anymore, just on internal Home-Assistant Interface

Expected behavior

AdGuard should bind to local LAN IP instead of Home-Assistant IP

Actual behavior

----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 4.1.6
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.13  (armv7 / raspberrypi4)
 Home Assistant Core: 2021.5.5
 Home Assistant Supervisor: 2021.04.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to NOTICE
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adguard.sh: executing... 
[16:39:15] ERROR: Got unexpected response from the API: Interface default does not exist
[cont-init.d] adguard.sh: exited 0.
[cont-init.d] discovery.sh: executing... 
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2021/05/20 16:39:17.802549 [info] AdGuard Home, version v0.106.3
2021/05/20 16:39:17.844019 [info] Initializing auth module: /data/adguard/data/sessions.db
2021/05/20 16:39:17.844963 [info] auth: initialized.  users:0  sessions:0
2021/05/20 16:39:17.845106 [info] Initialize web module
2021/05/20 16:39:18.018512 [info] Go to http://127.0.0.1:45158
2021/05/20 16:39:19.137392 [info] Starting the DNS proxy server
2021/05/20 16:39:19.137615 [info] Ratelimit is enabled and set to 20 rps
2021/05/20 16:39:19.137678 [info] The server is configured to refuse ANY requests
2021/05/20 16:39:19.137702 [info] DNS cache is enabled
2021/05/20 16:39:19.137730 [info] MaxGoroutines is set to 50
2021/05/20 16:39:19.137793 [info] Creating the UDP server socket
2021/05/20 16:39:19.138117 [info] Listening to udp://172.30.32.1:53
2021/05/20 16:39:19.138168 [info] Creating a TCP server socket
2021/05/20 16:39:19.138362 [info] Listening to tcp://172.30.32.1:53
2021/05/20 16:39:19.138591 [info] Entering the tcp listener loop on 172.30.32.1:53
2021/05/20 16:39:19.138951 [info] Entering the UDP listener loop on 172.30.32.1:53

Steps to reproduce

Don't know what caused it, but it is since this morning (around 10:00 CEST) that the device is not listening anymore. Also an update from 4.1.2 to 4.1.6 didn't fixed it, and I rebooted a couple of times since then.

Proposed changes

see discussion: https://github.com/hassio-addons/addon-adguard-home/discussions/192

That's a useful answer
Without any help

Same problem here. Using HAOS 6.0. I've configured the static IP using nmcli, but AdGuard Home addon still listens to 127.0.0.1. Thought it can detect the host network interface in the DHCP settings page.


After I restart supersivor first and then the addon, it seems to be able to listen to my LAN ip.