Adguard Home does not work

Hello I hope you can help me I am trying to install Adguard Home for the first time but when I give it to start I get this error in the registry.

[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... 
-----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 4.1.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.13  (amd64 / qemux86-64)
 Home Assistant Core: 2021.5.4
 Home Assistant Supervisor: 2021.04.3
-----------------------------------------------------------
 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... 
/var/run/s6/etc/cont-init.d/adguard.sh: line 27: null: unbound variable
[cont-init.d] adguard.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[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.

Me to, but further symptoms. Adguard was installed and previously working. But DNS was “dropping out” and after checking the adguard logs, I could see it was continually restarting after an error about not being able to bind to a udp port? Uninstalled and re-installed. Not I get the same error.

Cheers.
PDJ

Hello, after doing what you told me it’s still the same :frowning:

Also have this problem
Was working before the latest update.

Could it be that just the day I want to install the addon itself fails?

Yes. Looks like the addon is broken. We need to wait for the smart one to find and fix the error.

1 Like

Hi. It seems Franck Nijhof already fixed it in the repo. We just have to wait until it’s published to Hassio :slight_smile:

see Ensure compared variable is bound by frenck · Pull Request #180 · hassio-addons/addon-adguard-home · GitHub

It seems to be working but now it’s something I think I did wrong, I get this error.

[13:01:02] INFO: Starting AdGuard Home server...
2021/05/20 13:01:03.166063 [info] AdGuard Home, version v0.106.3
2021/05/20 13:01:03.166585 [info] home.upgradeSchema0to1(): called
2021/05/20 13:01:03.166624 [info] deleting /data/adguard/dnsfilter.txt as we don't need it anymore
2021/05/20 13:01:03.166682 [info] home.upgradeSchema1to2(): called
2021/05/20 13:01:03.166722 [info] deleting /data/adguard/Corefile as we don't need it anymore
2021/05/20 13:01:03.166762 [info] home.upgradeSchema2to3(): called
2021/05/20 13:01:03.166789 [info] home.upgradeSchema3to4(): called
2021/05/20 13:01:03.166810 [info] home.upgradeSchema4to5(): called
2021/05/20 13:01:03.166890 [info] home.upgradeSchema5to6(): called
2021/05/20 13:01:03.166919 [info] Upgrade yaml: 6 to 7
2021/05/20 13:01:03.166933 [info] Upgrade yaml: 7 to 8
2021/05/20 13:01:03.166958 [fatal] unexpected type of dns.bind_host: <nil>

After upgrading to 4.1.4 it’s working again for me, I did need to reboot host before I could install 4.1.4 however.

It’s the first time I install it so I’m not sure if it’s because I didn’t do something right with this:

unexpected type of dns.bind_host:

In the end I did it through docker and it didn’t give me any problems.

Version 4.1.6 now available for install and the issues seem to be fixed.