[SOLVED] Can't install other addons while AdGuard Home addon is running.

[mjoshd]

Problem/Motivation

Cannot install addons or upgrade Hass.io while Adguard addon is running.
Stopped AdGuard addon and install/upgrade works as expected.
Re-tried install while Pi-hole addon was running and it worked as expected.

Expected behavior

Installation of other addons & upgrades of Hass.io work as normal.

Actual behavior

System logs from attempting to install the community MQTT & Web client addon:

19-01-13 16:46:53 INFO (MainThread) [hassio.addons.addon] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_mqtt
19-01-13 16:46:53 INFO (SyncWorker_28) [hassio.docker.interface] Pull image hassioaddons/mqtt tag 0.3.1.
19-01-13 16:47:03 ERROR (SyncWorker_28) [hassio.docker.interface] Can't install hassioaddons/mqtt:0.3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: read udp 127.0.0.1:35023->127.0.0.53:53: i/o timeout").

Steps to reproduce

Install, configure & start AdGuard Home addon.
Try to install any other addon while AdGuard Home is running.
Hopefully this is reproducible and not just a byproduct of my setup (Hass.io on Ubuntu Server 18.04).

Proposed changes

Not sure what the root of the issue is but I am happy to help in any way I can. Just let me know what is needed.

[addons-assistant]

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

[tjorim]

Dis you set a static IP with static external DNS servers on your server?

[mjoshd]

Yes, these are the DNS settings
for the host OS
/etc/netplan/50-cloud-init.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      dhcp4: false
      addresses: [192.168.1.198/24]
      gateway4: 192.168.1.1
      nameservers:
        addresses: [192.168.1.1,8.8.8.8,9.9.9.9]

and for Docker
/etc/docker/daemon.json

{"dns": ["8.8.8.8", "8.8.4.4"]}

[mjoshd]

The issue was solved by running the following, which is a slightly different version of what Silicon_Avatar posted in the Home Assistant Community forums:

sudo -s
systemctl disable systemd-resolved.service
reboot now

I can now install addons & perform Hass.io upgrades while AdGuard Home is running. 🎉

Hopefully this info will help others if they encounter the same situation.

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.