Getting the below error message. Changing the DNS port removes the error but the web ui does not load.
2019/01/10 20:03:36 Couldn't start forwarding DNS server, cause: couldn't listen to UDP socket, cause: listen udp :53: bind: address already in use
I’m having the same issue as @Maaniac it seems.
Upon starting the addon I get the normal start-up messages, then this:
2019/01/10 21:56:10 Creating the UDP server socket
2019/01/10 21:56:10 Couldn't start forwarding DNS server, cause: couldn't listen to UDP socket, cause: listen udp :53: bind: address already in use
Then it appears to try again, generating the same error repeatedly.
If I change the DNS port from 53 to something else, the addon starts and I can access the WebUI just fine.
Wohoo!
Since the launch of AdGuard Home I planned to try this. Also trying to find a suitable docker image etc.
And here we go, perfectly integrated into Hass.io.
Setup took no longer than 5 minutes, and the first ads are already blocked. The DNS with TLS is a great and appreciated plus.
Well done @frenck, thanks!
I am having trouble with this add-on.
I got it to load and have access to the web interface, but it isn’t blocking any ads.
I’m sorry I am not technical, and presume that is my problem.
I have set a static IP on my raspberry pi.
The static external DNS server issue is where I am uncertain.
I have Google WiFi. My DNS is set for automatic (8.8.8.8).
Should I change this setting to the ISP’s DNS? If that is my likely issue, other than making this add-on work, what potential risks come with this setting as opposed to the automatic setting?
I appreciate your patience and help!
After you have the addon running, it would be best to check the wiki for AdGuard Home itself for more information on how to use it:
In short, you change your router’s DNS to the box running this addon, then in the addon set the upstream DNS to google or cloudflare, or whatever you would like.
I’m not sure if you are having this problem for the same reason I am, but I think I found the solution for mine.
I’m running HassIO on an Ubuntu box. Ubuntu uses systemd-resolved which starts at boot and binds to port 53.
The “solution” was to disable it, by running Sudo systemctl disable system-resolved in the Ubuntu host, then editing /etc/resolv.conf so only my router was listed as a nameserver. Then reboot the host.
I’m not sure if this is the 100% correct way to fix the issue, but it seemed to work.
I use a raspberry pie.
Is it wrongly understood that on my router should set the DNS as my raspberry pie ip port 53? or is it only the ip?
Just the IP should be fine. The default DNS port is 53, so if you’re using that, the IP should be all that needs to be given.
Thanks very much for this info… I had to use a slightly different command but same result… it all seems to be working correctly now. 
sudo systemctl disable systemd-resolved.service
sudo reboot now
Hi guys,
I’m not 100% about the setup. My pi has an static IP address, but I’m not sure, what " static external DNS servers!" means.
Can somebody please explain what that means? Do I need to set anything here?
surely thats the DNS server(s) that you want Adguard to use for its DNS queries… ie: 8.8.8.8 or 1.1.1.1 or the default DNS server of your ISP. You would point your devices to Adguard (your RPi IP) but Adguard needs to resolve DNS queriers too so it needs an EXTERNAL IP to do so, such as those I gave above
Thanks! But where do I need to set this? Inside the AdGuard panel?
Currently I can’t access the panel. It asks me for my username and when I use my HA login, it tells me that this is wrong. Is this maybe caused by the activated 2fa?
Here is the issue from the log:
2019/01/18 13:29:42 [warn] 586#586: *9 [lua] ha-auth.lua:65: authenticate(): Authentication against Home Assistant failed!, client: 192.168.yyy.xx, server: _, request: "GET / HTTP/1.1", host: "192.168.yyy.xx:3210"
No, inside the adguard-home addon, under settings, is where you set your Upstream DNS servers.
The setting a static external DNS server for the PI is something separate, and not 100% necessary it seems, since I never bothered doing it and everything still works fine.
Thanks 
Any idea about the login issue?
I’m not having that issue, so I don’t have any ideas on what the issue is, but I can make some suggestions for troubleshooting.
First try leave_front_door_open: true in the configuration for the addon. That should disable authentication for it, which is not good and should not be left that way, but it will atleast give you an idea if you can get the addon running and get into it without issue, so the HA authentication must be the issue.
After testing that, remember to remove it when done testing.
Then I would try removing 2FA from HA and seeing if that improves things. I don’t personally use 2FA so I’m not sure how that works or more precisely how that works with addons. Have you used any other addons by Frenck with 2FA and not had issues, or might this be an issue for all addons?
Thanks for the quick help! I tried it out on my second HA instance and it worked there. So I’ll try your debug steps on my not working instance and try to figure out, what’s going wrong there.
I’ve had Adguard running in Hassio for a few days now, and it works great. The only issue I have noticed is I no longer get notifications using the notify call (send a notification to my phone). After some trial and error I’ve noticed that it stops working while Adguard is running, even if I have turned all filters off. The notify call works like a dream as soon as I have Adguard disabled again. I don’t think this is anything to do with my configuration?
Release v0.2.0Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Release v0.3.0Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Just in case you hadn’t noticed, 0.94 is out.