Can't install any add-on

Hello,
I am running HA in container ubuntu in NUC.
I had AdGuard running OK for about 2-3 weeks but one day I don’t know what changed and it stopped working correct.

 Add-on version: 2.3.1
 You are running the latest version of this add-on.
 System: Ubuntu 16.04.6 LTS  (amd64 / qemux86-64)
 Home Assistant version: 0.105.4
 Supervisor version: 200
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adguard.sh: executing... 
[cont-init.d] adguard.sh: exited 0.
[cont-init.d] discovery.sh: executing... 
[09:35:42] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[09:35:42] INFO: Starting AdGuard Home server...
2020/02/18 09:35:42 [info] AdGuard Home, version v0.100.9, channel release

2020/02/18 09:35:42 [info] Upstream 0: 1.1.1.1:53
2020/02/18 09:35:42 [info] Go to http://127.0.0.1:45158
2020/02/18 09:35:42 [info] Starting the DNS proxy server
2020/02/18 09:35:42 [info] Ratelimit is enabled and set to 20 rps
2020/02/18 09:35:42 [info] The server is configured to refuse ANY requests
2020/02/18 09:35:42 [info] DNS cache is enabled
2020/02/18 09:35:42 [info] Creating the UDP server socket
2020/02/18 09:35:42 [info] Listening to udp://[::]:53
2020/02/18 09:35:42 [info] Creating the TCP server socket
2020/02/18 09:35:42 [info] Listening to tcp://[::]:53
2020/02/18 09:35:42 [info] Entering the UDP listener loop on [::]:53
2020/02/18 09:35:42 [info] Entering the tcp listener loop on [::]:53
[09:35:42] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

I tried with Pi-Hole and had the same nginx error (whatever that is).

Unistalled both of them and tried to install adguard again but I get an error message saying “Failed to install addon, Unknown Error, see logs”.
Then in logs:

20-02-20 22:18:49 ERROR (SyncWorker_15) [hassio.docker.interface] Can't install hassioaddons/adguard-amd64:2.3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38263->[::1]:53: read: connection refused").

After some hours of searching,I will try to sum up where I believe the problem is.

1st) The NUC has static IP through my router. I guess I should have it through this procedure but I don’t know how to do that since there is no “import from USB” in the system tab. Probably the instructions are only applied to RPI.
2nd) I might have “damaged” the DNS and that’s why I can’t install any add-on. Again I don’t know how to change DNS of NUC. Maybe it is linked with the 1st issue.
3rd) I don’t know how and where to run the command “hassio su repair” (or something like that which I don’t remember exactly now), which could probably repair the DNS issue.

Some of the things that I already tried:
image
In homeassistant:


and debug:

Also I would like to note that I don’t have SSH add-on installed in HA.

I hope I don;t need to unistall and install HA all over again!!!

Thank you for reading and posting any suggestions!

What is the operating system you are running?

Ubuntu 16.04

So in order to get things like AdGuard running, you need to modify your host system, since Ubuntu uses a systemd-resolved that uses the same port.

My current guess, is that you have modified your host incorrect, causing the systemd-resolve not to be running and thus host resolving being disabled.

This causes this behavior. You need to fix the DNS resolving on your host system.

1 Like

As usually, you were right.
When I reset to default the DNS of host everything came back to normal.
The reason I have changed it, was for the port 53 in order for Adguard to work properly.
And now the million dollar question is what should I do to run Adguard in NUC.
I tried also this solution but didn’t work.
Thx Frenck!