MT2500 working now, thanks! I thought it wasn’t, but after restarting AdGuard, it worked."
1 Like
I can confirm the script / Adguard Home is working correctly again on the Brume 2 - Firmware version: 4.7.4 - many thanks.
1 Like
Can you add '/etc/init.d/adguardhome' to 'sysupgrade.conf' in your next version of the script?
The fix for the MPTCP bug is not persistent after an update right now.
1 Like
Thanks for letting me know, I updated the script 
2 Likes
I decided to have a go with the script which went really smooth i tested it first on my GL-AXT1800 Slate AX ruining 4.6.11 worked a treat but when i updated to beta firmware openwrt-ax1800-4.8.0-0626-1750903293 things went pear shaped.
Do i needed to run the script every time a new firmware is released (i did say yes to making the script permanent), and i guess that adguardhome is compressed somewhere else as its missing from the directory even though its working it shows the AdGuard home stock release that comes with the firmware
it refused to update until i edited the (procd_set_param command /usr/bin/AdGuardHome --glinet -c /etc/AdGuardHome/config.yaml -w /etc/AdGuardHome -l syslog) then I clicked updated and failed to update.
using winSCP no adguardhaome in the AdGuard directory so i guess its compressed somewhere else.
If i get into more trouble will using UBOOT put the router back to normal.
I'm not very good with SHH that's why in the past i have updated AdGuard by winSCP and has worked fine up until the latests firmware releases only the Flint 2 works fine but the Flint 3 has no older firmware so i cant even use winSCP to update AdGuard.
Any help will be much appreciated
Updating using the AdGuard Self-Update isn't supported while using my script.
Please follow those steps and when you are done, reinstall the current firmware:
Many thanks for the reply i reinstalled the firmware all working but AdGuard still on Version: 0.107.56 does it up date at certain times, and is that correct that you can no longer see AdGuard home in its directory only the data folder and the config.yaml
Well I did contact support on the question of updating AdGuard home made harder by the new beta firmwares and there official response is it should not updated, just thought I would post their Response.
Admon, take a look at the script, a few days ago I try to use it to update AGH on my AXT1800 with recently installed 4.8 beta, and it bricked the router, just wanted let you know 
Thanks for what you do for the community
1 Like
That’s interesting I was wondering about that, the new firmware’s across the board has stoped me manually updating AdGuard which is a pain and you also can no longer view AdGuard home using winSCP for some reason, I wish they would bring back the update option fir routers with plenty of space like the Flint 2 & 3
Can't confirm that so far.
I updated AdGuard to the latest version on F/W 4.8.2 (FLINT2) and now I cannot use a login and password to log into the AdGuard web portal, before I could - now I can only log in only if I log into the flint first. Any ideas? (pre 4.8.2 f/w was no issue updating it)
This isn't an issue since the AGH authentication is handled by GL firmware instead of AGH.
You can enable direct login by modifing the config.yaml, see Aguard Home Password? - #4 by dandek
1 Like
My conf file already includes a working user & pass. Nothing has changed on my end.
EDIT: Downgraded to v0.107.64 and all works well again, seems to have been an issue with v0.107.65!
Update on F/W 4.8.2 (FLINT2) I managed last night to update AGH really happy about that also managed to get a domain to not go through the tunnel and direct to WAN, I will do more testing tonight but AdGuard is still not visible using winSCP even if I wait 10 minutes, even after upgrade to the latest AGH still not visible, if you check the Flash rom it does not show AGH is taken any space, if I have time I will try the Flint 3 but that seems less stable to me.
Hi admon I may try your script on the Flint 3 if you’ve tried it on Firmware v4.8.1 it may solve a problem I’ve contacted GL.iNet technical because manually updating AdGuard it runs for a short time or if you restart the router then AdGuard disappears completely but is still running (still blocking ads) does you’re script overcome this problem, but GL.iNet just tell me that it is not recommend to update AdGuard with no exception to what’s happening I understand the reason way back when they stoped it updating because the lack of room, but Flint 2 & 3 there is no reason why it should be updated.
I’m now back to my Flint 2 as manual updating works fine I’m currently on ADH Version: v0.107.66 I feel I’m alone here wanting to update AdGuard if so then I will get a life.
Since I use my script often, I can say that it works on Flint 3 with 4.8 
Hi thanks if I get in to deep water will u-boot put things back to normal
Hello admon just run the script on my Flint 3 and it works grate and doesn’t disappear now my Flint 3 is on Version: v0.107.67 really pleased thank you, i didn’t make the script permanent will it need to be run on future firmware updates.
Yup. You should always run the script after a firmware upgrade.
1 Like