So there is no workaround. You were good for only one reboot. Correct? And you never requested a download of the latest version from the GUI. Do you recall which version of kamoj-addon survived a reboot?Thank you!! I tried this and yes, this does work, and I was able to revert back to version v0.107.29 of AGH, I just had to make sure to uncheck 'install' for adguard home first and it worked for me. I did a reboot and AdGuard Home was still working!! but sadly for some reason it auto updated to the latest version .38, then when I did another reboot again, AGH stopped working, so for sure its the newer versions that do not work with Kamoj add on.
When you have lost internet access are you able to check out the DNS and WWW ports from the /tmp/addons directory and cat the firewall-start-adguardhome.sh, adguard_port_dns, and adguard_bind_port_www for bad values? As you recall "6060.5300" is not a valid DNAT value. And I assume that the AdguardHome URL does not point to x.x.x.x:8080, but rather x.x.x.x.
I'm not sure why @kamoj is attributing this to AGH as this anomalous behavior is generated by addon_adguard.sh and the GUI interactions.
Clearly @kamoj did not intend his workaround to force a download of the latest AGH on the 2nd reboot.
Have you enabled verbose adguard logging? Have you inspected the adguard logfiles at /var/log/AdGuardHome.log?
There should be a clearcut way to install/uninstall/stop/start/reset AGH using addon_adguard.sh without relying on the GUI interactions. And that is no longer the case.