What's new

AdGuardHome [RELEASE] Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hi,

I'm trying to setup AdGuardHome on my RT-AC68U (merlin firmware 386.4) using the installation script (v1.2.0) provided by amtm (v. 3.2.3 FW).
As default DNS (set in the WAN configuration page of the router) I use 8.8.8.8 and 4.4.4.4. The DNS settings in the LAN configuration page are left blank.

AdGuardHome is working as intended for all the client that uses the DNS address provided by the router (IP 192.168.100.1).

The problem is when a client has manual configured DNS (like cloudflare 1.1.1.1). In fact the router (or AdGuardHome) doesn't seem to enforce the use of the router as DNS server (192.168.100.1) and let the client use his DNS (1.1.1.1)

I tried to solve using iptables with the following rules:
Code:
### DNS ###

# Block FORWARD for DNS #
iptables -I FORWARD -p tcp --dport 53 -j DROP
iptables -I FORWARD -p udp --dport 53 -j DROP

# Allow DNS only if destination is the router #
iptables -I INPUT -p tcp --dport 53 -d 192.168.100.1 -j ACCEPT
iptables -I INPUT -p udp --dport 53 -d 192.168.100.1 -j ACCEPT


# Redirect all DNS query to the router #
iptables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -i br0 -j REDIRECT
iptables -t nat -I PREROUTING -p udp -m udp --dport 53 -i br0 -j REDIRECT


### DNSoverTLS (DoT) ###

# Block FORWARD for DoT
iptables -I FORWARD -p tcp --dport 853 -j DROP
iptables -I FORWARD -p udp --dport 853 -j DROP

to make some trials I added to host file this line 0.0.0.0 www.google.com:
now in the client with the manual configurated DNS (1.1.1.1) if I use nslookup www.google.com the machine correctly redirect the query to the router DNS (192.168.100.1) and give me 0.0.0.0 as answer:
Code:
Server:    1.1.1.1
Address:    1.1.1.1#53
Non-authoritative answer:
Name:    www.google.com
Address: 0.0.0.0

If I open Safari to browse www.google.com corectly I receive "error no connection" and if I browse some site known to be full of ADs , AdGuardHome does his job and there are no ads. Site like ipleak dot net says my DNS are google ones.

If I open Chrome instead I can browse www.google.com and AdGuardHome filtering isn't working (sites full of ADs). ipleak dot net says my DNS are cloudflare ones, followed by google DNS.

This is my Asus DNS filter configuration on the router. (I disabled the Asus DNS filter implementation to use instead only iptables rules)
Code:
dnsfilter_custom1=
dnsfilter_custom2=
dnsfilter_custom3=
dnsfilter_rulelist1=
dnsfilter_rulelist2=
dnsfilter_rulelist3=
dnsfilter_rulelist4=
dnsfilter_rulelist5=
dnsfilter_mode=11
dnsfilter_enable_x=0

Am I missing somenting in my iptables configuration?
Or this problem could be related to Chrome bypassing my DNS Enforcement configuration using DNSoverTLS or DNSoverHTTPS. In this case how can I enforce clients using Chrome to use AdGuardHome?
I really don't understand where is the problem and need some help. Thanks for your time

Here is my AdGuardHome configuration:
upstream DNS server (where home.arpa is my RT-AC68U's Domain Name):
Code:
[/router.asus.com/]192.168.150.1:553
[/www.asusnetwork.net/]192.168.150.1:553
[/www.asusrouter.com/]192.168.150.1:553
[/use-application-dns.net/]192.168.150.1:553
[/dns.resolver.arpa/]192.168.150.1:553
[/home.arpa/]192.168.150.1:553
[//]192.168.150.1:553
8.8.8.8
8.8.4.4
tcp://8.8.8.8
tcp://8.8.4.4
private reverse DNS server:
Code:
[/10.in-addr.arpa/]192.168.150.1:553
[/168.192.in-addr.arpa/]192.168.150.1:553
[/0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/][]:553

edit: added AdGuardHome configuration
 
Last edited:
I think I found why DNS enforcing rules are not working. Chrome is using DoH or DoT:
Screenshot 2022-02-09 at 16.54.31.png


how can I prevent the use of DoT or DoH on my LAN to enforce the use of AdGuardHome DNS? Thanks
 
I think I found why DNS enforcing rules are not working. Chrome is using DoH or DoT:
View attachment 39359

how can I prevent the use of DoT or DoH on my LAN to enforce the use of AdGuardHome DNS? Thanks
add a DoT, DoH domain to your blocklist.

for example, blocking a list of commonly used DoT,DoH servers will effectively prevent outbound 443, and 853 dns traffic from said devices, but still allow adguardhome.


devices cannot connect to what they cannot resolve. fortunately these browsers don't implement IP addresses in their connecting methods.
 
Hi,

I'm trying to setup AdGuardHome on my RT-AC68U (merlin firmware 386.4) using the installation script (v1.2.0) provided by amtm (v. 3.2.3 FW).
As default DNS (set in the WAN configuration page of the router) I use 8.8.8.8 and 4.4.4.4. The DNS settings in the LAN configuration page are left blank.

AdGuardHome is working as intended for all the client that uses the DNS address provided by the router (IP 192.168.100.1).

The problem is when a client has manual configured DNS (like cloudflare 1.1.1.1). In fact the router (or AdGuardHome) doesn't seem to enforce the use of the router as DNS server (192.168.100.1) and let the client use his DNS (1.1.1.1)

I tried to solve using iptables with the following rules:

# Redirect all DNS query to the router #
iptables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -i br0 -j REDIRECT
iptables -t nat -I PREROUTING -p udp -m udp --dport 53 -i br0 -j REDIRECT

should be
Code:
iptables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -i br0 -j DNAT --to-destination 192.168.100.1
iptables -t nat -I PREROUTING -p udp -m udp --dport 53 -i br0 -j DNAT --to-destination 192.168.100.1
 
add a DoT, DoH domain to your blocklist.
Thanks, this solved the issue.
Despite DoH and DoT are blocked by the blocklist and Chrome is set to use the "secure DNS" however the browser automatically fall back to normal DNS resolution (in this case to 192.168.100.1:53 running AdGuardHome) and doens't loose internet connectivity.

should be
Code:
iptables -t nat -I PREROUTING -p tcp -m tcp --dport 53 -i br0 -j DNAT --to-destination 192.168.100.1
iptables -t nat -I PREROUTING -p udp -m udp --dport 53 -i br0 -j DNAT --to-destination 192.168.100.1
I also deleted my rules with "REDIRECT" to use these one.

Last thing: I'm in a double NAT enviroment (RT-AC68U WAN --> MY ISP DUMB ROUTER --> VDSL) and had some trouble resolving some address (like twitter dot com, or reddit dot com, or any link from google search to the searched term) and I solved using "tls://dns dot google" instead of 8.8.8.8 as upstreamingDNS in AdGuardHome.
I don't know why.. probably my ISP Router was trying to route my DNS search to his DNS server.
 
Long over due,
Release v1.3.0

Whats changed:
  • changed the way the script is start/stop/restart (rc.func.AdGuardHome)
  • Added an intermediary script handler of AdGuardHome (AdGuardHome.sh), (@Jack Yaz solution until AdGuardHome devs can resolve their system call issue.)
  • simplified S99AdGuardHome (it will no longer use internet checks and none of that crazy stuff before it is told to start.)

Thanks go out to:
@Jack Yaz for providing the most valuable ideas and collaborative work. Thank you Jack

As always, here is the changelog:
 
Last edited:
Long over due,
Release v1.3.0

Whats changed:
  • changed the way the script is start/stop/restart (rc.func.AdGuardHome)
  • Added an intermediary script handler of AdGuardHome (AdGuardHome.sh), (@Jack Yaz solution until AdGuardHome devs can resolve their system call issue.)
  • simplified S99AdGuardHome (it will no longer use internet checks and none of that crazy stuff before it is told to start.)

Thanks go out to:
@Jack Yaz for providing the most valuable ideas and collaborative work. Thank you Jack

As always, here is the changelog:
After updating to v1.3.0, AGH seems to be going into some infinite restart loop.

This is even after a "kill" and "start" was initiated

[EDIT 1] Tried to do a re-install by running the AGH installer through AMTM but the installer quits with an error saying unable to detect Internet
Code:
Feb 13 16:31:02 RT-AC86U-7510 admin: Started AdGuardHome from S99AdGuardHome[15012].
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337517 [info] Initializing auth module: /tmp/mnt/mntASUS/entware/etc/AdGuardHome/data/sessions.db
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337863 [info] auth: initialized.  users:1  sessions:10
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337932 [info] Initialize web module
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.141538 [info] AdGuard Home is available at the following addresses:
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.172173 [info] Go to http://127.0.0.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.172852 [info] Go to http://127.0.1.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173001 [info] Go to http://[::1]:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173133 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173282 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173412 [info] Go to http://192.168.1.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173558 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173688 [info] Go to http://10.8.0.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173825 [info] Go to http://[fd00:ac68:1::1]:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173971 [info] Go to http://10.8.0.18:31107
Feb 13 16:31:12 RT-AC86U-7510 S99AdGuardHome[15012]: Warning: AdGuardHome is not responding; S99AdGuardHome[15012] will re-start it!
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394081 [info] Received signal "terminated"
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394177 [info] stopping AdGuard Home
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394196 [info] stopping http server...
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.407195 [info] stopped http server
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.407983 [info] Stopped
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.509346 [info] AdGuard Home, version v0.107.3
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.509846 [info] AdGuard Home is running as a service
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611107 [info] Initializing auth module: /tmp/mnt/mntASUS/entware/etc/AdGuardHome/data/sessions.db
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611513 [info] auth: initialized.  users:1  sessions:10
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611600 [info] Initialize web module
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.148427 [info] AdGuard Home is available at the following addresses:
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161697 [info] Go to http://127.0.0.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161793 [info] Go to http://127.0.1.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161817 [info] Go to http://[::1]:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161855 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161876 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161896 [info] Go to http://192.168.1.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161932 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161952 [info] Go to http://10.8.0.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.162024 [info] Go to http://[fd00:ac68:1::1]:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.162045 [info] Go to http://10.8.0.18:31107
Feb 13 16:31:14 RT-AC86U-7510 admin: Started AdGuardHome from S99AdGuardHome[15012].
 
Last edited:
After updating to v1.3.0, AGH seems to be going into some infinite restart loop.

This is even after a "kill" and "start" was initiated

[EDIT 1] Tried to do a re-install by running the AGH installer through AMTM but the installer quits with an error saying unable to detect Internet
Code:
Feb 13 16:31:02 RT-AC86U-7510 admin: Started AdGuardHome from S99AdGuardHome[15012].
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337517 [info] Initializing auth module: /tmp/mnt/mntASUS/entware/etc/AdGuardHome/data/sessions.db
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337863 [info] auth: initialized.  users:1  sessions:10
Feb 13 16:31:02 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:02.337932 [info] Initialize web module
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.141538 [info] AdGuard Home is available at the following addresses:
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.172173 [info] Go to http://127.0.0.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.172852 [info] Go to http://127.0.1.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173001 [info] Go to http://[::1]:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173133 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173282 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173412 [info] Go to http://192.168.1.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173558 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173688 [info] Go to http://10.8.0.1:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173825 [info] Go to http://[fd00:ac68:1::1]:31107
Feb 13 16:31:03 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:03.173971 [info] Go to http://10.8.0.18:31107
Feb 13 16:31:12 RT-AC86U-7510 S99AdGuardHome[15012]: Warning: AdGuardHome is not responding; S99AdGuardHome[15012] will re-start it!
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394081 [info] Received signal "terminated"
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394177 [info] stopping AdGuard Home
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.394196 [info] stopping http server...
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.407195 [info] stopped http server
Feb 13 16:31:12 RT-AC86U-7510 AdGuardHome[16954]: 2022/02/13 16:31:12.407983 [info] Stopped
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.509346 [info] AdGuard Home, version v0.107.3
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.509846 [info] AdGuard Home is running as a service
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611107 [info] Initializing auth module: /tmp/mnt/mntASUS/entware/etc/AdGuardHome/data/sessions.db
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611513 [info] auth: initialized.  users:1  sessions:10
Feb 13 16:31:13 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:13.611600 [info] Initialize web module
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.148427 [info] AdGuard Home is available at the following addresses:
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161697 [info] Go to http://127.0.0.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161793 [info] Go to http://127.0.1.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161817 [info] Go to http://[::1]:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161855 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161876 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161896 [info] Go to http://192.168.1.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161932 [info] Go to http://<WAN IP>:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.161952 [info] Go to http://10.8.0.1:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.162024 [info] Go to http://[fd00:ac68:1::1]:31107
Feb 13 16:31:14 RT-AC86U-7510 AdGuardHome[18259]: 2022/02/13 16:31:14.162045 [info] Go to http://10.8.0.18:31107
Feb 13 16:31:14 RT-AC86U-7510 admin: Started AdGuardHome from S99AdGuardHome[15012].
Odd how are you killing it?

The proper way is either

/opt/etc/init.d/S99AdGuardHome stop

Or

/opt/etc/init.d/S99AdGuardHome kill

If you are killing it any other way, then it will be resurrected.
 
You won't see a version change because it is to the .sh file run option 1
As mentioned in the earlier comment, if I were to re-run the installer and try to select option 1, the installer will throw an error saying "unable to detect the internet" and then just exits the install

For clarity, internet connection is always active and AGH was killed first before attempt to run the installer.

It seems when the installer is initiated, AGH daemon was attempted to be started and then it gets stuck in the "infinite" restarts again
 
Last edited:
As mentioned in the earlier comment, if I were to re-run the installer and try to select option 1, the installer will throw an error saying "unable to detect the internet" and then just exits the install

Okay

run

sh /opt/etc/AdGuardHome/installer update


On the command line.

Which will skip that check and update the file you need to update.
 
Okay

run

sh /opt/etc/AdGuardHome/installer update


On the command line.

Which will skip that check and update the file you need to update.
Still gives me the same error

Code:
Info:  Detected RT-AC86U router.
 Info:  Detected Linux platform.
 Info:  Detected ARMv8 architecture.
 Info:  JFFS custom scripts and configs are already enabled.
 Info:  DNS Environment is Ready.
 *** Error:  AdGuardHome is dead or internet is not responding, skipping version check.
 Info:  Choose what you want to do:
  1) Install/Update AdGuardHome
  2) Uninstall
  b) Backup
  q) Quit
 =>  Please enter the number that designates your selection:, [1-2/b/q]:
 
Still gives me the same error

Code:
Info:  Detected RT-AC86U router.
 Info:  Detected Linux platform.
 Info:  Detected ARMv8 architecture.
 Info:  JFFS custom scripts and configs are already enabled.
 Info:  DNS Environment is Ready.
 *** Error:  AdGuardHome is dead or internet is not responding, skipping version check.
 Info:  Choose what you want to do:
  1) Install/Update AdGuardHome
  2) Uninstall
  b) Backup
  q) Quit
 =>  Please enter the number that designates your selection:, [1-2/b/q]:
That just means adguardhome wasn't fully up and running at the time of the update check. I will have to come up with something else for that. Maybe like skipping the update check after running updates or installing. Despite the artificial error, your adguardhome should be up and running.
 
That just means adguardhome wasn't fully up and running at the time of the update check. I will have to come up with something else for that. Maybe like skipping the update check after running updates or installing. Despite the artificial error, your adguardhome should be up and running.
Since option 1 is to do a fresh install or update an existing install, why would/should there be any attempt(s) in starting the AGH daemon. That was what I observed when running the installer and tailing the logs

The "infinite" restarts is still happening and I had to kill the whole AGH daemon
 
Last edited:
Since option 1 is to do a fresh install or update an existing install, why would/should there be any attempt(s) in starting the AGH daemon. That was what I observed when running the installer and tailing the logs
Because you are changing the binary, and the process. Earlier attempts showed that adguardhome installer would stall on the last check once adguardhome binary was replaced causing the installer to hang and never finish at the end. The solution was to stop AGH before replacing the binary.
 
Since option 1 is to do a fresh install or update an existing install, why would/should there be any attempt(s) in starting the AGH daemon. That was what I observed when running the installer and tailing the logs

The "infinite" restarts is still happening and I had to kill the whole AGH daemon
In all my attempts I am unable to replicate the infinite restarts. Aguardhome only restarts if either the process is killed or somehow you have changed the way it listens on addresses. Can you share your .yaml file redaction private details such as login and password?
 
In all my attempts I am unable to replicate the infinite restarts. Aguardhome only restarts if either the process is killed or somehow you have changed the way it listens on addresses. Can you share your .yaml file redaction private details such as login and password?
As requested. The only change to the yaml file is the web portal bind port

From the earlier shared info, this is the line that is causing all the restarts
Code:
Feb 13 16:31:12 RT-AC86U-7510 S99AdGuardHome[15012]: Warning: AdGuardHome is not responding; S99AdGuardHome[15012] will re-start it!
 

Attachments

  • AdGuardHome_share.txt
    3.4 KB · Views: 89

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top