AdGuardHome AGH not working on new firmware 3006

[darkony]

Now worked, ran the command that was provided to update, and now I am at 1.8.2

curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer

 

[jsbeddow]

I have finally moved over to the 3006.102.5 beta branch, and can report that the current version of AGH does work there: well, nominally at least. I can install it and it works perfectly until I reboot the router. I have tried a complete uninstall of AGH and re-install (without using previous options or backup) and same result: it works until I reboot the router.

I did capture the post-boot syslog events file, and would be happy to PM that to @SomeWhereOverTheRainBow if that might be helpful, let me know.

​

 

[SomeWhereOverTheRainBow]

I have finally moved over to the 3006.102.5 beta branch, and can report that the current version of AGH does work there: well, nominally at least. I can install it and it works perfectly until I reboot the router. I have tried a complete uninstall of AGH and re-install (without using previous options or backup) and same result: it works until I reboot the router.

I did capture the post-boot syslog events file, and would be happy to PM that to @SomeWhereOverTheRainBow if that might be helpful, let me know.

​

Sure you are welcome to share your findings in PM with me. Also, if you are running scribe, it uses syslog-ng. On newer AX routers there may still be a bug present with either AGH itself, or with syslog-ng. Basically, adguardhome would fail to start on reboot because it would fail to detect the presence of a syslog once syslogng had already started. The work around was to switch adguardhome from using syslog for its log facility to just using a basic log file.

 

[jsbeddow]

Sure you are welcome to share your findings in PM with me. Also, if you are running scribe, it uses syslog-ng. On newer AX routers there may still be a bug present with either AGH itself, or with syslog-ng. Basically, adguardhome would fail to start on reboot because it would fail to detect the presence of a syslog once syslogng had already started. The work around was to switch adguardhome from using syslog for its log facility to just using a basic log file.

PM sent, with a link to my syslog file on Pastebin. I don't use scribe, so it's unlikely to be related to syslog-ng (unless Eric has made that the default). I also proposed some possible reasons for the problem for you to review (could there be a problem using DNS Director set to Router, as under those circumstances multiple processes try to bind to port 53?).

 

[SomeWhereOverTheRainBow]

@SomeWhereOverTheRainBow my upgrade failed, output as below, sorry trying to do it on an iPad remotely but hope info helps...

admin@AsusRouter:/tmp/home/root# curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer
One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit, or your internet maybe down.
Please check your internet connection, or try again in an hour.
The installer script will now exit.

admin@AsusRouter:/tmp/home/root# grep -A1 curl.*api\.github\.com /jffs/curllst*
/jffs/curllst:(2944)/usr/sbin/curl -fsNL --connect-timeout 10 --retry 3 --max-time 12 https://api.github.com/repos/AdguardTeam/AdGuardHome/releases/latest
/jffs/curllst-(2943)/bin/sh /usr/sbin/amtm
--
/jffs/curllst:(6049)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=3 -o /tmp/AGH_GIT_API_6049.json
/jffs/curllst-(4176113)/bin/sh /opt/etc/AdGuardHome/installer
--
/jffs/curllst:(38067)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=3 -o /tmp/AGH_GIT_API_38067.json
/jffs/curllst-(4175322)sh installer
--
/jffs/curllst:(41082)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=3 -o /tmp/AGH_GIT_API_41082.json
/jffs/curllst-(4175322)sh installer
--
/jffs/curllst:(44538)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=3 -o /tmp/AGH_GIT_API_44538.json
/jffs/curllst-(4175322)sh installer
--
/jffs/curllst.1:(4177871)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=3 -o /tmp/AGH_GIT_API_4177871.json
/jffs/curllst.1-(4176113)/bin/sh /opt/etc/AdGuardHome/installer master
admin@AsusRouter:/tmp/home/root#

hopefully this issue should be resolved with this latest release of v1.8.3. Give it a test and tell me what you think. I'd install using the command line command still though.
curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer

 

[Apul]

Force updated Amtm, also updated the AG script to 1.8.2 (and automatically beta to .72). Same error is displayed in Amtm regarding the beta update status.

Not a big issue, AG itself is working fine, that's the most important.

Thanks for your hard work and the support!

I have no errors in Amtm.

 

[Stephen Harrington]

hopefully this issue should be resolved with this latest release of v1.8.3. Give it a test and tell me what you think. I'd install using the command line command still though.

@SomeWhereOverTheRainBow

Just reporting that I saw the following error pop up briefly (retrieved it from my SSH client buffer) when I did command-line update to 1.8.3 from 1.8.2:

ler/master/installer && sh installer
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
bad decrypt
4144603152:error:06065064:lib(6):func(101):reason(100):NA:0:
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
bad decrypt
4150452240:error:06065064:lib(6):func(101):reason(100):NA:0:

Assume it's some kind of curl error?

Update appeared to occur and AGH seems to be running OK.

 

[bluzfanmr1]

I logged in today and amtm showed an update to 1.8.3 available for AdGuardHome. This update ran fine via amtm and I am now on version 1.8.3 without any issues.

 

[SomeWhereOverTheRainBow]

@SomeWhereOverTheRainBow

Just reporting that I saw the following error pop up briefly (retrieved it from my SSH client buffer) when I did command-line update to 1.8.3 from 1.8.2:

ler/master/installer && sh installer
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
bad decrypt
4144603152:error:06065064:lib(6):func(101):reason(100):NA:0:
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
bad decrypt
4150452240:error:06065064:lib(6):func(101):reason(100):NA:0:

Assume it's some kind of curl error?

Update appeared to occur and AGH seems to be running OK.

I fixed this issue.

 

[worf105]

Hi all,

I am on 3004.388.9_2 running on a RT-AX86U.

AMTM shows me AdGuardHome 1.7.7 -> 1.8.4 (Same all the way through 1.8.1 - 1.8.4) I get all the same errors as mentioned before.

All i have installed is MerlinAU, Backupmon, scMerlin. My AGH branch is Edge.

AGH works OK but any help would be great to update the latest please.

 

[saison2023]

I upgraded AGH to 1.8.4 using command line without any issue (on the upgrade side).
Just after the upgrade, I can't tell why and what happen exactly, but my router became slow, Skynet wasn't running fine. I tried to restart services (like DNS/DHCP using scMerlin) but at the end I had to reboot the router. After the reboot and few minutes, everything went back to normal. Not sure this is related to the upgrade, but I thought it could not be worst to share, maybe useful for someone.

 

[SomeWhereOverTheRainBow]

Hi all,

I am on 3004.388.9_2 running on a RT-AX86U.

AMTM shows me AdGuardHome 1.7.7 -> 1.8.4 (Same all the way through 1.8.1 - 1.8.4) I get all the same errors as mentioned before.

All i have installed is MerlinAU, Backupmon, scMerlin. My AGH branch is Edge.

AGH works OK but any help would be great to update the latest please.

I'd install using the command line command instead of relying on AMTM atleast until AMTM has had time to correct the mod file for AdGuardHome. I have already submitted a pull request. Hopefully @thelonelycoder is receptive to it. Once @thelonelycoder accepts my pull request, you should just be able to use "uu" inside the AMTM menu.. it is only a small modification that will permanently resolve all issues.
curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer

 

[SomeWhereOverTheRainBow]

I upgraded AGH to 1.8.4 using command line without any issue (on the upgrade side).
Just after the upgrade, I can't tell why and what happen exactly, but my router became slow, Skynet wasn't running fine. I tried to restart services (like DNS/DHCP using scMerlin) but at the end I had to reboot the router. After the reboot and few minutes, everything went back to normal. Not sure this is related to the upgrade, but I thought it could not be worst to share, maybe useful for someone.

Yea it is possible it is symptom of upgrading during a time when the worst possible was possible in regards to the connection. Once the router hits that state, it can be hard to recover. It could be possible that Adguardhome itself had a delay on starting up its dns service even though the process itself was already running. I have seen instances where that has happen to me personally. But only on a small handful of times. If it becomes an ongoing problem with adguardhome, it maybe important to collect as much information as you can (e.g. logs, and debug). When that happens, we can share the information with the adguardhome developers.

 

[charlie2alpha]

One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit, or your internet maybe down.
Please check your internet connection, or try again in an hour.
The installer script will now exit.

I'd install using the command line command instead of relying on AMTM atleast until AMTM has had time to correct the mod file for AdGuardHome. I have already submitted a pull request. Hopefully @thelonelycoder is receptive to it. Once @thelonelycoder accepts my pull request, you should just be able to use "uu" inside the AMTM menu.. it is only a small modification that will permanently resolve all issues.
curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer

This doesn't work for me, the manual install command gives this error:
One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit, or your internet maybe down.
Please check your internet connection, or try again in an hour.
The installer script will now exit
My router is an GT-AXE11000 running on 3004.388.9_2 firmware.

 

[ComputerSteve]

I'm also getting this same error :
One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit, or your internet maybe down.
Please check your internet connection, or try again in an hour.
The installer script will now exit.

 

[thelonelycoder]

I'd install using the command line command instead of relying on AMTM atleast until AMTM has had time to correct the mod file for AdGuardHome. I have already submitted a pull request. Hopefully @thelonelycoder is receptive to it. Once @thelonelycoder accepts my pull request, you should just be able to use "uu" inside the AMTM menu.. it is only a small modification that will permanently resolve all issues.

I heard you and accepted your request.
amtm 6.1.2 is now available.

 

[bluzfanmr1]

We had a storm and sudden power outage of 3 minutes last night. Had no DNS after several reboots. On a hunch I disabled the new IoT Guest Network I had recently created after seeing messages in the log. This worked and DNS came back. I re-enabled the IoT Guest Network and that was fine too. I have not rebooted again yet to see if the same thing happens again but I will soon. Here is what continuously repeats in the log when there is an issue:

Jul 12 00:42:02 AdGuardHome[35195]: 2025/07/12 00:42:02.466373 [info] starting plain server server=plain addr=0.0.0.0:3000
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709202 [info] dnsproxy: starting dns proxy server
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709466 [info] dnsproxy: creating udp server socket addr=0.0.0.0:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709697 [info] dnsproxy: listening to udp addr=[::]:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709747 [info] dnsproxy: creating tcp server socket addr=0.0.0.0:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709893 [info] dnsproxy: warning: binding attempt=1 err="listen tcp 0.0.0.0:53: bind: address already in use"
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.712030 [error] closing query log: flushing log buffer: nothing to write to a file
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.712087 [fatal] starting dns server: configuring listeners: listening on tcp addr 0.0.0.0:53: listening to tcp socket: listen tcp 0.0.0.0:53: bind: address already in use
Jul 12 00:42:22 S99AdGuardHome[7405]: Warning: AdGuardHome is dead; Monitor will start it!
Jul 12 00:42:22 S99AdGuardHome[7405]: Started AdGuardHome from S99AdGuardHome[7405].

 

[SomeWhereOverTheRainBow]

We had a storm and sudden power outage of 3 minutes last night. Had no DNS after several reboots. On a hunch I disabled the new IoT Guest Network I had recently created after seeing messages in the log. This worked and DNS came back. I re-enabled the IoT Guest Network and that was fine too. I have not rebooted again yet to see if the same thing happens again but I will soon. Here is what continuously repeats in the log when there is an issue:

Jul 12 00:42:02 AdGuardHome[35195]: 2025/07/12 00:42:02.466373 [info] starting plain server server=plain addr=0.0.0.0:3000
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709202 [info] dnsproxy: starting dns proxy server
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709466 [info] dnsproxy: creating udp server socket addr=0.0.0.0:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709697 [info] dnsproxy: listening to udp addr=[::]:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709747 [info] dnsproxy: creating tcp server socket addr=0.0.0.0:53
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.709893 [info] dnsproxy: warning: binding attempt=1 err="listen tcp 0.0.0.0:53: bind: address already in use"
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.712030 [error] closing query log: flushing log buffer: nothing to write to a file
Jul 12 00:42:16 AdGuardHome[35195]: 2025/07/12 00:42:16.712087 [fatal] starting dns server: configuring listeners: listening on tcp addr 0.0.0.0:53: listening to tcp socket: listen tcp 0.0.0.0:53: bind: address already in use
Jul 12 00:42:22 S99AdGuardHome[7405]: Warning: AdGuardHome is dead; Monitor will start it!
Jul 12 00:42:22 S99AdGuardHome[7405]: Started AdGuardHome from S99AdGuardHome[7405].

Hopefully my release of v1.8.5 should resolve this problem. You are welcome to test it if you like.