search

hassio-addons / addon-adguard-home

AdGuard Home - Home Assistant Community Add-ons
https://addons.community
MIT License
388 stars 48 forks source link

AdGuard Home DNS server 127.0.0.1 only available #355

Closed tomi19921702 closed 1 year ago

tomi19921702 commented 1 year ago

Problem/Motivation

Couldn't set DNS server to 127.0.0.1 that was the only Ip shown in the setup guide also tried the HA IP.

Expected behavior

Actual behavior

Couldn't connect to DNS

Steps to reproduce

I Just freshly installed AdGuard on HA.

Proposed changes

Found on Reddit the info to add the bind_hosts:

  • 192.0.0.0 Function and added to the yaml manually. And it worked afterwards.
frenck commented 1 year ago

I'm not sure what to do with this issue, could you provide logs? Screenshots or something else?

The proposed change is not entirely clear to me, as there is no YAML involved in this process.

avlemos commented 1 year ago

trying to understand this bit of cryptic issue report, first time I installed AH as well, I had to specify to what IP address I wanted it to bind, as it was only biding to 127.0.0.1 by default (this is from memory, I haven't had this issue since).

frenck commented 1 year ago

I had to specify to what IP address I wanted it to bind, as it was only biding to 127.0.0.1 by default

That is not correct. The add-on binds to all public-facing addresses managed by the Supervisor. The add-on requests the Supervisor for those.

avlemos commented 1 year ago

well, fact of the matter is, when I did the first install, I did had to specify it. thinking this is what this person experienced as well, judging by the bind_hosts configuration parameter.

(I don't have this issue anymore, just thought I'd weigh in)

frenck commented 1 year ago

I did had to specify it.

No. You should not. The fact you did it is working around it? There is no user configuration option for it. It asks the supervisor for the available interfaces it manages and binds to it.

avlemos commented 1 year ago

what can I tell you? maybe something failed with the supervisor, because it definitely wasn't working, so I resorted to the manual Yaml configuration route thingy.

I'm happy, no beef here. Just trying to get ahead on what @tomi19921702 meant.

frenck commented 1 year ago

< so I resorted to the manual Yaml configuration route thingy

That is up to you, that is not how it should have been solved or how it should have been done. Those files are managed, poking around in those manually isn't supported.

Closing the issue on this end, as this is going nowhere.

../Frenck