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

[juched]

Thank you. You changed the same part I was playing with. But you did it right. Installs now and doesn’t crash. Now to configure. Thank you.

 

[SomeWhereOverTheRainBow]

Thank you. You changed the same part I was playing with. But you did it right. Installs now and doesn’t crash. Now to configure. Thank you.

I just pushed a new version as well.
Changelog can be viewed here.

* pushed a patch. minor typo.

 

[unknownz]

Thanks for the quick fix.

Are the changes effective on the "installer" through AMTM? Getting the following when doing the install through AMTM

[edit] Ignore, issue resolved after getting AMTM to do an overall update. Script version reflects as 1.06 after AMTM refresh the update

 

[SomeWhereOverTheRainBow]

Thanks for the quick fix.

Are the changes effective on the "installer" through AMTM? Getting the following when doing the install through AMTM

[edit] Ignore, issue resolved after getting AMTM to do an overall update. Script version reflects as 1.06 after AMTM refresh the update

View attachment 38816

Yea I have noticed sometimes there seems to be some type of bugginess between delays with github, and needing to refresh amtm. That is why some times I may request debugging such as trying to install with the link provided in the main post. All-in-all amtm should work, but sometimes uu has to be ran too.

 

[SomeWhereOverTheRainBow]

Thank you. You changed the same part I was playing with. But you did it right. Installs now and doesn’t crash. Now to configure. Thank you.

Unfortunately, I have found a medium level bug in AdGuard Homes which is open on their github, that may change the way the installer behaves in the comming v0.108.0 release of adguardhome.

--check-config breaks boostrap dns · Issue #4067 · AdguardTeam/AdGuardHome

Using the Lastest Stable Release when --check-config is run for the first time on a fresh meaning "new" .yaml file bootstrap resolver that are listed in - 8.8.8.8 - 9.9.9.9 format gets changed to -...

github.com

Hopefully the changes benefits what I can do with the installer, instead of hurting what I am able to do now.

I appreciate all the feedback given when an issue is found. Thank you all for giving AdGuardHome a try.

 

[Spydawg]

Does this need a paid sub for this to work? I already have a license just wondering if I need to add it in the install process or put in the config somewhere ?

 

[SomeWhereOverTheRainBow]

Does this need a paid sub for this to work? I already have a license just wondering if I need to add it in the install process or put in the config somewhere ?

No, the installer does ask you to create a user name and password though. That is only used for logging into the webui admin page for adguardhome.

 

[MorlinArt]

AdGuardHome stops running after some time and I have to manually restart it with

/opt/etc/init.d/S61AdGuardHome start

, this happens once a day / every day. After restart it works for may be 8-10 hrs and then stops again.

May be I missed something in the settings? Why is this happening?

Router: RT-AC68U
Merlin firmware: 386.4

AdGuardHome installed via amtm Adguard installer, I did a clean re-install several times after this started happening to no avail.

 

[juched]

AdGuardHome stops running after some time and I have to manually restart it with

/opt/etc/init.d/S61AdGuardHome start

, this happens once a day / every day. After restart it works for may be 8-10 hrs and then stops again.

May be I missed something in the settings? Why is this happening?

Router: RT-AC68U
Merlin firmware: 386.4

AdGuardHome installed via amtm Adguard installer, I did a clean re-install several times after this started happening to no avail.

Yes, it has crashed (or shutdown) on me quite a few times.... Thinking we need to decide upon the best plant to auto-restart. But my experience with init.d setup is limited... so didn't have time to learn more yet.

 

[SomeWhereOverTheRainBow]

AdGuardHome stops running after some time and I have to manually restart it with

/opt/etc/init.d/S61AdGuardHome start

, this happens once a day / every day. After restart it works for may be 8-10 hrs and then stops again.

May be I missed something in the settings? Why is this happening?

Router: RT-AC68U
Merlin firmware: 386.4

AdGuardHome installed via amtm Adguard installer, I did a clean re-install several times after this started happening to no avail.

I am not sure. You are the first people to report having such a problem. Is there anything going on internally with your router around that time. Think cron-tab, system logs, anything?

 

[SomeWhereOverTheRainBow]

Yes, it has crashed (or shutdown) on me quite a few times.... Thinking we need to decide upon the best plant to auto-restart. But my experience with init.d setup is limited... so didn't have time to learn more yet.

Ya I have ran it for several days straight with no problems. I am not quite sure. have you investigated your system logs for any funny lines. Also, do you have any cron-jobs running around the time it happens? I am trying to eliminate the router pulverizing the server to get resources.

 

[SomeWhereOverTheRainBow]

Yes, it has crashed (or shutdown) on me quite a few times.... Thinking we need to decide upon the best plant to auto-restart. But my experience with init.d setup is limited... so didn't have time to learn more yet.

I can add something but keep in mind it will be a bandaid solution, but first I need to know is it specific time it happens? Are there alot of cronjobs running? What does the system logs look like around the time it happens?

 

[MorlinArt]

I am not sure. You are the first people to report having such a problem. Is there anything going on internally with your router around that time. Think cron-tab, system logs, anything?

I've skimmed through the system log, all I could find was these, not sure if it's relevant:

Jan 17 19:58:19 AdGuardHome[4294]: 2022/01/17 19:58:19.097632 [info] Received signal "hangup"

Jan 21 15:17:09 Timemachine: daemon is stopped
Jan 21 15:17:09 WEBDAV_Server: daemon is stopped
Jan 21 15:17:10 custom_script: Running /jffs/scripts/services-stop
Jan 21 15:17:10 ntpd: Stopped ntpd
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.632005 [info] Received signal "terminated"
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.650726 [info] stopping AdGuard Home
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.663409 [info] stopping http server...
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.673898 [info] stopped http server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.698104 [info] Stopping the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.731950 [info] Stopped the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.927197 [info] Stopped
Jan 21 15:17:11 WEBDAV_Server: daemon is stopped
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:11 syslog: Got SIGTERM
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:12 Mastiff: Select error


Jan 22 09:59:54 AdGuardHome[27823]: 2022/01/22 09:59:54.270302 [info] error handling UDP packet: dns: buffer size too small
Jan 22 14:02:55 syslog: wlceventd_proc_event(491): eth2: Deauth_ind E2:5D:03:E3:58:3D, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 22 10:03:15 AdGuardHome[27823]: 2022/01/22 10:03:15.783480 [info] error handling UDP packet: dns: buffer size too small


The reason I was able to catch AdGuard crashing the first couple of times is because my Internet stopped working, after I restarted AdGuard everything went back to normal. So now I have AdGuardHome dashboard always open in one tab and I periodically check. Last two times however, upon checking the dashboard I came to know that AdGuard was down, while my Internet was working fine, so it could have been down for hours before I checked.

 

[SomeWhereOverTheRainBow]

I've skimmed through the system log, all I could find was these, not sure if it's relevant:

Jan 17 19:58:19 AdGuardHome[4294]: 2022/01/17 19:58:19.097632 [info] Received signal "hangup"

Jan 21 15:17:09 Timemachine: daemon is stopped
Jan 21 15:17:09 WEBDAV_Server: daemon is stopped
Jan 21 15:17:10 custom_script: Running /jffs/scripts/services-stop
Jan 21 15:17:10 ntpd: Stopped ntpd
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.632005 [info] Received signal "terminated"
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.650726 [info] stopping AdGuard Home
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.663409 [info] stopping http server...
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.673898 [info] stopped http server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.698104 [info] Stopping the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.731950 [info] Stopped the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.927197 [info] Stopped
Jan 21 15:17:11 WEBDAV_Server: daemon is stopped
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:11 syslog: Got SIGTERM
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:12 Mastiff: Select error


Jan 22 09:59:54 AdGuardHome[27823]: 2022/01/22 09:59:54.270302 [info] error handling UDP packet: dns: buffer size too small
Jan 22 14:02:55 syslog: wlceventd_proc_event(491): eth2: Deauth_ind E2:5D:03:E3:58:3D, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 22 10:03:15 AdGuardHome[27823]: 2022/01/22 10:03:15.783480 [info] error handling UDP packet: dns: buffer size too small


The reason I was able to catch AdGuard crashing the first couple of times is because my Internet stopped working, after I restarted AdGuard everything went back to normal. So now I have AdGuardHome dashboard always open in one tab and I periodically check. Last two times however, upon checking the dashboard I came to know that AdGuard was down, while my Internet was working fine, so it could have been down for hours before I checked.

The real question is did adguardhome stop working because the internet crashed? Or did adguardhome cause the internet to crash. Either of which seems to have coincide with adguardhome not running. The one thing I notice is a number of things failing and not just adguardhome once the "hang up" log appears, which kind of reminds me of the internet failing.

At either rate, I am working on a small modification that should resolve the issue.

 

[hong88]

i am getting the following errors. please help

Info: New ADGUARDHOME_VER=v0.107.2 Available!
Info: Updating ADGUARDHOME_VER=v0.108.0-b.2 to v0.107.2 .
Info: Downloading AdGuardHome_linux_arm64.tar.gz
./AdGuardHome/
./AdGuardHome/AdGuardHome
./AdGuardHome/LICENSE.txt
./AdGuardHome/AdGuardHome.sig
./AdGuardHome/README.md
./AdGuardHome/CHANGELOG.md
ln: /opt/sbin/AdGuardHome: No such file or directory
*** Error: Failed to download AdGuardHome package for your router
=====================================================

 

[SomeWhereOverTheRainBow]

i am getting the following errors. please help

Info: New ADGUARDHOME_VER=v0.107.2 Available!
Info: Updating ADGUARDHOME_VER=v0.108.0-b.2 to v0.107.2 .
Info: Downloading AdGuardHome_linux_arm64.tar.gz
./AdGuardHome/
./AdGuardHome/AdGuardHome
./AdGuardHome/LICENSE.txt
./AdGuardHome/AdGuardHome.sig
./AdGuardHome/README.md
./AdGuardHome/CHANGELOG.md
ln: /opt/sbin/AdGuardHome: No such file or directory
*** Error: Failed to download AdGuardHome package for your router
=====================================================

What is your router model and firmware version? Also what value do you get when you run

ls /opt/sbin

In the command line?

Edit***

From the looks of it, it appears your router failed to download a viable adguardhome binary, and the installer caught that.

 

[SomeWhereOverTheRainBow]

Yes, it has crashed (or shutdown) on me quite a few times.... Thinking we need to decide upon the best plant to auto-restart. But my experience with init.d setup is limited... so didn't have time to learn more yet.

I've skimmed through the system log, all I could find was these, not sure if it's relevant:

Jan 17 19:58:19 AdGuardHome[4294]: 2022/01/17 19:58:19.097632 [info] Received signal "hangup"

Jan 21 15:17:09 Timemachine: daemon is stopped
Jan 21 15:17:09 WEBDAV_Server: daemon is stopped
Jan 21 15:17:10 custom_script: Running /jffs/scripts/services-stop
Jan 21 15:17:10 ntpd: Stopped ntpd
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.632005 [info] Received signal "terminated"
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.650726 [info] stopping AdGuard Home
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.663409 [info] stopping http server...
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.673898 [info] stopped http server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.698104 [info] Stopping the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.731950 [info] Stopped the DNS proxy server
Jan 21 11:17:10 AdGuardHome[19404]: 2022/01/21 11:17:10.927197 [info] Stopped
Jan 21 15:17:11 WEBDAV_Server: daemon is stopped
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:11 syslog: Got SIGTERM
Jan 21 15:17:11 Mastiff: Got SIGTERM
Jan 21 15:17:12 Mastiff: Select error


Jan 22 09:59:54 AdGuardHome[27823]: 2022/01/22 09:59:54.270302 [info] error handling UDP packet: dns: buffer size too small
Jan 22 14:02:55 syslog: wlceventd_proc_event(491): eth2: Deauth_ind E2:5D:03:E3:58:3D, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 22 10:03:15 AdGuardHome[27823]: 2022/01/22 10:03:15.783480 [info] error handling UDP packet: dns: buffer size too small


The reason I was able to catch AdGuard crashing the first couple of times is because my Internet stopped working, after I restarted AdGuard everything went back to normal. So now I have AdGuardHome dashboard always open in one tab and I periodically check. Last two times however, upon checking the dashboard I came to know that AdGuard was down, while my Internet was working fine, so it could have been down for hours before I checked.

Release v1.0.7
changes can be seen here

Release v1.0.7 · jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer

Add checks to make sure we stay active for at least 6 hours. Add checks to make sure we are running Asuswrt-Merlin. What's Changed Dev by @jumpsmm7 in #16 v1.0.7 by @jumpsmm7 in #17 Fix branch by...

github.com

Changelog:

• Add checks to make sure we stay active for at least 6 hours.
• Add checks to make sure we are running Asuswrt-Merlin.

The time on the checks is subject to change based on if you guys feel it is needed, but I first want to see if it remains stable with the checks in place.

 

[TCoreX]

Hello, very nice work. Only I have the problem that I get despite valid certificate, only simple DNS resolution. Furthermore, if I specify the server address I specified in the encryption as DNS, when clienting, the Internet no longer works on the client. What am I doing wrong? Do I need to open ports? Thank you

 

[SomeWhereOverTheRainBow]

Hello, very nice work. Only I have the problem that I get despite valid certificate, only simple DNS resolution. Furthermore, if I specify the server address I specified in the encryption as DNS, when clienting, the Internet no longer works on the client. What am I doing wrong? Do I need to open ports? Thank you

You need to be more specific of what you have done so far. Provide screenshots if possible,but redact anything you consider personal. The only thing this installer does is set adguardhome up as a local dns server. If you are trying to use extra features like running AdGuardHome as remote server for DoH, DoT, DoQ, or Dnscrypt, then you are at the mercy of -your own devices, others who have done this help, and what you can google as this would require you to open additional ports using firewall-start. Also, if you are having basic configuration issues make sure you read the wiki link of adguardhome.

Home

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

github.com

 

[MorlinArt]

Release v1.0.7
changes can be seen here

Release v1.0.7 · jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer

Add checks to make sure we stay active for at least 6 hours. Add checks to make sure we are running Asuswrt-Merlin. What's Changed Dev by @jumpsmm7 in #16 v1.0.7 by @jumpsmm7 in #17 Fix branch by...

github.com

Changelog:

• Add checks to make sure we stay active for at least 6 hours.
• Add checks to make sure we are running Asuswrt-Merlin.

The time on the checks is subject to change based on if you guys feel it is needed, but I first want to see if it remains stable with the checks in place.

Thank you for your work.
Updated to 1.0.7, so far so good. I'll keep monitoring and report whether the issue is rectified.