Problem/Motivation

Working, but no web ui

Expected behavior

It was working, then next day it stopped working. It still respond to DNS queries properly, just the UI does not start.

Actual behavior

One press the "Start" button, it spins for a second, and becomes "start" again. There is no log, even when log_level: trace is set.

Steps to reproduce

I would like to know.

Proposed changes

I would know how to see a log of this thing, since the log on the hassio UI is not showing

Actual behavior

After restarting the addon all configured static and dynamic dhcp leases are gone.

Expected behavior

Restarting the addon should not cause that dhcp leases get deleted.

Steps to reproduce

• Add static dhcp leases
• Restart the addon
• Check dhcp leases again -> the list is empty

Problem/Motivation

Since update to HA 0.101.0 and Ad-Guard-Addon from 2.1 to 2.2.3
HomeAssistant shows the "sensor.adguard_average_processing_speed" now in seconds,
not millisesconds anymore.
Adguard-addon displays it still in "msec".

Don't know if the add-on transfers a wrong value to HA or HA recalculates it to seconds by its own,
so i post the report here first.

Expected behavior

show "sensor.adguard_average_processing_speed" in milliseconds again

Actual behavior

"sensor.adguard_average_processing_speed" shows value in seconds

Steps to reproduce

RaspberryPi 2
HAssIO Supervisor : 192
HassOS : 2.12
Home-Assistant : 0.101.0 and 0.101.1
AdGuard-Addon : 2.2.3

Screenshots

Graph shows values prior update and afterwards.
According to AdGuard-addon processing speed is between 30 and 40 msec.

Problem/Motivation

can't setup localhost

Expected behavior

I hope it could resolve my ha host address locally, like 192.168.1.130

Actual behavior

However, after I set it up and restart the addon, adguard dns still responds with public ip address.

Steps to reproduce

do exactly what I did

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Hosts do not resolve

Problem/Motivation

When Hassio has multiple IP addresses, AdGuard Home give a response from a different IP than the incoming IP address

Expected behavior

Reply from the right IP address

Actual behavior

Reply from a different IP.
[bakkerl@moros ~]$ nslookup google.com 192.168.75.9
;; reply from unexpected source: 192.168.75.17#53, expected 192.168.75.9#53
;; reply from unexpected source: 192.168.75.17#53, expected 192.168.75.9#53
;; reply from unexpected source: 192.168.75.17#53, expected 192.168.75.9#53
;; connection timed out; no servers could be reached

Steps to reproduce

• Default installation of Hassio (On Raspbarry)
• Add IP address on the same network.
• Install AdGuard Home addon
• Do DNS request to the added IP address.

Configure devices in the addon says:
Configure your devices
To start using AdGuard Home, you need to configure your devices to use it.
AdGuard Home DNS server is listening on the following addresses:
127.0.0.1
192.168.75.17
192.168.78.18
192.168.75.18
192.168.75.9
172.30.32.1
172.17.0.1

Problem/Motivation

after switching the DNS entry to the IP of the home assistant host, the adblocker starts working. But from now on, it is not possible to connect to the home assistant backend via DnS (DuckDNS).

Expected behavior

successful accessing the home assistant backend via IP AND DNS

Actual behavior

no access to the home assistant backend via DNS (DuckDNS). via IP address the access is still possible. Safari error message: „FetchEvent.respondWith received an error: no-response: no-response :: [{"url":"https://XYZ.duckdns.org/lovelace/default_view","error":{}}]“

Chrome error message: NET::ERR_CERT_INVALID

Is there a known issue in combination with the addon nginx proxy manager?

Steps to reproduce

see Problem/Motivation

Problem/Motivation

On slower devices (e.g., Pi or when using an external HDD over USB) and having a large query log, the startup of AdGuard might not succeed within the max wait timeout that NGinx has.

This causes the add-on startup to be aborted.

Expected behavior

Add-on to start, even if it takes longer

Actual behavior

Add-on startup get aborted after 60 seconds.

Steps to reproduce

Have a large query log on a slower I/O device.

Proposed changes

Extend wait timeout for NGinx to 15 minutes.

When HA reboots, Adguards "Custom filtering rules" need to be reapplied. It appears the Custom filtering rules and not being read on boot.

Problem/Motivation

Today I migrated from the working pihole HassIO addon to adguard. DNS lookups work fine in the overall network, however, home assistant (including addons) can't resolve DNS names anymore.

Expected behavior

Home Assistant and addons are able to resolve DNS hostnames.

Actual behavior

Home Assistant and addons are unable to resolve DNS hostnames, returning errors along the lines of try again. Manual calls to dig google.com via the SSH-Addon time out.

Steps to reproduce

Not sure if reproducible or not. Moving back to pihole does not seem to restore DNS resolution.

Proposed changes

None.

I am Hassio user, I used Pi Hole and i starting use Ad Guard, but when i try to use it when i connected through to Wireguard VPN, ad guard service does not work, i have not any DNS resolution.

I think the problem is because ad guard is not listening in the correct network interface. When i used Pi Hole, i could choose where service was waiting petitions.

Is this capability available in Ad Guard?

Problem/Motivation

Adguard-Addon does not start on Odroid C2 (log below)
aarch64 / HassOS 2.8 / HA 0.87.0 / SU 143 / stable

Actual behavior

[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 v0.1.1
Network-wide ads & trackers blocking DNS server.
From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

aarch64 / HassOS 2.8 / HA 0.87.0 / SU 143 / stable
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-nginx.sh: executing...
[cont-init.d] 11-nginx.sh: exited 0.
[cont-init.d] 20-config.sh: executing...
[cont-init.d] 20-config.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2019/02/08 13:28:02 AdGuard Home web interface backend, version v0.92-hotfix2
2019/02/08 13:28:02 Current working directory is /opt/AdGuardHome
2019/02/08 13:28:02 main.upgradeConfig(): got schema version 2
2019/02/08 13:28:02 Reading YAML file: /opt/AdGuardHome/data/AdGuardHome.yaml
2019/02/08 13:28:02 Loading filter 1 contents to: /opt/AdGuardHome/data/filters/1.txt
2019/02/08 13:28:02 File /opt/AdGuardHome/data/filters/1.txt, id 1, length 507908
2019/02/08 13:28:02 Downloading update for filter 1 from https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
2019/02/08 13:28:07 Filter 1 has been updated: 508024 bytes, 26406 rules
2019/02/08 13:28:07 Saving filter 1 contents to: /opt/AdGuardHome/data/filters/1.txt
2019/02/08 13:28:07 Writing YAML file: /opt/AdGuardHome/data/AdGuardHome.yaml
2019/02/08 13:28:07 Writing YAML file: /opt/AdGuardHome/data/AdGuardHome.yaml
2019/02/08 13:28:07 Creating dnsfilter
2019/02/08 13:28:07 Loading stats from querylog
2019/02/08 13:28:07 Starting the DNS proxy server
2019/02/08 13:28:07 Ratelimit is enabled and set to 20 rps
2019/02/08 13:28:07 The server is configured to refuse ANY requests
2019/02/08 13:28:07 DNS cache is enabled
2019/02/08 13:28:07 Creating the UDP server socket
2019/02/08 13:28:07 Listening to udp://[::]:53
2019/02/08 13:28:07 Creating the TCP server socket
2019/02/08 13:28:07 Listening to tcp://[::]:53
2019/02/08 13:28:07 Go to http://127.0.0.1:37043
2019/02/08 13:28:07 Entering the UDP listener loop on [::]:53
2019/02/08 13:28:07 Entering the TCP listener loop on [::]:53
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)

Problem/Motivation

DNS resolution on Hassio broken after Adguard installation.

Expected behavior

DNS resolution should be faster after the installation

Actual behavior

DNS resolution become slower and it just stop working after a while. The MET weather information will stop working, installation via Supervisor and Integrations also stopped working. Pointing out to DNS issue

Steps to reproduce

• Fresh install of Hassio on RPI2 supervised mode.
• Install Adguard add-ons and point router DNS to Adguard. At the beginning DNS resolution works but after 2 hours you will start getting network problem.
• I have even added Google DNS(8.8.8.8 and 8.8.4.4) into the upstream DNS. That can resolve the resolution of other devices when querying to Hassio, but not DNS resolution on the Hassio itself.
• The attempt to get version info from Reload in Supervisor > System failed
• I cant install anything from Integrations
• Have rebooted twice
• Even after removing the Adguard and reboot the host, DNS is still problematic
• I have rerun this same process like 3 times, the past 2 days to confirm there's some issue with Adguard and decided to dump Adguard altogether

Proposed changes

N/A

Problem/Motivation

I wanted to set up adguard to be my dns resolver anywhere, not just my local instance. In order to do that I need to set up the encryption options in adguard so that I can communicate it with it using dns-over-https. I am not comfortable communicating with my adguard instance from outside my network unencrypted.

Expected behavior

In the adguard add-ons settings, there's an option for "encryption settings". It's pretty straightforward, it asks you to provide a port, a domain name and a certificate to use. I filled those out and it saved. I then expected to be able to test it via curl and do dns resolutions via the dns-over-https syntax.

Actual behavior

Nothing happened. The port did not respond at all, nothing was listening. I tried enabling the web UI port to see if maybe enabling this option required using it in non-ingress mode but that didn't change anything. I could not make dns-over-https calls to the adguard instance

Steps to reproduce

See above. Just fill out the info on the encryption settings. You should then be able to test it by simply hitting the URL 'https://{HA base URL}:{port you choose}/dns-query?name=example.com&type=AAAA' and get a response similar to what you see here in cloudflare's docs

Proposed changes

I would like this settings panel to basically do what it says it does. When the encryption options are filled out and a port is provided for DoH then it starts a DNS-over-HTTPS server to listen for those types of DNS queries. It should also probably start a DoT server if the port is provided for that option as well since that is what it says it does.

Problem/Motivation

AdGuard Home has a set of configuration settings of its own. HA does not appear to be sending any add-on configuration settings through to AdGuard Home.

Expected behavior

When I attempt to pass in configuration settings, I expect them to configure AdGuard Home. For example:

dns:
  bind_host: 192.168.1.10

Actual behavior

AdGuard Home does not appear to be getting the configuration, it does not bind to a specific host:

2020/05/29 18:44:54 [info] Creating the UDP server socket
2020/05/29 18:44:54 [info] Listening to udp://[::]:53
2020/05/29 18:44:54 [info] Creating the TCP server socket
2020/05/29 18:44:54 [info] Listening to tcp://[::]:53
2020/05/29 18:44:54 [info] Entering the UDP listener loop on [::]:53
2020/05/29 18:44:54 [info] Entering the tcp listener loop on [::]:53

Steps to reproduce

Try to add configuration values for AdGuard Home, AdGuard Home should configure itself based on configuration values:

dns:
  bind_host: 192.168.1.10

Proposed changes

Bindly pass-through the configuration as yaml to AdGuard Home on start: ./AdGuardHome -c configuration.yaml

It's assumed AdGuard Home would ignore any YAML settings it doesn't understand.

Problem/Motivation

I am trying to automate the enabling/disabling of certain blocklists. Currently the adguard.disable_url service is not functioning as expected.

Expected behavior

Calling adguard.disable_url should disable the url. Leaving the name and URL intact

- service: adguard.disable_url data: url: https://example.example/filter.txt

Actual behavior

The item is left in a ghost state. With no name, URL. Any attempt to delete/edit this entry is met with an error. You also cannot use adguard.enable_url to recover the entry.

Steps to reproduce

Using the latest version 2.3.3
Add your own blocklist (have not verified on the default lists)
Attempt to disable a block list using adguard.disable_url

Proposed changes

Have the adguard.disable_url just disable the blocklist, in the same manner, click the 'Enabled' checkbox in the GUI would.

Problem/Motivation

When i block the services of Facebook, Whatsapp, Instagram, Youtube the apps on Android Phone still work fine.
The Websites are blocked, but the apps somehow circumvent this.

Expected behavior

If i block Netflix, the Netflix App does not work anymore. I would expect the same also for the other apps. Is there a way to make this work? Do i need to enable a specific setting for them?

Problem/Motivation

Wrong value shown by sensor.adguard_average_processing_speed.

Expected behavior

sensor.adguard_average_processing_speed shows the same value as "Average processing time" in the AdGuard UI.

Actual behavior

sensor.adguard_average_processing_speed constantly shows 0.01 ms.
The AdGuard UI shows 8 ms for "Average processing time".

Update

sensor.adguard_average_processing_speed seems to show seconds instead of milliseconds.
sensor.adguard_average_processing_speed now shows 0.03 ms while the AdGuard UI shows 30 ms.

Steps to reproduce

Probably compare 2.1.0 against 2.2.x since this is when the misbehavior started for me.

Proposed changes

Change scaling or unit of sensor.adguard_average_processing_speed

Additional information

Hass.IO 0.101.3 in Docker in Ubuntu on NUC8I3.
Neither restarting the AddOn nor Hass.IO fixes the issue.

Problem/Motivation

Not starting anymore after 2.4.1 update

Expected behavior

It starts

Actual behavior

Does not start, no log in supervisor

Steps to reproduce

Just start it

Proposed changes

Not sure, something must be broken

Problem/Motivation

The latest changes need some defensive coding changes.

Expected behavior

To be able to update to a new version without worrying about the container refusing to start.

Actual behavior

NGinx crashes on startup and takes the container down with it.
[11:39:22] INFO: Starting NGinx...
nginx: [emerg] invalid port in upstream "127.0.0.1:0" in /etc/nginx/includes/upstream.conf:2

See edd538a#r39556479

Steps to reproduce

Enable Encryption and clear the HTTPS port. Restart the addon.

Proposed changes

Check if the port in the configuration is 0 and if so don't update upstream.conf?

When I turn on Adguard Home, Tuya component cannot send request.

I tried to turn off all filters but it still have error.
Only when I turn off Adguard, Tuya component comeback

Problem/Motivation

I'm currently attempting to migrate from the pi.hole add-on for Home Assistant. In the pi.hole add-on it was possible to create a hosts mapping in the config, using the hosts dictionary.

According to this PR it is possible to use the /etc/hosts file to add mappings for LAN devices.

Proposed changes

Ability map LAN devices to /etc/hosts by allowing a hosts configuration just like the pi.hole add-on YAML.

Problem/Motivation

I can't configure AGH's internal DHCP server.

Expected behavior

DHCP is configured and works.

Actual behavior

I have HassOS configured with a static IP, 192.168.0.2, assigned directly to the interface. I see 3 interfaces in my dropdown: eth0/192.168.0.2, docker0/172.17.0.1, hassio/172.30.32.1. No matter which I select, I get the following message:

In order to use DHCP server a static IP address must be set. We failed to determine if this network interface is configured using static IP address. Please set a static IP address manually.

I don't understand where else AGH expects the interface to be manually configured. Further, selecting eth0 in the configuration dropdown displays:

    MTU: 1500
    Hardware address: b8:27:eb:79:dc:60
    IP addresses: 192.168.0.2

so it does seem to see an address. Further, clicking the error details link displays:

open /etc/dhcpcd.conf: no such file or directory

which is true, the file doesn't exist. Odd that these appear to be two different errors--one network, one file-related, and that the file-related error is displayed as a failure to determine the static IP.

Steps to reproduce

1. From the DHCP settings screen, select the router-facing network interface with a statically-configured IP--eth0, in my case.
2. Set gateway to 192.168.0.1.
3. Set netmask to 192.168.255.255.
4. Set start to 192.168.0.100.
5. Set end to 192.168.0.254.
6. Click Save.

Thanks for making this addon, it's super helpful. I'm wondering if it would be possible to add an option to not keep statistics, for privacy reasons? I'd prefer not to record what DNS requests my roommates are making.

Problem/Motivation

I am using the Router option, meaning Adguard is the DNS for the whole network.
Adguard doesn't start when restarting the docker service (and perhaps the same would happen when restarting the host server).

Expected behavior

Adguard should start in order to resolve DNS requests for the whole network

Actual behavior

The hassio-supervisor doesn't start because there is no internet (since Adguard is not started).
And Adguard is not starting because it cannot connect to the hassio API for authentication.

Steps to reproduce

Install/run Adguard
Setup Adguard as DNS server in your router WAN setup
Restart the docker service or host server
Hassio supervisor will not start since the router cannot resolve DNS requests
Adguard will not start because hassio is not started

Proposed changes

Add the ability to start Adguard without API connection (perhaps via command line), or perhaps removing the use of the hassio authentication, due to the nature of this Add-on.

A less than ideal workaround is to change the router settings temporarily to a non-local DNS, but this causes all network devices (router, 2 switches, several access points) to be re-configured, which takes time to setup and to revert back to the desired state. This allows to start the supervisor and then Adguard, finally the network devices needs to be setup to use Adguard again.

Problem/Motivation

AdGuard Home addon, by default, binds to all addresses on the system. If you're multi-homed, it's going to bind to every single address, [::]:53. When using vlans, this starts causing oddities in DNS responses.

From a 192.168.1.x host to 192.168.2.10 AdGuard Home

➜  ~ nslookup google.com 192.168.2.10    
;; reply from unexpected source: 192.168.1.10#53, expected 192.168.2.10#53

From a 192.168.2.x host to 192.168.1.10 AdGuard Home

~ $ nslookup google.com 192.168.1.10
;; reply from unexpected source: 192.168.2.10#53, expected 192.168.1.10#53

I want the ability to pass AdGuard Home configurations to the docker container so I can use dns.bind_host and control what interface(s) for AdGuard Home to listen on.

Expected behavior

When I add dns.bind_host to the configuration, I expect AdGuard home to bind to only that host:

Add On Config

ssl: true
certfile: me.com.cert
keyfile: me.com.key
dns:
  bind_host: 192.168.1.10

Actual behavior

AdGuard Home still continues to bind on all hosts:

2020/05/29 18:44:54 [info] Creating the UDP server socket
2020/05/29 18:44:54 [info] Listening to udp://[::]:53
2020/05/29 18:44:54 [info] Creating the TCP server socket
2020/05/29 18:44:54 [info] Listening to tcp://[::]:53
2020/05/29 18:44:54 [info] Entering the UDP listener loop on [::]:53
2020/05/29 18:44:54 [info] Entering the tcp listener loop on [::]:53

Steps to reproduce

Requires you to run AdGuard Home as the addon on a multi-homed (I'm using VLAN'd) host.

Proposed changes

Bindly pass-through the configuration as yaml to AdGuard Home on start: ./AdGuardHome -c configuration.yaml

In theory AdGuard Home should ignore any YAML values it doesn't understand.

Problem/Motivation

I have Hassio running on an Odroid board (ArchLinuxARM)
I used the standard install process for generic linux with Docker.
Problem is Adguard can not be started on port 53 (already in use by hassio_dns

Expected behavior

Adguard should be running on default port 53, so that it can be used by all machines on network
For example:
LAN >>> Adguard (53) >>> forward to trusted DNS or local Unbound DNS
Hassio containers >>> Internal Hassio DNS (for addons IP resolution) or Aguard as default

Actual behavior

Default 53 port is already in use by hassio-dns, which by the way forward queries to 8.8.8.8 or 1.1.1.1... That's exactly what I want to avoid. I have my own Unbound DNS server for all my network but wanted to add Adguard in front of it to filter what's going through

Steps to reproduce

Start Hassio
Start Adguard

Proposed changes

I tried to mess around with hassio_dns configuration files without success:

• corefile
• hosts

Hi

The plugin worked great for two days then it stopped resolving domains that are not blocked, The requests for these domains does not even show in the Query Log, it only shows the blocked requests.
No errors in HomeAssistant's log file
I switched of Protection but that also did not resolve the issue
The only way to get my internet working again was to not use Adguard as the DNS anymore.
(I did not try rebooting homeAssitant, perhaps I should have)
Using the default "https://dns10.quad9.net/dns-query" configuration

Let me know if there's any other information you will require

Kind Regards
Andre

Problem/Motivation

Hassio 0.94.2
Intel NUC
After installing adguard addon(1.2.0) the integration field in Hassio is blank. You cannot add it to Hassio.

Expected behavior

Succesfull integration configuration and the availability of adguard sensors and switches in HA.

Actual behavior

Configuration of integration not possible and the following error:

2019-06-12 19:00:21 ERROR (MainThread) [homeassistant.config_entries] Cannot find integration adguard
2019-06-12 19:00:21 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 671, in _async_create_flow
self.hass, handler_key)
File "/usr/src/homeassistant/homeassistant/loader.py", line 211, in async_get_integration
raise IntegrationNotFound(domain)
homeassistant.loader.IntegrationNotFound: Component adguard not found.
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/discovery.py", line 89, in async_process_new
service, context={'source': 'hassio'}, data=config_data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 64, in async_init
handler, context=context, data=data)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 674, in _async_create_flow
raise data_entry_flow.UnknownHandler
homeassistant.data_entry_flow.UnknownHandler
2019-06-12 19:14:09 ERROR (MainThread) [homeassistant.config_entries] Cannot find integration adguard

Steps to reproduce

remove and re-install the addon

Proposed changes

I hope you can find out whats wrong

I noticed AdGuard sensors not appearing, this was a little while after upgrading to latest HA 0.96.5, checked and restarted addon and the addon appears to load fine but then [error] Failed to decode: unexpected EOF is spammed in the logs.

I've tried restarting the addon multiple times but facing the same issue. Trying to get to the web GUI returns 502: Bad Gateway.

[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.0.1
 You are running the latest version of this add-on.
 System: HassOS 2.12  (armv7 / raspberrypi3)
 Home Assistant version: 0.96.5
 Supervisor version: 170
-----------------------------------------------------------
 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... 
{"uuid":"798de0e7b0314a869df2e8429c7b13b4"}
[16:59:52] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] hosts.sh: executing... 
[cont-init.d] hosts.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.
[16:59:53] INFO: Starting AdGuard Home server...
2019/07/27 16:59:54 [info] AdGuard Home, version v0.97.1, channel release
2019/07/27 16:59:54 [info] Added 8 client aliases from /etc/hosts
2019/07/27 16:59:54 [info] Upstream 0: https://dns.cloudflare.com:443/dns-query
..
..
..

2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF
2019/07/27 13:12:17 [error] Failed to decode: unexpected EOF

NOTE: the gap in the logs; it's hard to capture as the EOF lines spam in high numbers.

Problem/Motivation

Static DHCP Leases not working and list deletes itself after every restart.

Expected behavior

To Assign the assigned IP created on the Static DHCP Pool and to retain the information after every restart.

Actual behavior

Static DHCP List deletes itself after every restart and before the restart, it doesn't work anyways.

Steps to reproduce

Assigning Static DHCP Leases,
When tested, not working, still gets a random IP
After restart, the Static DHCP list that was created will be blank.

Problem/Motivation

Cant install adguard from home assistant.

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

20-06-11 19:00:22 INFO (SyncWorker_18) [supervisor.docker.interface] Pull image hassioaddons/adguard-armv7 tag 2.4.1.
20-06-11 19:00:37 ERROR (SyncWorker_18) [supervisor.docker.interface] Can't install hassioaddons/adguard-armv7:2.4.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").

(What actually happened)

Steps to reproduce

When I click on install.

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Motivation: Make the ZeroTier addon use the Adguard addon

I've set both addons up and directed my iPhone to use the HomeAssistant server as a DNS address and default route.

However, adverts are not being blocked and nothing in the Adguard query logs justs the remote client is using Adguard to resolve addresses.

Is there a way to make the Adguard addon listen on the ZeroTier IP address?

Problem/Motivation

AdGuard container gets stuck in faulted state after running ~8 hours. Currently have to restart the container approx 1-2 times a day to get it working again.

Expected behavior

AdGuard runs w/o manual intervention

Actual behavior

After running for approx ~8 hours, the container faults and gets stuck into a loop.

Steps to reproduce

Install AdGuard Home Add-On using default Config/Network options and let run for a day

Proposed changes

Don't know

Log

2020/03/09 03:52:30 [info] AdGuard Home, version v0.100.9, channel release

2020/03/09 03:52:30 [info] Upstream 0: https://dns.quad9.net:443/dns-query
2020/03/09 03:52:30 [info] Go to http://127.0.0.1:45158
2020/03/09 03:52:30 [info] Starting the DNS proxy server
2020/03/09 03:52:30 [info] Ratelimit is enabled and set to 20 rps
2020/03/09 03:52:30 [info] The server is configured to refuse ANY requests
2020/03/09 03:52:30 [info] DNS cache is enabled
2020/03/09 03:52:30 [info] Creating the UDP server socket
2020/03/09 03:52:30 [info] Listening to udp://[::]:53
2020/03/09 03:52:30 [info] Creating the TCP server socket
2020/03/09 03:52:30 [info] Listening to tcp://[::]:53
2020/03/09 03:52:30 [info] Entering the tcp listener loop on [::]:53
2020/03/09 03:52:30 [info] Entering the UDP listener loop on [::]:53
2020/03/09 05:29:48 [info] Filter 2 has been updated: 442270 bytes, 15611 rules
2020/03/09 05:29:50 [info] Saving filter 2 contents to: /data/adguard/data/filters/2.txt
2020/03/09 05:29:50 [info] Updated filter #2. Rules: 15613 -> 15611
2020/03/09 13:00:11 [info] Stopping AdGuard Home
2020/03/09 13:00:11 [info] Stopping the DNS proxy server
2020/03/09 13:00:11 [info] tcpListen.Accept() returned because we're reading from a closed connection, exiting loop
2020/03/09 13:00:11 [info] udpListen.ReadFrom() returned because we're reading from a closed connection, exiting loop
2020/03/09 13:00:11 [info] Stopped the DNS proxy server
2020/03/09 13:00:11 [info] Stopped
2020/03/09 13:02:11 [info] AdGuard Home, version v0.100.9, channel release

2020/03/09 13:02:11 [error] Couldn't parse config file: yaml: unmarshal errors:
line 9: cannot unmarshal !!str `` into int
2020/03/09 13:02:12 [info] AdGuard Home, version v0.100.9, channel release

2020/03/09 13:02:12 [error] Couldn't parse config file: yaml: unmarshal errors:
line 9: cannot unmarshal !!str `` into int
2020/03/09 13:02:13 [info] AdGuard Home, version v0.100.9, channel release

2020/03/09 13:02:13 [error] Couldn't parse config file: yaml: unmarshal errors:
line 9: cannot unmarshal !!str `` into int
2020/03/09 13:02:14 [info] AdGuard Home, version v0.100.9, channel release

2020/03/09 13:02:14 [error] Couldn't parse config file: yaml: unmarshal errors:
line 9: cannot unmarshal !!str `` into int
2020/03/09 13:02:15 [info] AdGuard Home, version v0.100.9, channel release

....

The Below is after restarting the container

2020/03/11 18:47:59 [info] AdGuard Home, version v0.100.9, channel release

2020/03/11 18:47:59 [info] Upstream 0: https://dns.quad9.net:443/dns-query
2020/03/11 18:47:59 [info] Go to http://127.0.0.1:45158
2020/03/11 18:47:59 [info] Starting the DNS proxy server
2020/03/11 18:47:59 [info] Ratelimit is enabled and set to 20 rps
2020/03/11 18:47:59 [info] The server is configured to refuse ANY requests
2020/03/11 18:47:59 [info] DNS cache is enabled
2020/03/11 18:47:59 [info] Creating the UDP server socket
2020/03/11 18:47:59 [info] Listening to udp://[::]:53
2020/03/11 18:47:59 [info] Creating the TCP server socket
2020/03/11 18:47:59 [info] Listening to tcp://[::]:53
2020/03/11 18:47:59 [info] Entering the UDP listener loop on [::]:53
2020/03/11 18:47:59 [info] Entering the tcp listener loop on [::]:53
2020/03/11 18:47:59 [info] Filter 1 has been updated: 566963 bytes, 29677 rules
2020/03/11 18:48:01 [info] Saving filter 1 contents to: /data/adguard/data/filters/1.txt
2020/03/11 18:48:01 [info] Updated filter #1. Rules: 29647 -> 29677

Problem/Motivation

Clients
Configure devices connected to AdGuard Home.
It is not possible to add IPV6 Client IP to resolve connected clients into their clientname

(Why the issue was filed)

Expected behavior

See on the Dashboard for tile ->
Top clients
for the last 24 hours

(for example)
Notebook (fd00::0000:dddd:eeee:ffff)

validate IPV6 clientip in the setting, by adding clients to the list of clients

(What you expected to happen)

Actual behavior

IPV6 Client ip is not supported during the form validation

(What actually happened)

Steps to reproduce

go to:
Settings -> Client Settings -> add client
use ipv6 adress

-> Error by the formvalidation: Invalid IPv4 format

(How can someone else make/see it happen)

runnings version hassio 0.94.4
AdGuard 2.0.0

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Is it possible to add these switches to hass so I can use them in an automation.

Problem/Motivation

I previously used the PiHole add-on. With the recent deprecation of PiHole I've been trying to setup the AdGuard add-on, but this is without success. Whenever I switch PiHole off and AdGuard on, there is no internet connection on my network. I've set the pi up with a static ip using nmcli. This was already needed for PiHole to work.

When I start AdGuard my internet stops working.

Expected behavior

A working internet connection with ads being blocked

Actual behavior

No internet connection at all

Steps to reproduce

1. Turn off the PiHole add-on
2. Start AdGuard

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Found out on tweakers.net that there is an update available for Adguard home

Expected behavior

Behavior is good already.

Actual behavior

Official update was released

Steps to reproduce

Check the Adguard website or GitHub repo 😉https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.102.0

Proposed changes

Update the system

Additional questions

Is it possible to add extra environment settings for more configuration in Adguard Home?

GitHub

AdguardTeam/AdGuardHome

Network-wide ads & trackers blocking DNS server. Contribute to AdguardTeam/AdGuardHome development by creating an account on GitHub.

Problem/Motivation

It is impossible to run AdGuard on the same machine as home-assistant due to Hassio-dns using port 53.

Expected behavior

Hassio-dns being disabled for AdGuard to run.

Actual behavior

AdGuard can't boot due to used port 53
It seems to be difficult to disable Hassio-dns https://community.home-assistant.io/t/how-disable-hassio-dns-coredns/138465

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Home Assistant Community

How disable hassio_dns / coredns

Hi, I’ve recently updated hassio, noticing these problems: new addonds/container, called hassio_dns (I already have a dns server, pihole) this container contains a process, coredns, which spawn in different processes and eat all cpu *quad core) seems that now hassio is not good to connect to external api, like netatmo and ikea tradfri (maybe related to dns) How can I disable this hassio_dns, using instead previous approach? I’ve also tried to disable/uninstall container, without success (afte...

The add-on version 1.2.0 doesn't start anymore. See logs below.

[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: 1.2.0
 You are running the latest version of this add-on.
 System: Resin OS 2.3.0+rev1  (armv7 / raspberrypi3)
 Home Assistant version: 0.94.2
 Supervisor version: 166
-----------------------------------------------------------
 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... 
Log level is set to INFO
[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... 
{"uuid":"7483d39824224e9aab1ce9266a24762c"}
[23:23:21] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] hosts.sh: executing... 
[cont-init.d] hosts.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.
[23:23:21] INFO: Starting AdGuard Home server...
2019/06/16 23:23:22 [info] AdGuard Home, version v0.96-hotfix, channel release
2019/06/16 23:23:22 [info] Added 8 client aliases from /etc/hosts
2019/06/16 23:23:22 [info] Upstream 0: 192.168.1.99:55
2019/06/16 23:23:25 [info] Start DNS server periodic jobs
2019/06/16 23:23:25 [info] Starting the DNS proxy server
2019/06/16 23:23:25 [info] Ratelimit is enabled and set to 20 rps
2019/06/16 23:23:25 [info] The server is configured to refuse ANY requests
2019/06/16 23:23:25 [info] DNS cache is enabled
2019/06/16 23:23:25 [info] Creating the UDP server socket
2019/06/16 23:23:25 [info] Listening to udp://[::]:53
2019/06/16 23:23:25 [info] Creating the TCP server socket
2019/06/16 23:23:25 [info] Listening to tcp://[::]:53
2019/06/16 23:23:25 [info] Entering the UDP listener loop on [::]:53
2019/06/16 23:23:25 [info] Entering the tcp listener loop on [::]:53
2019/06/16 23:23:25 [info] Go to http://127.0.0.1:45158
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x2c pc=0x1d89a8]
goroutine 50 [running]:
crypto/tls.(*Conn).write(0x3e90000, 0x3eb6000, 0x125, 0x140, 0x3eb4000, 0x120, 0x180)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/crypto/tls/conn.go:896 +0xf4
crypto/tls.(*Conn).writeRecordLocked(0x3e90000, 0x6c9416, 0x3eb4000, 0x120, 0x180, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/crypto/tls/conn.go:945 +0x1fc
crypto/tls.(*Conn).writeRecord(0x3e90000, 0x3eb4016, 0x3eb4000, 0x120, 0x180, 0x0, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/crypto/tls/conn.go:967 +0x90
crypto/tls.(*Conn).clientHandshake(0x3e90000, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/crypto/tls/handshake_client.go:167 +0x114
crypto/tls.(*Conn).Handshake(0x3e90000, 0x0, 0x0)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/crypto/tls/conn.go:1343 +0xe8
net/http.(*persistConn).addTLS.func2(0x0, 0x3e90000, 0x0, 0x20fc140)
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/net/http/transport.go:1190 +0x34
created by net/http.(*persistConn).addTLS
	/home/travis/.gimme/versions/go1.12.5.linux.amd64/src/net/http/transport.go:1186 +0x174
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Problem/Motivation

I uninstalled the addon after adding it to my sidebar. The entry in my sidebar stayed but wasn't functional. I couldn't remove it by logging out / logging in.

Expected behavior

When the uninstall button was clicked I expected the addon to be removed from the sidebar as part of the uninstall process.

Actual behavior

The addon wasn't removed, and then could not be removed until the addon was reinstalled, the toggle changed for showing in the sidebar, then uninstalled again.

Steps to reproduce

Install addon, toggle the option to show in the sidebar, uninstall the addon. You can see in the attached screenshot that the sidebar entry is present, but the addon is not installed (icon is black, not green)

Problem/Motivation

The main reason I installed AdGuard (previously Pi-Hole which wasn't working smoothly) is for a DHCP server (my router fails to handle my 50+ devices when it comes to DHCP and renewing leases). I'd like to be able to see the list of active leases (or even better, list of connected clients with host names).

Expected behavior

A dedicated page that shows more DHCP information.

Actual behavior

The only thing possible is adding static leases. In Pi-Hole above the static list table, there's the actual lease table (and with a click of a button a regular lease could be added as a static lease).

Proposed changes

I've tried looking at leases.db, stats.db and sessions.db and didn't see that AdGuard is keeping track on DHCP leases except for the list of static IPs. It would be great if I could follow the DHCP process in my network somehow.

Problem/Motivation

switch.adguard_protection does not work as intended

Expected behavior

toggling the switch.adguard_protection from within lovelace should toggle the protection

Actual behavior

switching switch.adguard_protection in Lovelace off or on does not change the status of the add-on. Hence, the switch immediately goes back to its previous state reflecting the actual state of the add-on. In case I switch the add-on off/on from within its GUI the status of the switch.adguard_protection updated accordingly. It appears that the integration to HA lost its capability to switch the protection on/off but at the same time is still capable of reading the actual state of the add-on.

Steps to reproduce

just give it a try :-)

Proposed changes

don't know

Log

2020-02-04 07:32:25 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:33:21 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:33:24 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:35:53 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning on AdGuard Home switch.

Problem/Motivation

The static dhcp leases are currently not persisted in hassio snapshots.

Expected behavior

The leases.db file which is located in /opt/AdGuard/ should stored in /data/adguard/ so that is will be included in snapshots.

The name of the db files is currently hardcoded into AdGuard Home.
See: https://github.com/AdguardTeam/AdGuardHome/blob/9389b087be6300a1a301c2eeb2ef1024675e4d9f/dhcpd/db.go#L17

GitHub

AdguardTeam/AdGuardHome

Network-wide ads & trackers blocking DNS server. Contribute to AdguardTeam/AdGuardHome development by creating an account on GitHub.

is there a way to change the available ports to forward in the addon?
HTTPS 443 and 853 should be configurable.

I enabled dns over tls which causes the admin page to switch to the https port and actually has shut me out.

Problem/Motivation

I have a number of services running off my server, and I'd like to define DNS entries such as server.example.org:8123 as simply homeassistant.example.org.

Expected behavior

I would expect that defining this in the hosts section of the config would work.

Actual behavior

Will not allow me to save the config file.

Steps to reproduce

Add the following to the hosts section of the config:
{ "name": "Desktop", "ip": "192.168.1.5:8123" },

Proposed changes

Please support various ports in the hosts/ip section. Thank you.

Problem/Motivation

AdGuard does not start due to different if name: enp1s0 instead of eth0

Expected behavior

AdGuard add-on should start and serve requests via main Ethernet I/f.

Actual behavior

In Ubuntu 20.04 LTS, the interfaces naming is different and the Ethernet if is names enp1s0. It seems, AdGuard is having eth0 hardcoded and is looking for it.

Steps to reproduce

1. Deploy hass.io (Home Assistant as a docker) on Ubuntu LTS 20.04.
2. Start AdGuard and it will fail:

[16:14:47] INFO: Starting AdGuard Home server...
2020/05/03 16:14:47 [info] AdGuard Home, version v0.101.0, channel release
, arch linux amd64%!(EXTRA string=)
2020/05/03 16:14:47 [info] Available network interfaces: "lo", "enp1s0", "docker0", "hassio", "vethd58e6de", "vethd426a69", "veth6939fd9", "vethb718215", "vethfb1a84b", "veth5523162", "vethbbf54cd", "veth85b6671", "vethbff20fe", "veth1db6c63", "veth72bde02", "vethe2aec86", "vethd26aeb3", "vethf17be3b", "vethaf5c051", "vethd936c4e",
2020/05/03 16:14:47 [info] Couldn't find interface by name eth0, cause: route ip+net: no such network interface
2020/05/03 16:14:47 [error] DHCP: Couldn't find interface by name eth0, cause: route ip+net: no such network interface
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x975ccf]

Problem/Motivation

After installing the add on, and restarting Hass I lost connection toy ecobee and darksky components as well as no connection to nabucasa.

Expected behavior

Function without losing Hass functionality

Actual behavior

The above stopped working until I uninstalled the addon. I even tried turning all of the filtering off with no change.

Steps to reproduce

Install, restart, check components and homeassistant cloud connections.

Problem/Motivation

Cannot install addons or upgrade Hass.io while Adguard addon is running.
Stopped AdGuard addon and install/upgrade works as expected.
Re-tried install while Pi-hole addon was running and it worked as expected.

Expected behavior

Installation of other addons & upgrades of Hass.io work as normal.

Actual behavior

System logs from attempting to install the community MQTT & Web client addon:

19-01-13 16:46:53 INFO (MainThread) [hassio.addons.addon] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_mqtt
19-01-13 16:46:53 INFO (SyncWorker_28) [hassio.docker.interface] Pull image hassioaddons/mqtt tag 0.3.1.
19-01-13 16:47:03 ERROR (SyncWorker_28) [hassio.docker.interface] Can't install hassioaddons/mqtt:0.3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:35023->127.0.0.53:53: i/o timeout").

Steps to reproduce

Install, configure & start AdGuard Home addon.
Try to install any other addon while AdGuard Home is running.
Hopefully this is reproducible and not just a byproduct of my setup (Hass.io on Ubuntu Server 18.04).

Proposed changes

Not sure what the root of the issue is but I am happy to help in any way I can. Just let me know what is needed.

Good day!
Adguard plugin stopping to block anything from any lists. Even when I add "||google.com^" to custom filtering rules, it says "Not found in your filter lists" after check.
Only plugin reinstallation solves this problem for another 10-12 hours.
There are no warnings or errors in log files, and meanwhile plugin is serving DNS requests normally (including DNS rewrites).
In dashboard it looks like this:
https://clip2net.com/s/48mUuXx

Hassio ver. 0.112.3, plugin ver. 2.4.2.
Thanks!