Adguard failed to setup, will retry

[Gunth]

The problem

Hi all, Since the latest release (2024.1.6) i lost the Adguard integration entities, all the sensors are unavailable and I dont see any logs in the log file except in the integration page "Failed setup, will retry".

The adguard addon is still working correclty.

G.

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

2024.1.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Adguard

Link to integration documentation on our website

https://www.home-assistant.io/integrations/adguard/

Diagnostics information

No diagnostics file available

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing in the log file :-(

Additional information

No response

[home-assistant[bot]]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (adguard) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of adguard can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign adguard Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

adguard documentation adguard source _{^{(message by IssueLinks)}}

[Vansmak]

Same here. I have 2 adguard instances that are not ha addons but were successfully integrated before and now fail to setup

[SamJongenelen]

Same here. Worked for years now but recently failed.

[bjorndegroot]

Same here!

[Dio55]

Also same here

[N3rdix]

You could turn on debug logging, reload the integration and share the logs. Maybe that's already a hint. My Adguard Home (externally running, not the addon) is still correctly connected to the integration with 2024.1.6

[Vansmak]

i was able to add them again successfully after deleting and restarting

[SamJongenelen]

I deleted it and rebooted. It discovered it again, but immediately it went to failed to setup.. I am using haos and addon

[hitesh-singh]

I'm having the same issue, after update Uninstall the integration, Rebooted HA, Tryed reconfigure, nothing worked.

I'm on the following Version

Core: 2024.1.6 Supervisor: 2023.12.1 Operating System: 11.4 Frontend: 20240104.0

AdGuard Home Version: v0.107.43

[tescophil]

I'm running adguard externally to home assistant and have the same issue, failed to setup since the upgrade to 2024.1.6

[pblohrndz]

Same Issue.

Core 2024.1.6 Supervisor 2023.12.1 Operating System 11.4 Frontend 20240104.0

AdguardHome: v0.107.43

[N3rdix]

Logs? No one? Without any input it might be hard for the devs to judge

[Gunth]

I've enabled the debug mode but didn't find any logs in the file after reloading the integration or restarting ...

[tescophil]

Same here, nothing in the logs after enabling debug logging and reloading the integration. Rolled back to 2024.1.5 and it functions perfectly.

[Vansmak]

Mine are persisting after removing. rebooting, re-adding. Try unchecking verify ssl.

[mjpiratex]

Also experienced similar as reported. Experienced error after update. Attempted adding a second copy, it's prompting for user/password in the current prompt- something I didn't set or setup. Unable to add second copy. Attempted to remove, reboot,and readd integration, failed to initialize, tried to add another copy- it also failed second screenshot. Diagnostics button for that seems absent now.

[Dio55]

Problem still exist with Adguard Home 5.03 and Home Assistant Core 2024.2.0

[miguel-rodrigues-kenbi]

Disabling HTTPS on the add-on and restarting it resolved the problem for me.

[mjpiratex]

Disabling HTTPS on the add-on and restarting it resolved the problem for me.

Did you re-enable the SSL after this step? It worked with SSL enabled previously.

[Dio55]

Disabling HTTPS solves the problem, but it introduces a new problem: DNS via https and tls will not work anymore. Re-enabling HTTPS again introduces the original problem.

[mjpiratex]

Disabling HTTPS solves the problem, but it introduces a new problem: DNS via https and tls will not work anymore. Re-enabling HTTPS again introduces the original problem.

What else can we do to help resolve this issue?

[Dio55]

To solve the problem, I have disabled the Adguard setting to redirect to HTTPS automatically. Until now I have noticed no negative side effects.

[tescophil]

Any movement on this, same problem persists in the latest version 2024.2.3, the 'fix' to turn of auto redirect to HTTPS does not work in my case. Enabling debug logging results in nothing showing up in the logs.

[Vansmak]

For what it's worth I have 2 instances outside if ha addons that are connecting. Non ssl

[SamJongenelen]

Disabling auto redirect worked for me. Did a reboot too (HAOS)

[chdefrene]

For me, the trick was to disable the Verify SSL certificate option when setting up the integration. Makes sense, since I'm using a self signed certificate. With this option off, the service works even when "Redirect to HTTPS automatically" is turned on in the Adguard settings.

[tescophil]

I'm not using a self signed cert, still doesn't work...

Deleted, reinstalled without the "Check SSL cert: option and it now works, but is still fundamentally broken...

[zipzagster]

I can't install the integration, even disabling SSL. Do I leave username and password blank?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mjpiratex]

This is still in the same state as my last comment. Still not working.