Adguard unable to start after update

Apps and Virtualization
,
1

after updating adguard the now is unable to start, Now showing

[EFAULT] Failed ‘up’ action for ‘adguard-home’ app. Please check /var/log/app_lifecycle.log for more details

checking the lifecycle log I get the following errors:

[2025/02/04 17:12:28] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘adguard-home’ app: adguard Pulling
adguard Error Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:46633->[::1]:53: read: connection refused

Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:46633->[::1]:53: read: connection refused

[2025/02/04 17:14:52] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘adguard-home’ app: adguard Pulling
adguard Error Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:54194->[::1]:53: read: connection refused

Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:54194->[::1]:53: read: connection refused

[2025/02/04 17:19:59] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘adguard-home’ app: adguard Pulling
adguard Error Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:36653->[::1]:53: read: connection refused

Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:36653->[::1]:53: read: connection refused

[2025/02/04 17:20:34] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘adguard-home’ app: adguard Pulling
adguard Error Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:41143->[::1]:53: read: connection refused
Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:41143->[::1]:53: read: connection refused

[2025/02/04 17:26:21] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘adguard-home’ app: adguard Pulling
adguard Error Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:39071->[::1]:53: read: connection refused

Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:39071->[::1]:53: read: connection refused

2

I just had the same issue after upgrading to 25.04.0.
Did you find any solution?

I also tried to reinstall Adguard from scratch. After I deleted the app, the installer thought it was already installed and asked me if I wanted to created a second instance. I did it and that wasn’t working either

3

Maybe related:

4

I am also having this exact problem after switching to the community fork. I’m also running AdGuard version 1.1.26 and I’m at a complete loss on how to get this working

5

I read through the jira and got adguard’s app to work by changing the DNS port. However, I feel like this completely defeats the purpose of this app if I can’t run the DNS service on port 53…

6

What?

I’m using Adguard on port 53, which was made possible by changing the Incus DNS port to something else as linked above…

7

Ahh, my apologies I found your fix from the other post. Thank you so much!

1 Like
8

I got it running under incus:

1 Like