Hello, I was back from holidays and updated some stuff, also my router to latest firmware, some scripts, agh, etc and... entware, sadly.
After I've updated entware, adh stopped working, I can't connect anymore to router:14711 and I can't unistall or reinstall anything with AMTM
I've tried to execute some commands I've read here and in other post like
Code:
curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer
but no luck, I've also tried to change builds to edge, beta or stable but always same result: installation get stuck at "starting adguardhome"
Of course I've tried to reboot router several times but always same result.
I would like to avoid to make a clean install of everything again, it's possible to recover?
Thanks
View attachment 52913
View attachment 52914
Whenever adguardhome updates the .YAML configuration file schema, older .YAML configurations don't always update to match the latest versions of adguardhome. You may be using an old backup you made months ago (or longer). In this uncertain scenario, You may be faced with no other choice but starting over. There have been significant settings that have changed in the .YAML file in the past 6 months (or less) which includes how the default WEBUI port number is configured in the .YAML file. I can see your backup .YAML file is not up-to-date with the latest .YAML format.
Your lack of port number being listed by the installer image below suggest such:
It should appear after
http://192.168.50.1:[someportnumber] .
This tells me that the more up-to-date installer is no longer parsing your much older incompatible .YAML file. Which also explains why AdGuardHome is stuck at
The fact that AdGuardHomes .YAML configuration file checker is ignorant to, or not catching this as a problem is baffling. But is a clear indication to why your AdGuardHome is stuck at "Starting AdGuardHome...".
If you know your way around using nano, or other terminal editors, you may be able to piecemeal copy over settings you do not wish to have to reconfigure in the webui. That way you preserve your old settings with the new .YAML configuration. All of AdGuardHomes files are located in
/opt/etc/AdGuardHome the one you would be interested in is
AdGuardHome.yaml.
As for this issue with AdGuardHome, I am fighting a continuous battle with them to get them to improve their schema checker, and format updater. AdGuardHome literally has no sufficient built in mechanisms that adequately update the .YAML file yet here they go changing the format of the .YAML file again. Hence another example of AdGuardHomes continuous beta cycle.
You can edit the .YAML file making sure,
Code:
http:
address: 0.0.0.0:14711
at the top of the .yaml file, this is the new appropriate format for the .YAML file.
The old version would have:
Code:
bind_host: 0.0.0.0
bind_port: 14711
at the top of the .YAML file.
Also, you may need to modify the schema version.
is the one the installer uses ATM, but I need to research if this has changed yet again.
If AdGuardHome users wish for this issue to go away, I recommend (suggest) you open a feature request to AdGuardHome to improve AdGuardHome's ability to update Schema and ability to check the .YAML file changes as the AdGuardHome developers add or change features with in it. Other wise, it is ultimately the users job to keep track of these issues and changes by following AdGuardHome's release updates and reading AdGuardHome's wiki.
The summer has come and gone, leaving behind a decent harvest of long-awaited features and improvements, with a side order of bug fixes :grapes:! Service blocking pause schedule Users can now easil...
github.com
Network-wide ads & trackers blocking DNS server. Contribute to AdguardTeam/AdGuardHome development by creating an account on GitHub.
github.com
In Entware AdguardHome update is disabled by default -
https://github.com/Entware/entware-go/blob/master/adguardhome-go/files/adguardhome.conf#L11
Current AdguardHome versions from GitHub do run correctly, but it may stop in future. We make special patches for all go binaries to run correctly in Entware. Just as an example -
https://github.com/Entware/Entware/blob/master/tools/go-src/patches/500-entware.patch
@zyxmon , I hope the Entware developers have a contingency plan to deal with future hiccups caused by AdGuardhomes broken configuration file checker and inability to start/stop services when the .YAML file is aged past a point of schema acceptance, other wise building your own binaries might not be the only solution you may have to provide.
