AdGuardHome AGH not working on new firmware 3006

[decedion]

I'm trying to update from version 1.7.7 to 1.8.6 from amtm and it doesn't do anything. I select the ag option, it stays for a while "thinking" and returns to the amtm menu without doing anything.
And if I use the script directly:

$ 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 (60req./hr), and our token work around did not work (5000req./hr).
For more information, please read /tmp/174087_headers.out.
Please be sure to check your internet connection, and please try again later.
The installer script will now exit.

 

[bidh]

Hello, I was advised there were updates available for my router.

Available amtm script updates:
- amtm 6.1 -> 6.1.2
- MerlinAU 1.4.9 -> 1.5.0
- AdGuardHome 1.7.7 -> 1.8.6

Which I did but the AGH update failed with.
One or more critical variables could not be set in a timely manner./n
Please check your internet connection, or try again later.

I rebooted before trying the AGH update again but no success.

amtm 6.1.2 by thelonelycoder
RT-AX58UV2 (armv7l) Kernel-4.19.183
FW-3004.388.8_4-gnuton
Operation Mode: Wireless router

This command allowed AGH to be updated to 1.8.6

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

Info: Detected RT-AX58U router.
Info: Detected Linux platform.
Info: Detected ARMv7 architecture.
Info: JFFS custom scripts and configs are already enabled.
Info: DNS Environment is Ready.
Info: AI_VERSION=v1.8.6
Info: ADGUARDHOME_BUILD=Release
Info: ADGUARDHOME_VER=v0.107.63

 

[Milan]

This error I get when I am trying to update via curl:

One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit (60req./hr), and our token work around did not work (5000req./hr).
For more information, please read /tmp/113859_headers.out.
Please be sure to check your internet connection, and please try again later.
The installer script will now exit.

What is the reason?

Content of the /tmp/113859_headers.out file:

HTTP/1.1 403 rate limit exceeded
Date: Sun, 13 Jul 2025 10:18:18 GMT
Server: Varnish
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-RateLimit-Used, X-RateLimit-Resource, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset
Content-Type: application/json; charset=utf-8
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
X-GitHub-Media-Type: github.v3; format=json
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1752404400
X-RateLimit-Resource: core
X-RateLimit-Used: 60
Content-Length: 280
X-GitHub-Request-Id: 80B6:1E790D:7A7EF3A:7E70D0E:687387EA

 

[Viktor Jaep]

This error I get when I am trying to update via curl:


What is the reason?

Content of the /tmp/113859_headers.out file:

They are either a very popular site that is dishing out many downloads/requests, or they're getting hit with some kind of DoS attack is my guess. Best thing to do is give it a break, wait a few hours, and try again.

 

[bluzfanmr1]

Try again if you are able.

Hopefully my release of v1.8.6 should resolve these problems. The brave are welcome to try it out.

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

What's Changed Update installer by @jumpsmm7 in #237 Full Changelog: v1.8.3...v1.8.6

github.com

Same issue with the same error messages. No DNS until I disable the Guest Network Pro IoT network. Once I do that I can re-enable the IoT network and it works too.

 

[bluzfanmr1]

I also caught these error messages after trying to update amtm and AGH, though they may have been related to no DNS situation I have been posting about.

awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit (60req./hr), and our token work around did not work (5000req./hr).
For more information, please read /tmp/1577891_headers.out.
Please be sure to check your internet connection, and please try again later.
The installer script will now exit.

 

[SomeWhereOverTheRainBow]

I also caught these error messages after trying to update amtm and AGH, though they may have been related to no DNS situation I have been posting about.

awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
awk: /tmp/AGH_GIT_API_1577891.json: No such file or directory
One or more critical variables could not be set in a timely manner.
It is possible we have hit the github api ratelimit (60req./hr), and our token work around did not work (5000req./hr).
For more information, please read /tmp/1577891_headers.out.
Please be sure to check your internet connection, and please try again later.
The installer script will now exit.

What is the output of cat /tmp/1577891_headers.out

 

[Ripshod]

Same issue with the same error messages. No DNS until I disable the Guest Network Pro IoT network. Once I do that I can re-enable the IoT network and it works too.

I suggest deleting the IoT network then rebuilding it from a Customized Network.
I had nothing but problems with the default IoT network as GNP builds it.

 

[bluzfanmr1]

What is the output of /tmp/1577891_headers.out

That file wasn't there when I went to look at it. Sorry I meant to say that in my post. I may have nuked it with a reboot in the scramble to get everything up again.

 

[Milan]

Is still there the startup issue when used with syslog-ng and scribe?

 

[bluzfanmr1]

I suggest deleting the IoT network then rebuilding it from a Customized Network.
I had nothing but problems with the default IoT network as GNP builds it.

Ok thanks for the tip, I will give it a try.

 

[SomeWhereOverTheRainBow]

That file wasn't there when I went to look at it. Sorry I meant to say that in my post. I may have nuked it with a reboot in the scramble to get everything up again.

Most likely it was some kind of curl error or you would have seen how long left you had for rate limit. It also seems like you have been unsuccessful updating to the lastest version, ergo why you are still recieving the same results.

 

[SomeWhereOverTheRainBow]

Is still there the startup issue when used with syslog-ng and scribe?

i would have to assume yes. I think it is a bug with agh.

 

[bluzfanmr1]

Most likely it was some kind of curl error or you would have seen how long left you had for rate limit. It also seems like you have been unsuccessful updating to the lastest version, ergo why you are still recieving the same results.

To clarify, I had been able to update to v1.8.6 but the issue persists when rebooting. After reboot, I have to disable the Guest Network Pro IoT network to get AGH to work. After that I re-enable the GNP IoT network and everything works nicely together. @Ripshod suggest deleting the ASUS provided IoT setup and use custom instead, which I will try.

 

[SomeWhereOverTheRainBow]

To clarify, I had been able to update to v1.8.6 but the issue persists when rebooting. After reboot, I have to disable the Guest Network Pro IoT network to get AGH to work. After that I re-enable the GNP IoT network and everything works nicely together. @Ripshod suggest deleting the ASUS provided IoT setup and use custom instead, which I will try.

Let me ask, do you have dns director turned on? If so, try disabling it.

 

[bluzfanmr1]

Let me ask, do you have dns director turned on? If so, try disabling it.

I do have it on so I disabled it, rebooted, and same result. I also tried the suggestion of @Ripshod and deleted the IoT, then created a custom network and that didn't work either.

 

[Ripshod]

that didn't work either

Worth a try.

 

[dave14305]

There’s a lot of energy being spent on wanting to have the latest AGH binary, but there is always a reasonably current version sitting in Entware.

 

[SomeWhereOverTheRainBow]

There’s a lot of energy being spent on wanting to have the latest AGH binary, but there is always a reasonably current version sitting in Entware.

preach it! Then they would be spending alot of time trying to figure out how to get that running with their setup! I love it.

 

[bluzfanmr1]

I'm pretty techie, but don't understand the difference in what I'm running compared to Entware. If there's something I could do different just let me know,