1
24.7 Production Series / Re: Adguard not starting after Update
« on: August 10, 2024, 10:35:10 pm »
Chiming in that this is also happening me, as well as resolution.
No output is generated, even with --verbose command when running directly from SSH.
I opened the log file in
Opening up
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!
Post the full output when you run thisCode: [Select]./usr/local/AdGuardHome/AdGuardHome
No output is generated, even with --verbose command when running directly from SSH.
I opened the log file in
Code: [Select]
/var/log/AdGuardHome.log
and every attempted start of the service had the same type of error: Code: [Select]
[fatal] clients: init persistent client at index 5: init blocked services "<my client>" : unknown blocked-service "<several different services>"
Opening up
Code: [Select]
/usr/local/AdGuardHome/AdGuardHome.yaml
and manually changing every client blocked services list to: Code: [Select]
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!