profile
viewpoint

Ask questionswith AdGuard no Access to Homeassistant

Problem/Motivation

after switching the DNS entry to the IP of the home assistant host, the adblocker starts working. But from now on, it is not possible to connect to the home assistant backend via DnS (DuckDNS).

Expected behavior

successful accessing the home assistant backend via IP AND DNS

Actual behavior

no access to the home assistant backend via DNS (DuckDNS). via IP address the access is still possible. Safari error message: „FetchEvent.respondWith received an error: no-response: no-response :: [{"url":"https://XYZ.duckdns.org/lovelace/default_view","error":{}}]“

Chrome error message: NET::ERR_CERT_INVALID

Is there a known issue in combination with the addon nginx proxy manager?

Steps to reproduce

see Problem/Motivation

hassio-addons/addon-adguard-home

Answer questions MartinKuhl

The Let's encrypt authority is missing. OK I did the following steps: I entered the IP-Address if the HA Server as DNS-Server (see Screenshot) and after applying the settings, it looks like the SSL certificate of my NGINX proxy manager is not accessable. You mentioned right my NPM ist setting up exact this certificate (need port 80 and 443).

I did not change the DNS entry in my router instead I change the corresonding setting in the network settings of my mac. In the DNS configuration part of adguard I only modified the Upstream-DNS-Server 8.8.8.8, 8.8.4.4., 1.1.1.1

image

useful!
source:https://uonfu.com/
Github User Rank List