Home Assistant Community Add-on: AdGuard Home

Looks like you missed step one of the install instructions, hassio does have a valid dns during startup. Causing these errors.

Hi Franck,
I corrected the missing DNS server but still it doesnā€™t work. I hope you can help.
Here is the new trace log:
[08:49:43] TRACE: bashio::dns dns.info.host .host
[08:49:43] TRACE: bashio::cache.exists: dns.info.host
[08:49:43] TRACE: bashio::fs.file_exists: /dev/shm/bashio/dns.info.host.cache
[08:49:43] TRACE: bashio::cache.exists: dns.info
[08:49:43] TRACE: bashio::fs.file_exists: /dev/shm/bashio/dns.info.cache
[08:49:43] TRACE: bashio::api.hassio GET /dns/info false
[08:49:43] DEBUG: Requested API resource: http://hassio/dns/info
[08:49:43] DEBUG: Request method: GET
[08:49:43] DEBUG: Request data: {}
[08:49:43] DEBUG: API HTTP Response code: 200
[08:49:43] DEBUG: API Response: {ā€œresultā€: ā€œokā€, ā€œdataā€: {ā€œversionā€: ā€œ1ā€, ā€œlatest_versionā€: ā€œ1ā€, ā€œhostā€: ā€œ172.30.32.3ā€, ā€œserversā€: [ā€œdns://192.168.0.1ā€], ā€œlocalsā€: []}}

[08:49:43] TRACE: bashio::jq: {ā€œresultā€: ā€œokā€, ā€œdataā€: {ā€œversionā€: ā€œ1ā€, ā€œlatest_versionā€: ā€œ1ā€, ā€œhostā€: ā€œ172.30.32.3ā€, ā€œserversā€: [ā€œdns://192.168.0.1ā€], ā€œlocalsā€: []}}
.result
[08:49:43] TRACE: bashio::var.true: false
[08:49:43] TRACE: bashio::jq: {ā€œresultā€: ā€œokā€, ā€œdataā€: {ā€œversionā€: ā€œ1ā€, ā€œlatest_versionā€: ā€œ1ā€, ā€œhostā€: ā€œ172.30.32.3ā€, ā€œserversā€: [ā€œdns://192.168.0.1ā€], ā€œlocalsā€: []}}
if .data == {} then empty else .data end
[08:49:43] TRACE: bashio::var.has_value:
[08:49:43] TRACE: bashio::cache.set: dns.info {ā€œversionā€:ā€œ1ā€,ā€œlatest_versionā€:ā€œ1ā€,ā€œhostā€:ā€œ172.30.32.3ā€,ā€œserversā€:[ā€œdns://192.168.0.1ā€],ā€œlocalsā€:[]}
[08:49:43] TRACE: bashio::fs.directory_exists: /dev/shm/bashio
[08:49:43] TRACE: bashio::var.has_value: .host
[08:49:43] TRACE: bashio::jq: {ā€œversionā€:ā€œ1ā€,ā€œlatest_versionā€:ā€œ1ā€,ā€œhostā€:ā€œ172.30.32.3ā€,ā€œserversā€:[ā€œdns://192.168.0.1ā€],ā€œlocalsā€:[]} .host
[08:49:43] TRACE: bashio::cache.set: dns.info.host 172.30.32.3
[08:49:43] TRACE: bashio::fs.directory_exists: /dev/shm/bashio
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:49:43] INFO: Starting AdGuard Home serverā€¦
[08:49:43] TRACE: bashio::net.wait_for 45158 localhost 900
2020/01/12 08:49:43 [info] AdGuard Home, version v0.100.8, channel release

2020/01/12 08:49:43 [info] Upstream 0: https://dns.quad9.net:443/dns-query
2020/01/12 08:49:43 [error] Couldnā€™t load filter 2 contents due to stat /data/adguard/data/filters/2.txt: no such file or directory
2020/01/12 08:49:43 [error] Couldnā€™t load filter 3 contents due to stat /data/adguard/data/filters/3.txt: no such file or directory
2020/01/12 08:49:43 [error] Couldnā€™t load filter 4 contents due to stat /data/adguard/data/filters/4.txt: no such file or directory
2020/01/12 08:49:43 [info] Go to http://127.0.0.1:45158
2020/01/12 08:49:43 [info] Starting the DNS proxy server
2020/01/12 08:49:43 [info] Ratelimit is enabled and set to 20 rps
2020/01/12 08:49:43 [info] The server is configured to refuse ANY requests
2020/01/12 08:49:43 [info] DNS cache is enabled
2020/01/12 08:49:43 [info] Creating the UDP server socket
2020/01/12 08:49:43 [info] Listening to udp://[::]:53
2020/01/12 08:49:43 [info] Creating the TCP server socket
2020/01/12 08:49:43 [info] Listening to tcp://[::]:53
2020/01/12 08:49:43 [info] Entering the UDP listener loop on [::]:53
2020/01/12 08:49:43 [info] Entering the tcp listener loop on [::]:53
2020/01/12 08:49:43 [info] Couldnā€™t request filter from URL https://adaway.org/hosts.txt, skipping: Get https://adaway.org/hosts.txt: couldnā€™t initialize HTTP client or transport, cause: couldnā€™t initialize HTTP transport, cause: couldnā€™t bootstrap https://dns.quad9.net:443/dns-query, cause: couldnā€™t find any suitable IP address for host dns.quad9.net
2020/01/12 08:49:43 [info] Failed to update filter https://adaway.org/hosts.txt: Get https://adaway.org/hosts.txt: couldnā€™t initialize HTTP client or transport, cause: couldnā€™t initialize HTTP transport, cause: couldnā€™t bootstrap https://dns.quad9.net:443/dns-query, cause: couldnā€™t find any suitable IP address for host dns.quad9.net

2020/01/12 08:49:43 [info] Couldnā€™t request filter from URL https://hosts-file.net/ad_servers.txt, skipping: Get https://hosts-file.net/ad_servers.txt: couldnā€™t initialize HTTP client or transport, cause: couldnā€™t initialize HTTP transport, cause: couldnā€™t bootstrap https://dns.quad9.net:443/dns-query, cause: couldnā€™t find any suitable IP address for host dns.quad9.net
2020/01/12 08:49:43 [info] Failed to update filter https://hosts-file.net/ad_servers.txt: Get https://hosts-file.net/ad_servers.txt: couldnā€™t initialize HTTP client or transport, cause: couldnā€™t initialize HTTP transport, cause: couldnā€™t bootstrap https://dns.quad9.net:443/dns-query, cause: couldnā€™t find any suitable IP address for host dns.quad9.net

Just found a solution: I changed the bootstrap server in Adguard to the same as Hassio.
Thanks for pointing me in the right direction!

Do I have to set HassIO on a white-list or something like that, when using Adguard? I am asking because I donā€™t see any updates for add-ons or HassIO anymore. My Adguard Home add-on is on version 2.1.0 for example and there is no update available.

@anon90333909 That is usually caused by missing the first step in the add-on installation manual.

Thanks for your fast reply. I am using my fritz box to assign a fixed ip to my RaspberryPi. Local DNS is set there too. Do I need to set things up on my RaspberryPi using the network configuration?

Iā€™m unable to access my Hassio interface remotely after changing my router DNS settings to the IP of my Hassio and having AdGuard running (with protection enabled or disabled)., it just times out. When Iā€™m connected to the local network via WiFi it works just fine. What have I done wrong? :frowning:

Edit:
The following morning, without changing a thing everything seemed to have worked the way it should. Iā€™m so glad itā€™s working now and itā€™s great that it works with Ingress.

The manual says to use a static assigned IP, that is not static, you are using DHCP reservation, which will indeed get you into trouble.

1 Like

:tada: Release v2.3.1

Full Changelog

This is a general maintenance release.

:hammer: Changes

  • :arrow_up: Upgrades AdGuard Home to v0.100.9

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work:
https://github.com/sponsors/frenck or https://patreon.com/frenck

1 Like

Got it. It is working now. Thanks for your patience and hard work. Keep it up!

1 Like

Is there a way to filter the logs to see which adult content was blockedā€¦ hard to go through all blockedā€¦

unfortunately not :frowning:

@frenck, firstly a great add-on, thanks.
I am trying to get AdGuard set up correctly so that I can use it to allow the Mobile App to run on my local network. I followed your advice for adding the record in the DNS rewrite table, however the Home Assistant App still doesnā€™t work inside my home network.
My router doesnā€™t allow any DNS related settings, so cannot do anything on the router.
I am using the DuckDNS addon and have this configured with security

On windows, it uses my hassio as the DNS Server (I can see from IPCONFIG the DNS Server is set to 192.168.1.2 and get the expected response of 192.168.1.2 from a ping or nslookup of mydomain.duckdns.org.

To try and track down the issue, I have done the following:
I have enabled DNS over TLS in AdGuard from Settings, Encryption settings - I read somewhere that Android needs this to resolve DNS queries (is this correct?).
Ticked ā€˜Enable Encryptionā€™
added Server name (mydomain.duckdns.org) Redirect to HTTPS remains UNCHECKED
added certificates file path /ssl/fullchain.pem and private key path
restarted AdGuard

The Home Assistant App gives Unable to connect to Home Assistant error

I installed IP Tools on the phone to try and diagnose the problem further
If I do a DNS lookup from IP tools my mobile still gives the external IP (i.e. the one served by duckdns.org), so I assume that the mobile is using a different DNS server to look up the address.
I have flushed the DNS cache (from chrome) on the handset.
IP config on the mobile gives DNS1 as 192.168.1.2 and DNS 2 as 134744072 (DHCP server addon only has 192.168.1.2 set, and a domain of mydomain.local).
Any ideas?

@frenck Hi Franck! I have installed recently my AdGuard Add-on on my Hass.io. The ad blocking seems to work with mixed results(some ads are blocked and some not both on different websites and in Facebook), but in the add-on web UI dashboard I still donā€™t see any data. I donā€™t see any major issue in my log file (except the ā€œnginx: [alert]ā€¦ā€). What can be the problem?

I reach my HA from outside of my home network via mydomain.duckdns.org and SSL is activated for this connection. In my router (Netis WF2780) I have added as DNS server: 172.30.32.1

Here is my log data:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 2.3.1
 You are running the latest version of this add-on.
 System: HassOS 3.10  (armv7 / raspberrypi2)
 Home Assistant version: 0.105.4
 Supervisor version: 200
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adguard.sh: executing... 
[cont-init.d] adguard.sh: exited 0.
[cont-init.d] discovery.sh: executing... 
[00:26:55] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[00:27:00] INFO: Starting AdGuard Home server...
[services.d] done.
2020/02/16 00:27:01 [info] AdGuard Home, version v0.100.9, channel release
2020/02/16 00:27:01 [info] Upstream 0: https://dns.quad9.net:443/dns-query
2020/02/16 00:27:01 [info] Go to http://127.0.0.1:45158
[00:27:01] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
2020/02/16 00:27:05 [info] Starting the DNS proxy server
2020/02/16 00:27:05 [info] Ratelimit is enabled and set to 20 rps
2020/02/16 00:27:05 [info] The server is configured to refuse ANY requests
2020/02/16 00:27:05 [info] DNS cache is enabled
2020/02/16 00:27:05 [info] Creating the UDP server socket
2020/02/16 00:27:05 [info] Listening to udp://[::]:53
2020/02/16 00:27:05 [info] Creating the TCP server socket
2020/02/16 00:27:05 [info] Listening to tcp://[::]:53
2020/02/16 00:27:05 [info] Entering the tcp listener loop on [::]:53
2020/02/16 00:27:05 [info] Entering the UDP listener loop on [::]:53

It means you didnā€™t configure your network right, and are not using AdGuard.

@frenck Can you direct me at which part of my network settings should I check and reconfigure eventually?

In the add-on setup guide it is mentioned for the Router Setup that: ā€œThis setup will automatically cover all the devices connected to your home router and you will not need to configure each of them manually.ā€ This I already did as I mentioned in my previous comment. What else I should configure?

Dear Franck, first of all thank you for all your work and gratz for your new position!

I am running Docker on Ubuntu on a NUC. The add-on was running OK for about 2-3 weeks but some days now I donā€™t know what changed and it doesnt work.

 Add-on version: 2.3.1
 You are running the latest version of this add-on.
 System: Ubuntu 16.04.6 LTS  (amd64 / qemux86-64)
 Home Assistant version: 0.105.4
 Supervisor version: 200
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adguard.sh: executing... 
[cont-init.d] adguard.sh: exited 0.
[cont-init.d] discovery.sh: executing... 
[09:35:42] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[09:35:42] INFO: Starting AdGuard Home server...
2020/02/18 09:35:42 [info] AdGuard Home, version v0.100.9, channel release

2020/02/18 09:35:42 [info] Upstream 0: 1.1.1.1:53
2020/02/18 09:35:42 [info] Go to http://127.0.0.1:45158
2020/02/18 09:35:42 [info] Starting the DNS proxy server
2020/02/18 09:35:42 [info] Ratelimit is enabled and set to 20 rps
2020/02/18 09:35:42 [info] The server is configured to refuse ANY requests
2020/02/18 09:35:42 [info] DNS cache is enabled
2020/02/18 09:35:42 [info] Creating the UDP server socket
2020/02/18 09:35:42 [info] Listening to udp://[::]:53
2020/02/18 09:35:42 [info] Creating the TCP server socket
2020/02/18 09:35:42 [info] Listening to tcp://[::]:53
2020/02/18 09:35:42 [info] Entering the UDP listener loop on [::]:53
2020/02/18 09:35:42 [info] Entering the tcp listener loop on [::]:53
[09:35:42] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

NUC has static IP and in my mikrotik I have as DNS the IP of NUC.
pot 53 is bind for AdGuard.

Any help is apreciated!!!

@acme looks like we have the same problem (our log files are almost identical, except for the hardware). I am also waiting for an answer from @frenck.

Hi
yesterday I tried to install AdGuard on a Home Assistant running hassio on a RPI 4.
I access the instance via a https adress with cetificates and everything worked perfectly right out of the box.
The problem I have occurs when I enable the encryption part in the AdGuard settings.
The setup of the encryption pace asks for my domain and the cetrificates which were accepted without problems. But After activating I cannot get to the settings page within HA anymore.

Can anybody point me in the rigt direction to fix this?

thanks and regards
Chris

I installed pi-hole and had the same problem.
Unistalled both of them and tried to install adguard again but I get an error message saying ā€œFailed to install addon, Unknown Error, see logsā€.
Then in logs:

20-02-20 22:18:49 ERROR (SyncWorker_15) [hassio.docker.interface] Can't install hassioaddons/adguard-amd64:2.3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38263->[::1]:53: read: connection refused").

I have no idea what I should doā€¦
Portainer screenshot in case it helps:
image
:exploding_head: