Adguard listening on 127.0.0.1 instead of the hassio ip?

Hufflepuff-source · May 22, 2021, 10:26am

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.

roussell · May 30, 2021, 2:08pm

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

betaj · June 14, 2021, 6:53am

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

71n0 · June 20, 2021, 5:45pm

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 :-/

lumwh80 · December 15, 2021, 8:03am

hi any solution to the above?

Robbb · January 4, 2022, 11:04pm

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.

jjnj · February 28, 2022, 1:50pm

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

Robbb · March 3, 2022, 9:17pm

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.

sirnicolas21 · April 20, 2022, 12:29am

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

junja430 · May 14, 2022, 2:16pm

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

nimaghoroubi · July 10, 2022, 12:50pm

You are a great human being, thank you!

RockyN · October 29, 2022, 5:45pm

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

Paradroid888 · November 14, 2022, 9:41pm

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

dahkalsab · March 16, 2023, 7:49am

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```

Hufflepuff-source · March 16, 2023, 8:37am

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

TheRealFalseReality · March 31, 2023, 1:27am

**[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!

HoneyBadger100 · April 9, 2023, 2:36pm

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!

mrafayaleem · July 4, 2023, 8:06pm

This resolved my issue without setting static IP on my home assistant. This is what AdGuard configuration options say here:

If you want your server to accept requests on all interfaces and using both IP versions, for example if you run a public server, put one item with the unspecified IP of any version:

'dns':
    'bind_hosts':
    - '0.0.0.0'

Thanks a bunch!

FloatingBoater · October 14, 2023, 11:02am

There may be something odd going on with integration with HASSOS (although several versions newer than your original post HASS 2023.10.3 / HASSOS 11.0) as my AdGuard DHCP stopped working after a HASSOS update to v11.

This broke all IPv4 (IPv6 used autoconf) and changing config gave the same odd error (in text form to make it searchable for others…):

Error: control/dhcp/set_config | enabling dhcp: starting dhcp server: dhcpv6: finding interface eth0 by name: route ip+net: no such network interface | 400

Removing the extra dns: bind_hosts: config from the Addon config got DHCP working again, but it appeared blocking wasn’t working either. Re-adding the config back then seemed to work fine!

So…

Step 1 - remove `dns: bind_hosts:`

Settings → Addons → AdGuard Home → Configuration tab => (…) Edit in YAML and REMOVE three lines

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

Restart AdGuard.

Step 2 test AdGuard DHCP now works

Blocking probably doesn’t work.

Step 3 add back `dns: bind_hosts:`

Settings → Addons → AdGuard Home → Configuration tab => (…) Edit in YAML and ADD three lines

ssl: true
certfile: fullchain.pem
keyfile: privkey.pem
dns:                       <==== ADD BACK
  bind_hosts:              <==== ADD BACK
    - 0.0.0.0              <==== ADD BACK

Restart AdGuard.

Step 4 test AdGuard DHCP and blocking now works

Some other reports suggest just going into config and hitting save also fixed some issues (e.g. re-apply config).
I tried:

AdGuard → Settings → General Settings
Change nothing!
Save (Configuration successfully saved)

Then:

AdGuard → Settings → DHCP Settings
Select DHCP interface → Your LAN IP
Change nothing!
Save configuration (Configuration successfully saved - not no such network interface)

Why? Dunno!

LearningHASlowly · October 17, 2023, 2:15am

@FloatingBoater thanks for the tips

I’m curious: what are your HAOS networking ipv4 settings? Mine were all nulled out after the upgrade and I can’t recall what to put in the gateway and DNS fields. Is gateway my router address and DNS is the IP of my raspberry pi that is running home assistant? Or do I put external IP? Or router? It’s been running fine for so long I can’t remember how I had it setup…

Adguard listening on 127.0.0.1 instead of the hassio ip?

Step 1 - remove dns: bind_hosts:

Step 2 test AdGuard DHCP now works

Step 3 add back dns: bind_hosts:

Step 4 test AdGuard DHCP and blocking now works

Step 1 - remove `dns: bind_hosts:`

Step 3 add back `dns: bind_hosts:`