Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adguard "Auto-update failed. Please follow these steps to update manually." #212

Open
micceo opened this issue Mar 29, 2024 · 3 comments
Open

Comments

@micceo
Copy link

micceo commented Mar 29, 2024

Hi ladies and germs!

"AdGuard Home v0.107.46 is now available!" and trying to updates give me this:
Auto-update failed. Please follow these steps to update manually.

This just me or a general quirk?

Should I just go ahead and update the manual way or wait for some fix through the repository or other means?

On opnsense:
OPNsense 24.1.4-amd64
FreeBSD 13.2-RELEASE-p10
OpenSSL 3.0.13

Adguard through installed and which has been updating as it should before, installed from added repository.
Ver: v0.107.45

@Stephen-X
Copy link

Stephen-X commented Apr 9, 2024

FYI I "fixed" the problem by reinstalling AdGuard Home and attempting another update after rebooting. Configurations weren't lost.

@kisst
Copy link

kisst commented Apr 25, 2024

I was about to do the manual update, when I discovered that my config file is just plain missing, no data folder no config, and while the service is running and it's configured, I can't find the config hence can't do a backup and considering the amount of changes I already did to the config I really don't want to start from scratch.
Looking at the service definition in /usr/local/etc/rc.d/adguardhome is see no custom config location to be set, however the default location is just empty, I am currently running a whole root filesystem level grep for unique parts of the running config, but no luck yet, before the next reboot I want to resolve this, any clue where to look?

@kisst
Copy link

kisst commented Apr 25, 2024

I managed to trigger a write out the current config file by making a change on the admin interface, and with that I was able to create the backup of the config, and just run the upgrade, apart from the lost query log history it worked fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants