Adguard listening on 127.0.0.1 instead of the hassio ip?

Configuration
#1

Hello Fam,

I have hassio running on a RPI4 (IP reserved on Nest Wifi to 192.168.86.27). The Adguard Home was installed running successfully for more than 2 months now. When I opened it today - I noticed it stopped working at 3 in the morning and auto reset everything. The setuo guide section now says it’s litening in 127.0.0.1. First of all - WHY and HOW?
I tried to uninstall and reconfigure. It still is listening on that IP. I tried to set my DNS on my Nest Wifi to that but it is not not filtering nor listening. How do I fix it? ANy help would be appreciated. Pretty please.

3 Likes
#2

Just a me too here. Mine has been running fine for over a year and about a week ago just stopped. I noticed that it’s listening on 127.0.0.1 and see no way to change it. I run under Debian supervised and DO have a static IP set as well as external DNS servers set (9.9.9.9, 1.1.1.1)

Edit: I have also removed/re-installed the adguard add on with no change

#3

I have the exact same issue - let me know if you ever figure out a way to fix this please!

#4

Same here. It stopped working a few weeks a go and so only listening to 127.0.0.1, not to my hassio Pi IP address anymore. I did a reseach the whole day and did not find a solution.
I now installed Raspbian & AdGuardHome on a second Pi and it directly worked. But I’d like to get it back into Home Assistant agan :-/

#5

hi any solution to the above?

#6

Go to Adguard/Conf/AdGuardHome.yaml and edit the file adding your expected local IP address in the section dns: bind_hosts: restart Adguard image after that.

#7

I cannot find this file, where can this be found?

#8

I am using Debian so for me the exact location of this file is:

/usr/share/hassio/addons/data/a0d7b954_adguard/adguard/AdGuardHome.yaml

if you using a different installation it can be somewhere else.

#9

go to addons and supervisor, click adguard, go to configuration, edit yaml and set bind_hosts to 0.0.0.0

certfile: fullchain.pem
keyfile: privkey.pem
ssl: true
dns:
  bind_hosts:
    - 0.0.0.0
4 Likes
#10

Instead trying to force by adding config values, I chose to follow these steps https://www.reddit.com/r/homeassistant/comments/oeptmi/comment/h4bdhd8/?utm_source=share&utm_medium=web2x&context=3 which worked for me. All it required was saving the configuraiton page one time. Could probably save the configuration page before starting the first time and would solve the issue as well

2 Likes
#11

You are a great human being, thank you!

#12

I found that if your device is using DHCP for it’s IP address, AdGuard will use the loopback address of 127.0.0.1. Set a static address and AdGuard will update to that address after a stop/start. Found under: Setting>System>Network

3 Likes
#13

Just ran into this issue. Rebooting HA didn’t fix it. But, just before I went to reinstall Adguard Home, I clicked the restart button on the integration. Fixed, the setup page then showed it was listening on my 192.x LAN address, not 127.0.0.1

1 Like
#14

Seems like the issue is not fixed yet 03.2023, had to dig the internet and the solution was

Go into Home Assistant -> Settings -> Add ons -> AdGuard Home -> Configuration tag
Click the save button on the network card without changing anything (although the button looks like it is disabled, you can still click it) -> finally hit the restart button```
1 Like
#15

Thanks. I did that and now I get two errors every time I refresh the filter list.

image
image1284×2778 428 KB

image
image1284×2778 299 KB

#16

**[quote=“sirnicolas21, post:9, topic:310137, full:true”]
go to addons and supervisor, click adguard, go to configuration, edit yaml and set bind_hosts to 0.0.0.0

certfile: fullchain.pem
keyfile: privkey.pem
ssl: true
dns:
  bind_hosts:
    - 0.0.0.0

[/quote]

**

Adding the DNS bind worked like a charm!

1 Like
#17

I have the same 127.0.0.1 issue and no matter if I try the “Save” button in the network settings, update the AdGuard, change to static IP, change to external DNS, reboot, etc etc, it keeps showing the same 127.0.0.1.

Can someone shine some light on this noob query: how to I get to the “AdGuardHome.yaml” to change the bind_hosts? I have tried to find it with the File Editor or Studio Code Server but did not find it.

This the installation profile I got from the AdGuard log:

Add-on version: 4.8.4
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.4.1
Home Assistant Supervisor: 2023.04.0

Cheers!

1 Like