hassio-addons / addon-adguard-home

AdGuard Home - Home Assistant Community Add-ons
https://addons.community
MIT License
401 stars 49 forks source link

Adguard UI does not load but everything works #289

Closed yevon closed 2 years ago

yevon commented 2 years ago

Problem/Motivation

The Adguard UI does not load from some time ago, it just shows home assistant again repeated like this:

image

I have set up manual ip and dns as stated but nothing changes, saving configs reloading etc. Any ideas what could it be or what can I check? Any other addon is working properly.

frenck commented 2 years ago

This sounds like a very very old issue.

Can you provide the output of ha info? And which version of the add-on are you running?

yevon commented 2 years ago

I'm running latest version of the plugin, 4.4.2.

I tried disabling and enabling ssl but it doesn't work anyway. I'm behind a reverse proxy with nginx that provides the ssl. Just for verifying the issue, I accessed to home assistant directly by ip-address without the reverse proxy and without ssl and the nginx ingress shows a "Not found":

image

With ha info what do you mean, ha logs? hardware? supervisor?

The plugin logs are:

`----------------------------------------------------------- Add-on: AdGuard Home Network-wide ads & trackers blocking DNS server

Add-on version: 4.4.2 You are running the latest version of this add-on. System: Ubuntu 21.10 (amd64 / qemux86-64) Home Assistant Core: 2021.12.7 Home Assistant Supervisor: 2021.12.2

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... Log level is set to INFO [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... [23:13:08] 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. [23:13:09] INFO: Starting AdGuard Home server... 2022/01/04 23:13:09.171226 [info] AdGuard Home, version v0.107.2 2022/01/04 23:13:09.174124 [info] dhcp: loaded leases v4:119 v6:0 total-read:119 from DB 2022/01/04 23:13:09.180740 [info] Initializing auth module: /data/adguard/data/sessions.db 2022/01/04 23:13:09.180977 [info] auth: initialized. users:0 sessions:0 2022/01/04 23:13:09.181411 [info] number of certs - 3 2022/01/04 23:13:09.181425 [info] got an intermediate cert 2022/01/04 23:13:09.181446 [info] got an intermediate cert 2022/01/04 23:13:09.252461 [info] Initialize web module 2022/01/04 23:13:09.269823 [info] dhcpv4: listening [dhcpv4] 2022/01/04 23:13:09 Server listening on 0.0.0.0:67 [dhcpv4] 2022/01/04 23:13:09 Ready to handle requests 2022/01/04 23:13:09.270099 [info] AdGuard Home is available at the following addresses: 2022/01/04 23:13:09.270156 [info] Go to http://127.0.0.1:45158 2022/01/04 23:13:09.270169 [info] Go to https://127.0.0.1:443 2022/01/04 23:13:09.478946 [info] Starting the DNS proxy server 2022/01/04 23:13:09.478977 [info] The server is configured to refuse ANY requests 2022/01/04 23:13:09.478990 [info] DNS cache is enabled 2022/01/04 23:13:09.479002 [info] MaxGoroutines is set to 50 2022/01/04 23:13:09.479012 [info] Fastest IP is enabled 2022/01/04 23:13:09.479024 [info] Creating the UDP server socket 2022/01/04 23:13:09.479132 [info] Listening to udp://192.168.1.130:53 2022/01/04 23:13:09.479145 [info] Creating the UDP server socket 2022/01/04 23:13:09.479171 [info] Listening to udp://172.30.32.1:53 2022/01/04 23:13:09.479181 [info] Creating a TCP server socket 2022/01/04 23:13:09.479214 [info] Listening to tcp://192.168.1.130:53 2022/01/04 23:13:09.479229 [info] Creating a TCP server socket 2022/01/04 23:13:09.479256 [info] Listening to tcp://172.30.32.1:53 2022/01/04 23:13:09.479260 [info] Creating a TLS server socket 2022/01/04 23:13:09.479286 [info] Listening to tls://192.168.1.130:853 2022/01/04 23:13:09.479298 [info] Creating a TLS server socket 2022/01/04 23:13:09.479321 [info] Listening to tls://172.30.32.1:853 2022/01/04 23:13:09.479328 [info] Creating a QUIC listener 2022/01/04 23:13:09.479384 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2022/01/04 23:13:09.479499 [info] Listening to quic://192.168.1.130:784 2022/01/04 23:13:09.479514 [info] Creating a QUIC listener 2022/01/04 23:13:09.479590 [info] Listening to quic://172.30.32.1:784 2022/01/04 23:13:09.479650 [info] Entering the tcp listener loop on 192.168.1.130:53 2022/01/04 23:13:09.479852 [info] Entering the UDP listener loop on 192.168.1.130:53 2022/01/04 23:13:09.479975 [info] Entering the UDP listener loop on 172.30.32.1:53 2022/01/04 23:13:09.480175 [info] Entering the DNS-over-QUIC listener loop on 192.168.1.130:784 2022/01/04 23:13:09.480276 [info] Entering the tcp listener loop on 172.30.32.1:53 2022/01/04 23:13:09.480319 [info] Entering the tls listener loop on 192.168.1.130:853 2022/01/04 23:13:09.480341 [info] Entering the tls listener loop on 172.30.32.1:853 2022/01/04 23:13:09.480410 [info] Entering the DNS-over-QUIC listener loop on 172.30.32.1:784 2022/01/04 23:13:09.647685 [error] os.Chtimes(): chtimes /data/adguard/data/filters/2.txt: no such file or directory 2022/01/04 23:13:09.647719 [info] Failed to update filter https://github.com/AdAway/adaway.github.io/blob/master/hosts.txt: data is HTML, not plain text [23:13:09] INFO: Starting NGinx...`

Thanks!

frenck commented 2 years ago

Ubuntu 21.10

Your are running a system that is not supported by the Home Assistant project.

cannondale0815 commented 2 years ago

@yevon I have a similar set up and ran into the same problem. You need to open up the Ingress port for AdGuard in the Ubuntu firewall configuration. You can find the Ingress port by opening the "ingress.json" file in the hassio root folder (the folder that contains your "homeassistant" folder). Note down that port, then configure the Ubuntu firewall to "ALLOW IN Anywhere" for that port (I am using "gufw" for all my firewall configurations, as that is super easy).

That solved this issue for me, and any other add-ons that have the same issue.

Hope this helps.

yevon commented 2 years ago

@yevon I have a similar set up and ran into the same problem. You need to open up the Ingress port for AdGuard in the Ubuntu firewall configuration. You can find the Ingress port by opening the "ingress.json" file in the hassio root folder (the folder that contains your "homeassistant" folder). Note down that port, then configure the Ubuntu firewall to "ALLOW IN Anywhere" for that port (I am using "gufw" for all my firewall configurations, as that is super easy).

That solved this issue for me, and any other add-ons that have the same issue.

Hope this helps.

Thanks, but I think that it was another issue. I just deleted it completely, installed again and it started working again. I had to apply manually all the config but is working nicely.

LordNex commented 2 years ago

Checkout NextDNS. I have AdGuard in my HA for initial screening and local dns rewrites. It then forwards to a Firewalla gold which does IPS/IDS among other things. It then forwards those requests through DoH to NextDNS and it has waaay more list and granular config. I’m now blocking over 80% of all traffic going in or out of my network with no ads or tracking

On Jan 20, 2022, at 7:41 AM, Gabriel @.***> wrote:



@yevonhttps://github.com/yevon I have a similar set up and ran into the same problem. You need to open up the Ingress port for AdGuard in the Ubuntu firewall configuration. You can find the Ingress port by opening the "ingress.json" file in the hassio root folder (the folder that contains your "homeassistant" folder). Note down that port, then configure the Ubuntu firewall to "ALLOW IN Anywhere" for that port (I am using "gufw" for all my firewall configurations, as that is super easy).

That solved this issue for me, and any other add-ons that have the same issue.

Hope this helps.

Thanks, but I think that it was another issue. I just deleted it completely, installed again and it started working again. I had to apply manually all the config but is working nicely.

— Reply to this email directly, view it on GitHubhttps://github.com/hassio-addons/addon-adguard-home/issues/289#issuecomment-1017515876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGXNJA6FHEG476VZVDW743UXAGKJANCNFSM5LGCMZ4A. You are receiving this because you are subscribed to this thread.Message ID: @.***>

yevon commented 2 years ago

Checkout NextDNS. I have AdGuard in my HA for initial screening and local dns rewrites. It then forwards to a Firewalla gold which does IPS/IDS among other things. It then forwards those requests through DoH to NextDNS and it has waaay more list and granular config. I’m now blocking over 80% of all traffic going in or out of my network with no ads or tracking On Jan 20, 2022, at 7:41 AM, Gabriel @.> wrote:  @yevonhttps://github.com/yevon I have a similar set up and ran into the same problem. You need to open up the Ingress port for AdGuard in the Ubuntu firewall configuration. You can find the Ingress port by opening the "ingress.json" file in the hassio root folder (the folder that contains your "homeassistant" folder). Note down that port, then configure the Ubuntu firewall to "ALLOW IN Anywhere" for that port (I am using "gufw" for all my firewall configurations, as that is super easy). That solved this issue for me, and any other add-ons that have the same issue. Hope this helps. Thanks, but I think that it was another issue. I just deleted it completely, installed again and it started working again. I had to apply manually all the config but is working nicely. — Reply to this email directly, view it on GitHub<#289 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGXNJA6FHEG476VZVDW743UXAGKJANCNFSM5LGCMZ4A. You are receiving this because you are subscribed to this thread.Message ID: @.>

I will have a look at those solutions I didn't know about them, thanks for the advice!