AdGuardHome AGH not working on new firmware 3006

[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!

You are good or should be good. Small hiccup on my part. But all your files should be up to date. Run your update again.

 

[Stephen Harrington]

You are good or should be good. Small hiccup on my part. But all your files should be up to date. Run your update again.

Thanks @SomeWhereOverTheRainBow, all good now after re-running update!

 

[SomeWhereOverTheRainBow]

Thanks @SomeWhereOverTheRainBow, all good now after re-running update!

still running smoothly?

 

[Stephen Harrington]

still running smoothly?

Seems to be - albeit on a my AX86U running 388.9_2.

The cutover to my BE86U and testing there on 3006.102.x will have to wait until I have the house (and internet) to myself, which may not happen for a few weeks now as it turns out. Hopefully others can give you feedback on AGH and 3006 series firmware long before then!

 

[SomeWhereOverTheRainBow]

Seems to be - albeit on a my AX86U running 388.9_2.

The cutover to my BE86U and testing there on 3006.102.x will have to wait until I have the house (and internet) to myself, which may not happen for a few weeks now as it turns out. Hopefully others can give you feedback on AGH and 3006 series firmware long before then!

Please do, and have no fear. I believe I have sufficiently accounted for 3006 and the requirements for SDN networks. When you do "test", please share your guest network settings aside from any SSID and Passwords. I suspect you will be able to redact that information. If you wish to do it in private message, I am fine with that as well. My hope is, with your testing that I accounted for everything; However, I also understand there is a possibility I may have missed something. You may be able to detect if I did, so I appreciate yours', or any one else's, feedback.

 

[jsbeddow]

Yes, I suspect that many of us are waiting in the wings, hoping to benefit from the experiences of the brave souls testing these frontiers. In other words, those who don't have to worry about the WAF, aka the household CFO.

 

[Strud]

I have issue installing the new version, getting the below message when entering ag in amtm:
"One or more critical variables could not be set in a timely manner./nPlease check your internet connection, or try again later./nThe installer script will now exit./n"
Then I'm thrown back in Amtm, can's see the AdGuard script menu at all. No idea what has changed, 1 or 2 weeks ago it was still working fine, when I was updating the beta to the latest one. No changes is my setup since that time, except the update of Amtm.

Currently I have the 1.7.6 version installed, running v0.108.0-b.71 beta. Amtm is updated to 6.1.1.

I'm on firmware FW-3006.102.4.

 

[SomeWhereOverTheRainBow]

I have issue installing the new version, getting the below message when entering ag in amtm:
"One or more critical variables could not be set in a timely manner./nPlease check your internet connection, or try again later./nThe installer script will now exit./n"
Then I'm thrown back in Amtm, can's see the AdGuard script menu at all. No idea what has changed, 1 or 2 weeks ago it was still working fine, when I was updating the beta to the latest one. No changes is my setup since that time, except the update of Amtm.

Currently I have the 1.7.6 version installed, running v0.108.0-b.71 beta. Amtm is updated to 6.1.1.

I'm on firmware FW-3006.102.4.

Have you tried rebooting the router before attempting the upgrade?

 

[SomeWhereOverTheRainBow]

I have issue installing the new version, getting the below message when entering ag in amtm:
"One or more critical variables could not be set in a timely manner./nPlease check your internet connection, or try again later./nThe installer script will now exit./n"
Then I'm thrown back in Amtm, can's see the AdGuard script menu at all. No idea what has changed, 1 or 2 weeks ago it was still working fine, when I was updating the beta to the latest one. No changes is my setup since that time, except the update of Amtm.

Currently I have the 1.7.6 version installed, running v0.108.0-b.71 beta. Amtm is updated to 6.1.1.

I'm on firmware FW-3006.102.4.

Issue is kinda fixed now. You were hitting githubs ap ratelimit. I have adjusted the script to significantly reduce this issue, but I cannot control whether other people in your area have the same public IP address as you. Or if you have an incling desire to run the installer as manytimes as you want until it breaks.

I have just released v1.8.1 here is the changelog: https://github.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/compare/v1.7.7...v1.8.1

 

[bluzfanmr1]

I've been using Adguard Home as well and have avoided upgrading to 3006 after reading about the issues, though I'm tempted to go back to Diversion and might just go ahead and upgrade.

Just wanted to follow up and say thanks for the necessary fix. I upgraded to 3006.xxx and everything works great.

 

[Stephen Harrington]

@SomeWhereOverTheRainBow I just tried to update 1.7.7. to 1.8.1 by doing an "ag" from the AMTM menu and AGH menu never appears, and after long delay I get same message as @Strud above about "One or more critical variables could not be set in timely manner..."

Can you advise next steps to remedy or manual install workaround please?

Cheers,

StephenH

 

[SomeWhereOverTheRainBow]

@SomeWhereOverTheRainBow I just tried to update 1.7.7. to 1.8.1 by doing an "ag" from the AMTM menu and AGH menu never appears, and after long delay I get same message as @Strud above about "One or more critical variables could not be set in timely manner..."

Can you advise next steps to remedy or manual install workaround please?

Cheers,

StephenH

It is because when you use the ag command in amtm. You may technically still be using the old installer. You are going to have to use the commandline command curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer to download a fresh installer. Hopefully that should resolve the issue. I recommend everyone trying to upgrade their AGH to use this as their upgrade method temporarily because I had to upgrade some critical components of the installer.

@Stephen Harrington , Hopefully doing it this way works for you. Otherwise, please indicate if it doesn't. I will the take a deep dive look at other options once I am off work.

 

[Stephen Harrington]

@SomeWhereOverTheRainBow yes thank you that worked I think?

AGH and AMTM menu now showing versions as below, slight anomaly is the "Info: New RELEASE ADGUARDHOME_VER=v0.108.0-b.71 Available!" message" as I've not previously elected to get Beta versions and wasn't offered the option to change builds on this update run (??).

 

[SomeWhereOverTheRainBow]

@SomeWhereOverTheRainBow yes thank you that worked I think?

AGH and AMTM menu now showing versions as below, slight anomaly is the "Info: New RELEASE ADGUARDHOME_VER=v0.108.0-b.71 Available!" message" as I've not previously elected to get Beta versions and wasn't offered the option to change builds on this update run (??).


View attachment 66564
View attachment 66565

Yea it looks like you have accidently switched off of the beta to the main maybe?

 

[jsbeddow]

Hmm...I haven't been tinkering/testing the rapid updates (of late yesterday or today), until just now when I ran the above suggested command line: as with Stephen Harrington, it seemed to update the installer successfully to 1.8.1, but also indicated that the release version was "ADGUARDHOME_VER=v0.108.0-b.71", when I also was definitely NOT previously running the beta versions. I quit out from the installer script as I wasn't planning to do a full update/re-install of AdGuardHome.

At this point though, amtm indicates that the installed version is still 1.7.7 and suggests that 1.8.1 is available, but when I run "ag" it hangs for a long period and eventually times out, returning to the amtm prompt. If I re-run the command line to update the installer, it also hangs for a while then I eventually get the previously mentioned "Github ratelimit/internet may be down" message. Am I also stuck waiting for a cool-down period here?

 

[SomeWhereOverTheRainBow]

Hmm...I haven't been tinkering/testing the rapid updates (of late yesterday or today), until just now when I ran the above suggested command line: as with Stephen Harrington, it seemed to update the installer successfully to 1.8.1, but also indicated that the release version was "ADGUARDHOME_VER=v0.108.0-b.71", when I also was definitely NOT previously running the beta versions. I quit out from the installer script as I wasn't planning to do a full update/re-install of AdGuardHome.

At this point though, amtm indicates that the installed version is still 1.7.7 and suggests that 1.8.1 is available, but when I run "ag" it hangs for a long period and eventually times out, returning to the amtm prompt. If I re-run the command line to update the installer, it also hangs for a while then I eventually get the previously mentioned "Github ratelimit/internet may be down" message. Am I also stuck waiting for a cool-down period here?

Yea so github api ratelimits at 60/hr unless people generate access tokens, which only increases the rate limit to 5000. So if you have ran the installer several times in a given hour period, it does have a cooldown period.

 

[jsbeddow]

Yea so github api ratelimits at 60/hr unless people generate access tokens, which only increases the rate limit to 5000. So if you have ran the installer several times in a given hour period, it does have a cooldown period.

Yeah, not sure how I would have hit even 60/hr (unless that is across your entire repository for all users, not just my requests). Regardless, any idea what happened here? Ie: why did my update from 1.7.7 to 1.8.1 seem to complete, but now even attempting to run "ag" from amtm fails?

 

[Stephen Harrington]

Yea it looks like you have accidently switched off of the beta to the main maybe?

@SomeWhereOverTheRainBow

Ok, so I'm confused now, I don't remember being on the Beta ... and certainly didn't switch anything in the last few days.
Looks like I got an identical outcome to what @jsbeddow is reporting?

 

[SomeWhereOverTheRainBow]

@SomeWhereOverTheRainBow

Ok, so I'm confused now, I don't remember being on the Beta ... and certainly didn't switch anything in the last few days.
Looks like I got an identical outcome to what @jsbeddow is reporting?

I will have to take a look once i am out of work. Most likely ag in AMTM is still using a dated installer. Can you confirm using the install command above causes that issue as well?

 

[Stephen Harrington]

Can you confirm using the install command above causes that issue as well?

Yes, I ran your manual command line install and that is what resulted.

I just ran it again to capture data with same result.

I never get the option to "Change Builds" anymore but I think it never actually installs the Beta anyway - just always says it is available ... or maybe i'm mis-reading that?

#################################################################################################################
# █████╗ ███████╗██╗   ██╗███████╗██╗    ██╗██████╗ ████████╗   ███╗   ███╗███████╗██████╗ ██╗     ██╗███╗   ██╗#
#██╔══██╗██╔════╝██║   ██║██╔════╝██║    ██║██╔══██╗╚══██╔══╝   ████╗ ████║██╔════╝██╔══██╗██║     ██║████╗  ██║#
#███████║███████╗██║   ██║███████╗██║ █╗ ██║██████╔╝   ██║█████╗██╔████╔██║█████╗  ██████╔╝██║     ██║██╔██╗ ██║#
#██╔══██║╚════██║██║   ██║╚════██║██║███╗██║██╔══██╗   ██║╚════╝██║╚██╔╝██║██╔══╝  ██╔══██╗██║     ██║██║╚██╗██║#
#██║  ██║███████║╚██████╔╝███████║╚███╔███╔╝██║  ██║   ██║      ██║ ╚═╝ ██║███████╗██║  ██║███████╗██║██║ ╚████║#
#╚═╝  ╚═╝╚══════╝ ╚═════╝ ╚══════╝ ╚══╝╚══╝ ╚═╝  ╚═╝   ╚═╝      ╚═╝     ╚═╝╚══════╝╚═╝  ╚═╝╚══════╝╚═╝╚═╝  ╚═══╝#
# █████╗ ██████╗  ██████╗ ██╗   ██╗ █████╗ ██████╗ ██████╗ ██╗  ██╗ ██████╗ ███╗   ███╗███████╗                 #
#██╔══██╗██╔══██╗██╔════╝ ██║   ██║██╔══██╗██╔══██╗██╔══██╗██║  ██║██╔═══██╗████╗ ████║██╔════╝                 #
#███████║██║  ██║██║  ███╗██║   ██║███████║██████╔╝██║  ██║███████║██║   ██║██╔████╔██║█████╗                   #
#██╔══██║██║  ██║██║   ██║██║   ██║██╔══██║██╔══██╗██║  ██║██╔══██║██║   ██║██║╚██╔╝██║██╔══╝                   #
#██║  ██║██████╔╝╚██████╔╝╚██████╔╝██║  ██║██║  ██║██████╔╝██║  ██║╚██████╔╝██║ ╚═╝ ██║███████╗                 #
#╚═╝  ╚═╝╚═════╝  ╚═════╝  ╚═════╝ ╚═╝  ╚═╝╚═╝  ╚═╝╚═════╝ ╚═╝  ╚═╝ ╚═════╝ ╚═╝     ╚═╝╚══════╝                 #
#██╗███╗   ██╗███████╗████████╗ █████╗ ██╗     ██╗     ███████╗██████╗     Author:                              #
#██║████╗  ██║██╔════╝╚══██╔══╝██╔══██╗██║     ██║     ██╔════╝██╔══██╗          SomeWhereOverTheRainBow        #
#██║██╔██╗ ██║███████╗   ██║   ███████║██║     ██║     █████╗  ██████╔╝    Contributors:                        #
#██║██║╚██╗██║╚════██║   ██║   ██╔══██║██║     ██║     ██╔══╝  ██╔══██╗          JackYaz,gspannu,thelonelycoder #
#██║██║ ╚████║███████║   ██║   ██║  ██║███████╗███████╗███████╗██║  ██║    v1.8.1                               #
#╚═╝╚═╝  ╚═══╝╚══════╝   ╚═╝   ╚═╝  ╚═╝╚══════╝╚══════╝╚══════╝╚═╝  ╚═╝                                         #
#################################################################################################################
 Info:  Detected RT-AX86U router.
 Info:  Detected Linux platform.
 Info:  Detected ARMv8 architecture.
 Info:  JFFS custom scripts and configs are already enabled.
 Info:  AI_VERSION=v1.8.1
 Info:  New RELEASE ADGUARDHOME_VER=v0.108.0-b.71 Available!
 Info:  ADGUARDHOME_VER=v0.107.63
 Info:  Run Option 1 to if you want to change builds or upgrade when updates are available.
 Info:  To visit AdGuardHome,
 Info:  please go to http://192.168.1.254:14711.
 Info:  You can use the WebUI to change things to your liking!
 Info:  Stop by https://github.com/AdguardTeam/AdGuardHome/wiki
 Info:  for any configuration needs.
 Info:  Choose what you want to do:
  1) Install/Update AdGuardHome
  2) Uninstall
  3) Change Username/Password
  4) Reconfigure
  b) Backup
  r) Restore
  q) Quit
 =>  Please enter the number that designates your selection:, [1-4/b/r/q]: 1
 Info:  This operation will install AdGuardHome and related files (<6MB)
 Info:  to ENTWARE, no other data will be changed.
 Info:  Also some start scripts will be installed/modified as required.
 =>  Do you want to install AdGuardHome? [y/n]: y
 Info:  installer is up to date. Skipping...
 Info:  New RELEASE ADGUARDHOME_VER=v0.108.0-b.71 Available!
 Info:  Updating ADGUARDHOME_VER=v0.107.63 to v0.108.0-b.71.
 Info:  Downloading AdGuardHome_linux_arm64.tar.gz
 Info:  AdGuardHome.sh is up to date. Skipping...
 Info:  S99AdGuardHome is up to date. Skipping...
 Info:  rc.func.AdGuardHome is up to date. Skipping...
 Info:  init-start file already configured
 Info:  services-stop file already configured
 Info:  dnsmasq.postconf file already configured
 Info:  Configure service-event-end file
 Info:  Configuring AdGuardHome...
 Info:  Checking AdGuardHome configuration...
 Info:  Found previous AdGuardHome config file
 =>  Do you want to use this file without reconfiguring? [y/n]: y
 Info:  Use previous settings file
 Info:  Starting AdGuardHome...
 Checking AdGuardHome...              dead.
 Checking AdGuardHome...              alive.
 Info:  Please wait while we perform one last check.
 Checking AdGuardHome...              alive.
 Info:  AdGuardHome setup is complete.
 Info:  Operation completed, returning to Main Menu. You can quit or continue.
=====================================================