AdGuard not updating

[svengru]

Looks like the bug was introduced in the previous version and this is not a server-side issue:
https://github.com/AdguardTeam/AdGuardHome/discussions/4989#discussioncomment-3798085

Did the manual update yesterday without any issue.

[guest34985]

I'm on the beta channel and on both systems it ran fine.
On one I had to refresh the page during update.

I used your repo to add AGH to my OPNsense (thanks for that btw!) and have 0.107.9 installed currently, but instead of version 0.107.15 I get offered 0.108.17 as an update. So I would switch to the beta branch I guess. How can I change back to stable branch for updates?

BR

[Vexz]

Hm, maybe overwrite the files of your currently running AGH with the ones from the latest stable version. But stop the service first and respect the file permissions. I'm running on the latest stable version and can't find an update. This means AGH doesn't offer me a beta version but instead searches for a newer version that doesn't exist yet. Could be that it is a bug on the old version you're running but that's just a wild guess.

[NeoDragon]

Solution picked from Adguard bug thread:


- SSH in your opnsense box
- Send this command, change USERNAME:PASSWORD to your Login/Pass of Adguard
- Specify port if you changed the default

Code Select Expand

curl -H 'Content-Type: application/json' -X POST -v 'http://USERNAME:PASSWORD@127.0.0.1/control/update'

If you are running adguard on SSL connection :

Code Select Expand

curl --insecure -H 'Content-Type: application/json' -X POST -v 'https://USERNAME:PASSWORD@127.0.0.1:443/control/update'

[RamSense]

Thanks for sharing!
I tried https version, but i got this error:
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL
I tried plain http:
Ambiguous output redirect.

[Koloa]

Solution picked from Adguard bug thread:


- SSH in your opnsense box
- Send this command, change USERNAME:PASSWORD to your Login/Pass of Adguard
- Specify port if you changed the default

Code Select Expand

curl -H 'Content-Type: application/json' -X POST -v 'http://USERNAME:PASSWORD@127.0.0.1/control/update'

Can confirm this worked - but, in my case, I had to use the IP address of my AGH box on my LAN, localhost didn't work.

Updated to .b17 successfully, no apparent loss of data.  Thank you!

[NeoDragon]

Thanks for sharing!
I tried https version, but i got this error:
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL
I tried plain http:
Ambiguous output redirect.

You might wanna try using the lan address and see if it works this way.

[Vesalius]

Solution picked from Adguard bug thread:


- SSH in your opnsense box
- Send this command, change USERNAME:PASSWORD to your Login/Pass of Adguard
- Specify port if you changed the default

Code Select Expand

curl -H 'Content-Type: application/json' -X POST -v 'http://USERNAME:PASSWORD@127.0.0.1/control/update'

Can confirm this worked - but, in my case, I had to use the IP address of my AGH box on my LAN, localhost didn't work.

Updated to .b17 successfully, no apparent loss of data.  Thank you!

Same here, but had to add the IP address and port for it to work for me. Thanks, that was much easier than I expected.

[RamSense]

Must be something easy to miss. Ip of the Adguard/opnsene box also did not work over here:
(both http and https have different port and used that port)
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL

ah just saw this post: I was also having the same issue with the auto update failing. I tried the curl command and my password (containing special characters) was also failing.

The supposed sollution there got me a bit further, but still not successful

/update request isn't allowed now
* Connection #0 to host 192.168.1.1 left intact

**Solved it
I was also logged in into adguard webpage while trying to use the command above to update. This did not work. While not being logged in and trying the command, it updated!

[mimugmail]

I updated the repo to include 0.107.15 ... you need to stop / start agh after update manually

[Vexz]

I updated the repo to include 0.107.15 ... you need to stop / start agh after update manually

Awesome! The AGH devs said they fixed the update problem in v0.107.15 so we should be good for now until we will face a different update problem anytime in the future.  ;D
Just out of curiosity: Why did you choose the stable version instead of beta? In the past the repo came with the beta version of AGH.
Do you recommend locking the package because an update of the package in the future might downgrade a newer currently running version?

FYI: The plugin details of AGH (System > Firmware > Plugins) doesn't mention v.1.8 yet. Maybe you wanna update those.

[mimugmail]

Honestly I have no idea why its beta. I thought I replaced it ages ago. Lets stick to stable

[guest34985]

I updated the repo to include 0.107.15 ... you need to stop / start agh after update manually

That worked great, thx a lot!

[abulafia]

Similar issue with the new update to .16 unfortunately...

[RamSense]

the same method above worked for updating to .16 also over here. Have you tried that?