Just installed this Addon on new Rasperian Pi 4 with HomeAssistant.
I Could not get this Addon to work. IP was 127.0.0 etc.
After a Reboot thinks finaly worked.
Please add to the installation instructions after installation REBOOT the device just to be sure.
Hope this helps other new users who run into the same issues.
Greetings Alex
Hello,
I need a quick help.
I have hassio running on my Pi4 along with nginx, duckdns and AdGuardHome. everything works fine, but now I want to use TLS in AdGuard, but unfortunately nginx logically blocks port 443.
Now I would have to add the following in the Adguard Config:
allow_unencrypted_doh: false
but I can’t find the yaml anywhere, I already tried via ssh, samba share and file editor.
I just can’t find it.
Maybe I’m being too stupid 
Have you tried seperatig the MAC with : ?
I’ve worked around this problem y creating a 2nd ducksdns domain purely for doh. Setup Adguard to listen to domain name dns only, under Encryption>Server name
Example ‘nornal’ url:
Https://mysite.duckdns.org
Example doh URL:
Https://mysitedns.duckdns.org
Of course, the only works after configuring duckdns. This will also work with other DNS registration systems
Hello,
I’d like to access the AdGuardHome.yaml file to add a manual modification to it (as described in the help below).
Do you know how this can be done?
Thanks!
Im having a strange issue.
I have used Adguard for several months without fail.
First off, might be unrelated. I am running HassOS off my Proxmox server.
When I reboot the instance my network settings reset back to DHCP. Even after using the save command after editing through nmcli.
When I change the settings and point my router towards my Home Assistant installation with adguard installed I loose my external connection. If I turn the DNS setting off on my router my WAN connection resumes.
Here is my Network manager setup:
Router (192.168.1.1) is set up to use 192.168.1.39 as DNS.
Have I missed something obvious?
If you want to use Adguard as the DNS you need to set your DNS server to 192.168.1.39 on HA as well. You can also add googles dns as a backup as well
192.168.1.39, 8.8.8.8
Thank you for the suggestion.
I changed the DNS in HA to 192.168.1.39 and pointed my router towards the same IP for DNS queries. This kills my WAN connection. I am not able to do a single DNS request unless I remove the router setting.
This is getting stranger by the minute.
Where in your router did you plus this AdGuard Home IP? I mean is it under DHCP config? Or are we talking about the DNS for the router itself?
To narrow down the issue, what if we use 8.8.8.8 instead of 192.168.1.39? Would the internet name resolution come back?
Also when we say “no WAN”… is that zero traffic? Or is IP direct link OK, but just no name resolution?
=====
That said, the documentation / install guide of this AdGuard Home add-on (link here)
… specifically ask users to…
Ensure your Home Assistant device has a static IP and static external DNS servers! This is important! You WILL end up having issues if you skip this step.**
… and that was bullet point #1 on the install guide.
… and that means, in your setup, you probably should not use 192.168.1.1 nor 192.168.1.39, if I understand the doc correctly.
Where in your router did you plus this AdGuard Home IP? I mean is it under DHCP config? Or are we talking about the DNS for the router itself?
I have an ASUS router, so there is an entry for DNS under the WAN section. I have used this field with great success, pointing all my devices to the Adguard DNS previously:
To narrow down the issue, what if we use 8.8.8.8 instead of 192.168.1.39? Would the internet name resolution come back?
Setting 8.8.8.8 in the same field makes it work.
Also when we say “no WAN”… is that zero traffic? Or is IP direct link OK, but just no name resolution?
No WAN as in no WAN. My router looses external connection. Local IP direct links still work.
… and that was bullet point #1 on the install guide.
… and that means, in your setup, you probably should not use192.168.1.1nor192.168.1.39, if I understand the doc correctly.
I have tried 192.168.1.1, 192.168.1.39 as well as 8.8.8.8 in the DNS field on Home Assistant. All of them give the same results. Also, following that guide suggest the following if you click the link and scroll down:
In addition, it’s recommended to set the DNS server and the local gateway. For most home routers the DNS server will have the same IP address as the router itself. If you are using Pi-Hole or a third-party DNS system then you can set the DNS server to that.
nmcli> set ipv4.dns 192.168.100.1
nmcli> set ipv4.gateway 192.168.100.1
I did notice a very long process time in the log of Adguard while trying the settings mentioned above. Is my Adguard installation borked?
What DNS settings to you have in Adguard ? If Googles DNS works then the issue points to Adguard and its DNS settings.
What DNS settings to you have in Adguard ? If Googles DNS works then the issue points to Adguard and its DNS settings.
I have the default values from the installation.
Can you share a screen shot of what you have configured?
I mean inside AdGuard itself. Look under Settings then DNS Settings and share what you have configured there.
Here is mine
Its in the .pdf-file attached to my previous message. Here is a snippet:
The PDF was blocked on my work machine so could not open it.
Why don’t you try my settings as see if there is any change. Don’t forget to save any changes.
