That's essentially it: After the 24.7.1 update, the Adguard plugin is visible, but refuses to start.
Any ideas?
Best e.
In my case it works without problems.
Quote from: atoll on August 10, 2024, 03:28:40 PM
That's essentially it: After the 24.7.1 update, the Adguard plugin is visible, but refuses to start.
Any ideas?
Best e.
I had the same issue. It would start and instantly stop. Reviewed the config and everything looked fine. Ended up deleting the yaml configuration file and redoing the whole configuration. Worked fine with a fresh config, so it acts like there was some setting it didn't like in old configs.
Post the full output when you run this
./usr/local/AdGuardHome/AdGuardHome
Chiming in that this is also happening me, as well as resolution.
Quote from: newsense on August 10, 2024, 07:30:09 PM
Post the full output when you run this
./usr/local/AdGuardHome/AdGuardHome
No output is generated, even with --verbose command when running directly from SSH.
I opened the log file in
/var/log/AdGuardHome.log and every attempted start of the service had the same type of error:
[fatal] clients: init persistent client at index 5: init blocked services "<my client>" : unknown blocked-service "<several different services>"Opening up
/usr/local/AdGuardHome/AdGuardHome.yaml and manually changing every client blocked services list to:
ids: []Saving the config and starting the service through the web gui again worked. Oddly after first logging into AdGuardHome again, the update banner at the top was active... but I'm 99.9% positive I was already on the latest version (but the UI was indicating it was a version behind). Applied the update, double checked all of my settings were correct, but I did notice that the global service blocking was all disabled... but that could have been from me not paying attention to which client(s) I was editing in the config ::). I think I will wait on turning any service blocking back on for now.
Hope this helps anyone else dealing with this!
I've seen these downgrades happening when the AGH package is reinstalled due to a change in the repo, but it is all fine after you do the upgrade again from the AGH GUI
Thanks for the input. In the end, I just deleted the .yaml file with the config; it was the fastest solution.
Now AdGuard is up and running again.