Auto Update failed for v0.107.15

[sydsyd]

On a Raspberry Pi - auto update is failing.
Haven't seen this issue before with other updates.
Just letting community know.

[tomhusband]

Yes, I can't update either. Installing manually is a bit intimidating for me. My Linux skills are pretty basic. Are there plans to correct this?

[sydsyd]

Updating manually on a Raspberry Pi didn't go well for me... I had to reinstall.

[tomhusband]

I really don't want to do that. I'll give it some time. Maybe there's a fix coming.

[threo9]

Waiting for fix too.

[raskx]

Not only rasp. 3 installations - OL8, and two Ubuntu 22. Autoupdate fails everywhere. +1 for fix.

[ainar-g]

This is an unfortunate consequence of #4970.

Theoretically, something like this could work:

curl -H 'Content-Type: application/json' -X POST -v 'http://LOGIN:[email protected]/control/update'

Where LOGIN and PASSWORD are your web interface login data and 127.0.0.1 is the address of AdGuard Home's web UI. That successfully updates AdGuard Home from v0.107.14 to v0.107.15 for me.

[Dimak47X]

It's OK when it prints "OK". Or when update done successfully :)

Ok :) But I have applied the command above and changed only username, password and ip of my Raspberry Pi with AdGuard Home server. Maybe I should change something else in the command? Or maybe there are any other options to update the version without reinstalling AdGuard Home? Thanks.

[raskx]

It's OK when it prints "OK". Or when update done successfully :)

Ok :) But I have applied the command above and changed only username, password and ip of my Raspberry Pi with AdGuard Home server. Maybe I should change something else in the command? Or maybe there are any other options to update the version without reinstalling AdGuard Home? Thanks.

Maybe you should use localhost or 127.0.0.1 instead of real local IP. Thats worked for me that way.

[Dimak47X]

Maybe you should use localhost or 127.0.0.1 instead of real local IP. Thats worked for me that way.

If I use 127.0.0.1 then I get the error "connection refused"

• Trying 127.0.0.1...
• TCP_NODELAY set
• connect to 127.0.0.1 port 80 failed: В соединении отказано
• Failed to connect to 127.0.0.1 port 80: В соединении отказано
• Closing connection 0
  curl: (7) Failed to connect to 127.0.0.1 port 80: В соединении отказано

[Flyinace2000]

Should the curl command be run from another machine on the same network or while SSH'ed into the box running AdGuard?

[Dimak47X]

So I have found the problem. There was HTTPS encryption enabled on my AdGuard. In the web interface of AdGuard I went to Settings -> Encryption settings -> UNcheck "Enable encryption" and save configuration. After that the command above was completed successfully

• Trying 192.168.1.205:80...

• Connected to 192.168.1.205 (192.168.1.205) port 80 (#0)

• Server auth using Basic with user 'admin'
  POST /control/update HTTP/1.1
  Host: 192.168.1.205
  Authorization: Basic YWRtaW46YWRtaW4=
  User-Agent: curl/7.79.1
  Accept: /
  Content-Type: application/json

• Mark bundle as not supporting multiuse
  < HTTP/1.1 200 OK
  < Access-Control-Allow-Origin: http://192.168.1.205
  < Vary: Origin
  < Vary: Accept-Encoding
  < Date: Thu, 06 Oct 2022 14:40:24 GMT
  < Content-Type: text/plain; charset=utf-8
  < Transfer-Encoding: chunked
  <
  OK

• Connection #0 to host 192.168.1.205 left intact

After that I was able to login to web console again (be sure to use http in the address bar this time, not https) and check that version is v0.107.15 now. HTTPS encryption may be enabled again then.

[masdeirf]

@Dimak47X: don't work for me, I don't have encryption enabled on my AdGuard. 😐

[Dimak47X]

Which error did you get when you run the command? May you copy-paste the output from the terminal?

[SmogUA]

[masdeirf]

Failed to load resource: the server responded with a status of 415 (Unsupported Media Type)
only application/json is allowed

[masdeirf]

This is an unfortunate consequence of #4970.

Theoretically, something like this could work:

curl -H 'Content-Type: application/json' -X POST -v 'http://LOGIN:[email protected]/control/update'

Where LOGIN and PASSWORD are your web interface login data and 127.0.0.1 is the address of AdGuard Home's web UI. That successfully updates AdGuard Home from v0.107.14 to v0.107.15 for me.

Worked for me 👍🙏 but I needed to add the port:

curl -H 'Content-Type: application/json' -X POST -v 'http://LOGIN:[email protected]:PORT/control/update'

(HTTPS encryption was off)

[tomhusband]

@ainar-g Many thanks, this worked perfectly. I'm going to save the command. I might need it again someday.

[SmogUA]

Works fine for me. Thanks a lot!

[Flyinace2000]

So now that 0.107.16 I'm still stuck on dot14. My password has an "@" contained within. So if I run the command on my MacOS machine I tried the following command:

MY_PASSWORD=“12345@098765” curl -H 'Content-Type: application/json' -X POST -v 'http://Admin:${MY_PASSWORD}@10.0.1.1:81/control/update'

*   Trying 10.0.1.1:81...
* Connected to 10.0.1.1 (10.0.1.1) port 81 (#0)
* Server auth using Basic with user 'Admin'
> POST /control/update HTTP/1.1
> Host: 10.0.1.1:81
> Authorization: Basic 12345@098765=
> User-Agent: curl/7.79.1
> Accept: */*
> Content-Type: application/json
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 403 Forbidden
< Date: Mon, 10 Oct 2022 23:46:00 GMT
< Content-Length: 9
< Content-Type: text/plain; charset=utf-8
< 
* Connection #0 to host 10.0.1.1 left intact
Forbidden%

If I try a similar command while SSH into my OPNSense box which runs AdGuard. declaring the MY_PASSWORD variable doesn't work. Removing that and inserting the password back into the command returns the following error

root@OPNsense:~ # curl -H 'Content-Type: application/json' -X POST -v 'http://Admin:12345@098765@http://127.0.0.1:81/control/update'
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL

Https is not enabled.

[Flyinace2000]

Ended up just re-installing from the OPNSense plugin and reconfiguring my install. Took the opportunity to make a new password to remove the "@".

[add0242]

Have the same problem, my password uses an ']'

[Gavrook]

Hi I have 2 instances of AdGuard Home installed on 2 Ubuntu Server machines both setup the same, they were both working fine for ages but one has for the past few months been giving me the titled error and won't update. The other is still working perfectly fine and receiving updates.

A while ago I managed to do a manual update, that got it to it's current version but the auto-update error still persisted.

I have tried all above and nothing works. Getting connection refused.
Encryption is off, but annoyingly my password does have an @ in it.