AdGuardHome AGH not working on new firmware 3006

[SomeWhereOverTheRainBow]

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,

So, aside from sharing your guest network ssid and password, maybe share your setting selections. Other users who are able can then try to replicate the behavior you are observing, or maybe someone here has some kind of helpful feed back. So far here is what we know:
1. You are running the latest version of the script.
2. You have to restart your guestnetworks after reboot in order to get everything working.

 

[bluzfanmr1]

So, aside from sharing your guest network ssid and password, maybe share your setting selections. Other users who are able can then try to replicate the behavior you are observing, or maybe someone here has some kind of helpful feed back. So far here is what we know:
1. You are running the latest version of the script.
2. You have to restart your guestnetworks after reboot in order to get everything working.

Below are the steps I was taking when it was failing. That being said, it's working now and there are no issues. Must've been something wonky in my setup. I had deleted and created a new network several times but this time I gave it a new name. I had been calling it IoTNet but this time chose something different and it all works. I wonder if the name of "IoTNet" caused a conflict somewhere.

Go to Guest Network Pro tab and select IoT Network
Enter new SSID (Was calling it IoTNet) and password
Move slider to off for Use same subnet as main network
Choose 2.4 band under more config and hit apply
Wait 10 secs or so for new network to come back live
Connect device(s) to new IoT network
Reboot
After reboot no DNS unless I disable and re-enable IoT network

 

[ComputerSteve]

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

 

[dave14305]

For more information, please read /tmp/166153_headers.out.

It tells you what to do.

 

[bluzfanmr1]

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

Like @dave14305 said, try and see what is in that tmp file. I got the same thing once but rebooted before I realized I should read it and it got nuked. The 2nd time I was able to capture it, but it was just a blank file.

 

[saison2023]

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.

I indeed saw it was really slow to do anything (stop, start disable,....), sound like something like that.
Thanks for replying and education.

 

[SomeWhereOverTheRainBow]

It tells you what to do.

Thanks for giving that suggestion, it certainly helps narrow down the problem.

 

[SomeWhereOverTheRainBow]

Like @dave14305 said, try and see what is in that tmp file. I got the same thing once but rebooted before I realized I should read it and it got nuked. The 2nd time I was able to capture it, but it was just a blank file.

When you have free time, i did one more update. I believe I have it straight now. Without you testing things, I have barely to little no feedback. So I thank you for your continuous support.

 

[SomeWhereOverTheRainBow]

Hey @SomeWhereOverTheRainBow , have I stuffed up something?

I've run an update (I think) from AMTM 1.7.6 using "ag" and then "Option 1 - Install/Update", but now slightly confused about what version I'm on?
AMTM still shows 1.7.6 with no updates available, but within the "ag" installer it shows 1.7.7 in the header and 1.7.6 within the lower text.


View attachment 66495View attachment 66496



Can you please clarify?
Do I need to do a re-install from the cli or something?
What command would I run?

Cheers,

StephenH

P.S. Just in case it's relevant, I was actually doing this update on my "old" RT-AX86U running 388.9_2, not the RT-BE86U as per my sig - I was holding off the final cutover to the BE86U for a couple of reasons, this imminent AdGuardHome update being amongst them!

P.P.S I've "fixed" my signature for now so it's less confusing!

What happens if you run updates now?

 

[Louis-NL]

cat /tmp/128022_headers.out

HTTP/1.1 403 rate limit exceeded
Date: Mon, 14 Jul 2025 12:21:39 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: 1752495967
X-RateLimit-Resource: core
X-RateLimit-Used: 60
Content-Length: 278
X-GitHub-Request-Id: AFE0:B093879835EF2324:6874F653

 

[SomeWhereOverTheRainBow]

cat /tmp/128022_headers.out

HTTP/1.1 403 rate limit exceeded
Date: Mon, 14 Jul 2025 12:21:39 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: 1752495967
X-RateLimit-Resource: core
X-RateLimit-Used: 60
Content-Length: 278
X-GitHub-Request-Id: AFE0:B093879835EF2324:6874F653

I wonder how many people are doing this behind a vpn source or have an IP address they share with many people(eg. CGNAT) . Its apparent with this one somehow you are (or rather your public facing ip address) is hitting github API ratelimit. What do you get with grep 'api.gitub' /jffs/curl*

 

[bluzfanmr1]

When you have free time, i did one more update. I believe I have it straight now. Without you testing things, I have barely to little no feedback. So I thank you for your continuous support.

Happy to help as I didn't want to be a pain in the rear.

Here's the behavior I'm seeing. No issues updating via amtm as long as I have no Guest Network Pro networks configured OR if I do have one configured, it's disabled. If I have a Guest Network Pro network enabled and I reboot, there is no DNS after and AGH fails to start with what I believe is the relevant line in the log below:

Jul 14 08:34:35 AdGuardHome[19714]: 2025/07/14 08:34:35.272111 [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

Let me know if you want me to try anything else.

 

[Louis-NL]

I wonder how many people are doing this behind a vpn source or have an IP address they share with many people(eg. CGNAT) . Its apparent with this one somehow you are (or rather your public facing ip address) is hitting github API ratelimit. What do you get with grep 'api.gitub' /jffs/curl*

grep 'api.gitub' /jffs/curl*
?

added an H

grep 'api.github' /jffs/curl*

results in this:

grep 'api.github' /jffs/curl*
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases

deleted in this response 12 times this, because my answer exceeds a limit here :
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases


/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.11)curl --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases
/jffs/curllst.1128022)curl -D /tmp/128022_headers.out --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=5 -o /tmp/AGH_GIT_API_128022.json
/jffs/curllst.1128022)curl -D /tmp/128022_headers.out --retry 3 --connect-timeout 3 --retry-delay 1 --max-time 15 --retry-connrefused -sL https://api.github.com/repos/AdguardTeam/AdGuardHome/releases?per_page=5 -o /tmp/AGH_GIT_API_128022.json -H "Authorization: token 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"

 

[SomeWhereOverTheRainBow]

Happy to help as I didn't want to be a pain in the rear.

Here's the behavior I'm seeing. No issues updating via amtm as long as I have no Guest Network Pro networks configured OR if I do have one configured, it's disabled. If I have a Guest Network Pro network enabled and I reboot, there is no DNS after and AGH fails to start with what I believe is the relevant line in the log below:

Jul 14 08:34:35 AdGuardHome[19714]: 2025/07/14 08:34:35.272111 [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

Let me know if you want me to try anything else.

Is it still happening with this most recent update I did? Currently there is a version 1.8.7 out.

 

[SomeWhereOverTheRainBow]

grep 'api.gitub' /jffs/curl*
?

added an H

grep 'api.github' /jffs/curl*

results in this:

grep 'api.github' /jffs/curl*

Is it still happening when you try to update now using the commandline command.
curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer

 

[Tomo]

as far as it goes, even on the old non 3006 platform i'm having problems updating from my 1.7.6 version, this is the error "One or more critical variables could not be set in a timely manner./n Please check your internet connection, or try again later./nThe installer script will now.exit./n"

Amtm updated to the latest version.

 

[SomeWhereOverTheRainBow]

as far as it goes, even on the old non 3006 platform i'm having problems updating from my 1.7.6 version, this is the error "One or more critical variables could not be set in a timely manner./n Please check your internet connection, or try again later./nThe installer script will now.exit./n"

Amtm updated to the latest version.

try running this command straight into the SSH command line, your AMTM "ag" is still using an outdated installer that lacks important fixes.

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

 

[bluzfanmr1]

Is it still happening with this most recent update I did? Currently there is a version 1.8.7 out.

Dang it sorry I wasn't more specific. Yes I had updated to 1.8.7 and it was still doing it. I see 1.8.8 is out and I'm going to update to that now.

 

[bluzfanmr1]

After updating to 1.8.8 there was DNS and AGH was working. However, now the Guest Network isn't working and devices cannot connect. I'm getting this in the logs now, which is the guest network:

Jul 14 15:21:17 rc_service: watchdog 2924:notify_rc start_dnsmasq 1
Jul 14 15:21:17 custom_script: Running /jffs/scripts/service-event (args: start dnsmasq)
Jul 14 15:21:17 custom_script: Running /jffs/scripts/dnsmasq-sdn.postconf (args: /etc/dnsmasq-1.conf 1)
Jul 14 15:21:17 dnsmasq[353253]: failed to create listening socket for 192.168.52.1: Address already in use
Jul 14 15:21:17 dnsmasq[353253]: FAILED to start up
Jul 14 15:21:17 custom_script: Running /jffs/scripts/service-event-end (args: start dnsmasq)

 

[dave14305]

@SomeWhereOverTheRainBow I don’t think you can rely on webs_state_info to always contain the current firmware version. To detect SDN support, check the rc_support nvram variable for mtlancfg string.