Not starting anymore about addon-adguard-home HOT 33 CLOSED

You could try using ha supervisor repair from one of the add-on terminals. Please note, if you have customizations (custom Docker container), those would be erased.

from addon-adguard-home.

@Simperdy The VM should NOT have a DHCP reservation when using AdGuard, but instead must be statically configured. You will run into the same issue again if you don't do this.

from addon-adguard-home.

You can partially import a snapshot to restore.

Importing the broken backup to this new install would just broke Adguard again. I need to move config files into the addon folder, not sure which though

EDIT: Fixed importing Adguardhome.yaml

from addon-adguard-home.

You could try using ha supervisor repair from one of the add-on terminals.

I had the same issue, this fixed it for me.

from addon-adguard-home.

👋 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 useful.

from addon-adguard-home.

Same here, not starting after update, also I don't see logs in supervisor

from addon-adguard-home.

Its the same Issue as #70
Apparently if your AdGuardHome.yaml is set to use TLS but has the https port set to 0 the issue starts.

I was able to copy the AdGuardHome.yaml from my container to my host, edit the yaml to:

tls:
  enabled: false

and copy it back to the container. AdGuard is starting backup fine :)

The file is in the following folder /data/adguard/AdGuardHome.yaml

from addon-adguard-home.

It's really not the same issue as it has been resolved.

There are two logs to check, the Addon/Log tab and also Supervisor/System/System Log.

There will be an issue in one of them

from addon-adguard-home.

This is the error

20-05-31 11:15:58 ERROR (SyncWorker_17) [supervisor.docker] Can't create container from addon_a0d7b954_adguard: 404 Client Error: Not Found ("No such image: hassioaddons/adguard-armv7:2.4.1")

from addon-adguard-home.

@Razer0123 That means the download failed, probably not enough diskspace to complete the upgrade operation.

from addon-adguard-home.

@Razer0123 That means the download failed, probably not enough diskspace to complete the upgrade operation.

I have over 24gb available

from addon-adguard-home.

Hmm, interesting, @Razer0123 Have you followed step 1 of the AdGuard installation guide? Does your box have a statically configured IP (not DHCP reservation in your router) and external DNS servers?

from addon-adguard-home.

I have now, but not sure it changes anything
Any way i could download the file manually?

from addon-adguard-home.

I have uninstalled and reinstalled the addon, works now
Not sure if it was a bad install or a config issue

Any way i could import settings from the old backup? which file should i move over?

from addon-adguard-home.

You can partially import a snapshot to restore.

from addon-adguard-home.

I had the same issue - Addon not starting after update. A reboot fixed this for me.

from addon-adguard-home.

Fixed it with help from @frenck by setting a static IP address and external DNS server

from addon-adguard-home.

Same issue here - not starting anymore

20-05-31 19:33:38 ERROR (SyncWorker_18) [supervisor.docker] Can't create container from addon_a0d7b954_adguard: 404 Client Error: Not Found ("No such image: hassioaddons/adguard-armv7:2.4.1")

from addon-adguard-home.

Quite a few people had this issue, see thread here:
https://community.home-assistant.io/t/adguard-addon-stopped-working-cant-create-container-no-such-image/200790/9

@frenck - I'm wondering if it could be a bootstrapping issue. I require adguard's DNS to resolve the docker registry in order to pull the new image. So if the order of events is:

1. shutdown adguard
2. pull new docker image
3. restart adguard

Then we will have an issue in step 2 because of no DNS?

If there's a simple check I can do to test I'd be willing to help?

Home Assistant Community

Adguard Addon stopped working - Can't create container / No such image

The issue has been reported here, with some possible fixes. What worked for me was installing Terminal & SSH from the Add-on store. Then pasting and running ha supervisor repair in the terminal. I had to start and restart Adguard a couple of times before it started working again

from addon-adguard-home.

Please see step one of the installation details https://github.com/hassio-addons/addon-adguard-home/blob/master/adguard/DOCS.md#installation

GitHub

hassio-addons/addon-adguard-home

AdGuard Home - Home Assistant Community Add-ons. Contribute to hassio-addons/addon-adguard-home development by creating an account on GitHub.

from addon-adguard-home.

@Gaff I can't fix people not reading. It is clearly defined as the first step. All reports until now have come down to skipping that first step.

from addon-adguard-home.

Ok Fair enough - I accept that I, too, didn't read it properly.

Still - would be good if there was some sort of warning / check. There's a few things I can think of:

• Have the container error (or refuse to start?) if it detects that it is it's own DNS server.
• Download the new image before shutting down the old one.
• If an image doesn't start up (or pull) then fall back.
• Attempt to pull the image on every startup [for some reasson HASS didn't attempt to re-pull] even after I rerouted my DNS.

Appreciate most of these are upstream issues. Do any of them have any merit do you think?

from addon-adguard-home.

Have the container error (or refuse to start?) if it detects that it is it's own DNS server.

We can't. Or else I would have build that.

Download the new image before shutting down the old one.

That is not fixable for an add-on.

If an image doesn't start up (or pull) then fall back.

Again not fixable for an add-on.

Attempt to pull the image on every startup [for some reasson HASS didn't attempt to re-pull] even after I rerouted my DNS.

Outside of add-on scope.

Do any of them have any merit do you think?

🤷

from addon-adguard-home.

Sure. I did say they were upstream / home-assistant issues.

You could ping a randomly generated name, then check the logs to see if it's present?

I accept this is pretty convoluted... but it's techinically doable! 😛

from addon-adguard-home.

No, we can't. You now assume logging is enabled.

from addon-adguard-home.

Hi,

• updated to the latest AdGuard version
• after the issue with Adguard I uninstalled it but I am not able to reinstall it.
• also no update of either core, supervisor or any other add-on could be performed.
• I always get 500 internal server errors about refused connections.
• resolving hosts doesn't work anymore.

@frenck: how can Hassio on docker on NUC/Ubuntu be brought back to normal dns config "pre-adguard"?

20-06-03 23:07:07 ERROR (SyncWorker_18) [supervisor.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:226 -> 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]:35943->[::1]:53: read: connection refused"). 20-06-03 23:07:07 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor fails!

20-06-03 23:07:09 ERROR (SyncWorker_10) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.4 -> 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]:37962->[::1]:53: read: connection refused"). 20-06-03 23:07:09 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails

Best
Dominik

from addon-adguard-home.

"Hassio on docker" does not exist and has never existed. I guess you mean you are running a Supervised installation.

Your host system has DNS issues. Probably related to changes you've made to your host system in order to be able to run AdGuard.

Please note, that the host system is your responsibility and not supported.

from addon-adguard-home.

You could try using ha supervisor repair from one of the add-on terminals. Please note, if you have customizations (custom Docker container), those would be erased.

This worked for me.

from addon-adguard-home.

You could try using ha supervisor repair from one of the add-on terminals. Please note, if you have customizations (custom Docker container), those would be erased.

This worked for me.

Running hassio as vm on Synology NAS.
Synology NAS has a static ip and dns servers, hassio vm has a dhcp reservation.

from addon-adguard-home.

@Simperdy The VM should NOT have a DHCP reservation when using AdGuard, but instead must be statically configured. You will run into the same issue again if you don't do this.

Thanks for the quick reply, I will change that soon.

Edit:
Changed the IP/GW/DNS to static via SSH & Web Terminal Addon and nmcli. (https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md)
After VM reboot the AdGuard Addon started without problems.

from addon-adguard-home.

I have uninstalled and reinstalled the addon, works now
Not sure if it was a bad install or a config issue

Uninstall and reinstall worked for me too.

from addon-adguard-home.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from addon-adguard-home.

Fully solved with the latest version of the add-on.

⬆️ AdGuard Home v2.6.0

https://github.com/hassio-addons/addon-adguard-home/releases/tag/v2.6.0

from addon-adguard-home.