Sorry if this has been asked before, but is there any way to parse the query log for a certian IP and domain? I’d like to get notifications if a certain domain is accessed by certain IP’s.
Is there a physical query log I can parse manually? Running the addon on HASSOS on a RPi4.
I had to install using the terminal&ssh addon and it fixed that.
can you write a setup guide for this method?
I used this.
Hello,
I see no option to use a service to bock/deblock services for a client. the only way seems to be through the settings but i have two child-users that i would like to be able to bleck/deblock with an automation.
Anyone else found a way to do this or do I need to drop a feature request?
Thank you!
Just to say also had the 127.0.0.1 error and, as others have noted, simply ‘saving’ the network tab and restarting the add-on fixed that. I’m thinking I should probably have posted this question here!
If anyone has any clue, I’m all ears!
thanks
Hi ,
My ADguard works correctly only for few hours, after that, I can connect anymore to the internet and I have to restore the DNS setting in my Fritzbox router to default . Then I can restore the ADguard DNS and it work another time for few hours:
I don’t need to restart home assistant or router or ADguard, I have only to change DNS on the router on default for a while and then switch it back to ad guard
My ad guard log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: AdGuard Home
Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
Add-on version: 4.1.9
You are running the latest version of this add-on.
System: Home Assistant OS 6.5 (amd64 / qemux86-64)
Home Assistant Core: 2021.10.6
Home Assistant Supervisor: 2021.10.6
-----------------------------------------------------------
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...
[19:00:26] 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.
[19:00:27] INFO: Starting AdGuard Home server...
2021/10/31 19:00:28.255741 [info] AdGuard Home, version v0.106.3
2021/10/31 19:00:28.272717 [info] Initializing auth module: /data/adguard/data/sessions.db
2021/10/31 19:00:28.277545 [info] auth: initialized. users:0 sessions:0
2021/10/31 19:00:28.277573 [info] Initialize web module
2021/10/31 19:00:28.333718 [info] Go to http://127.0.0.1:45158
[19:00:28] INFO: Starting NGinx...
2021/10/31 19:00:28.898401 [info] Starting the DNS proxy server
2021/10/31 19:00:28.898662 [info] Ratelimit is enabled and set to 20 rps
2021/10/31 19:00:28.898790 [info] The server is configured to refuse ANY requests
2021/10/31 19:00:28.898895 [info] DNS cache is enabled
2021/10/31 19:00:28.899082 [info] MaxGoroutines is set to 300
2021/10/31 19:00:28.899273 [info] Creating the UDP server socket
2021/10/31 19:00:28.899593 [info] Listening to udp://192.168.0.62:53
2021/10/31 19:00:28.899767 [info] Creating the UDP server socket
2021/10/31 19:00:28.900117 [info] Listening to udp://172.30.32.1:53
2021/10/31 19:00:28.900266 [info] Creating a TCP server socket
2021/10/31 19:00:28.900542 [info] Listening to tcp://192.168.0.62:53
2021/10/31 19:00:28.900717 [info] Creating a TCP server socket
2021/10/31 19:00:28.900892 [info] Listening to tcp://172.30.32.1:53
2021/10/31 19:00:28.902107 [info] Entering the tcp listener loop on 172.30.32.1:53
2021/10/31 19:00:28.920047 [info] Entering the UDP listener loop on 172.30.32.1:53
2021/10/31 19:00:28.920512 [info] Entering the UDP listener loop on 192.168.0.62:53
2021/10/31 19:00:28.920641 [info] Entering the tcp listener loop on 192.168.0.62:53
2021/11/01 12:00:29.292321 [info] Filter 1 has been updated: 799994 bytes, 41429 rules
2021/11/01 12:00:29.292359 [info] Saving filter 1 contents to: /data/adguard/data/filters/1.txt
2021/11/01 12:00:29.967770 [info] Updated filter #1. Rules: 41375 -> 41429
2021/11/02 12:00:30.723647 [info] Filter 1 has been updated: 801671 bytes, 41516 rules
2021/11/02 12:00:30.725036 [info] Saving filter 1 contents to: /data/adguard/data/filters/1.txt
2021/11/02 12:00:31.355726 [info] Updated filter #1. Rules: 41429 -> 41516
2021/11/03 12:00:32.664937 [info] Filter 1 has been updated: 802814 bytes, 41565 rules
2021/11/03 12:00:32.664966 [info] Saving filter 1 contents to: /data/adguard/data/filters/1.txt
2021/11/03 12:00:33.469118 [info] Updated filter #1. Rules: 41516 -> 41565
2021/11/04 12:00:34.485901 [info] Filter 1 has been updated: 803596 bytes, 41608 rules
2021/11/04 12:00:34.486035 [info] Saving filter 1 contents to: /data/adguard/data/filters/1.txt
2021/11/04 12:00:34.631513 [info] Filter 2 has been updated: 303290 bytes, 8124 rules
2021/11/04 12:00:34.631586 [info] Saving filter 2 contents to: /data/adguard/data/filters/2.txt
2021/11/04 12:00:35.196239 [info] Updated filter #1. Rules: 41565 -> 41608
2021/11/04 12:00:35.196269 [info] Updated filter #2. Rules: 8125 -> 8124
I would LOVE a feature like this too. I need to block social media services for specific clients using an automation.
Anyone have ideas?
I’m looking for the exact same thing, i dont want to block a domain/ip but rather just setup an automation to do what I want it to do when a certain IP (or anyone) tries to lookup a specific domain.
Currently running PiHole in a container but the lack of sensors and integration with HA i would see no reason to stay with PiHole if AdGuard can provide this feature.
Currently i’ve just research PiHole a bit and they have a API that you can call to get a query-log for certain client IPs or just plain search the log file your self, there should be a similar feature in AdGuard but havn’t actually checked if there is.
I would be happy to add this feature to one of the integration if needed, just need to do some more research since i dont want to put XX hours into a integration to then just switch to another one.
Does anyone know if this feature actually already exists in AdGuard or if there is a API that the integration could use to add this feature?
Hi, Everyone,
Maybe this question already went around, but I could not find anything related, aside from an issue posted on the AdGuard Addon Github, which was “dismissed” because the question was related to the integration.
I am using AdGuard Home as a DHCP server. Does anyone know if there’s a way to get a sensor with the number of DHCP leases (total and static)?
Cheers,
a Bit of an unusual one. I am using a SIP card to answer my door station. It uses web sockets. When I turn on AdGuard is seems to be blocking the Websocket connections to wss://xxx.duckdns.org/ws. I am using NGINX to resolve the Duckdns.
Any suggestions?
Is there a way to use individual messages (server not found) if AdGuard blocks a website?
hi all - i am looking for a way to automate blocked services (youtube, etc.) at certain times. is there a way to automate this?
Hello,
I have install AdGuardHome add-on on a Supervised HomeAssistant.
I have a lot of messages in 3 logs files on the Host :
==> /var/log/messages <==
Dec 18 11:13:42 home 15592d4c1975[637]: [INFO] 172.30.32.1:54466 - 47603 "PTR IN 202.1.168.192.in-addr.arpa. udp 55 true 2048" NXDOMAIN qr,rd,ra 44 1.612000334s
==> /var/log/syslog <==
Dec 18 11:13:42 home 15592d4c1975[637]: [INFO] 172.30.32.1:51736 - 48363 "PTR IN 107.1.168.192.in-addr.arpa. udp 55 true 2048" NXDOMAIN qr,rd,ra 44 1.632304071s
==> /var/log/user.log <==
Dec 18 11:13:42 home 15592d4c1975[637]: [INFO] 172.30.32.1:51736 - 48363 "PTR IN 107.1.168.192.in-addr.arpa. udp 55 true 2048" NXDOMAIN qr,rd,ra 44 1.632304071s
==> /var/log/messages <==
Dec 18 11:13:42 home 15592d4c1975[637]: [INFO] 172.30.32.1:51736 - 48363 "PTR IN 107.1.168.192.in-addr.arpa. udp 55 true 2048" NXDOMAIN qr,rd,ra 44 1.632304071s
Is there a way to disable this ? Many Thanks
PS: I have set log to warning in the AddOn config, but there is no change.
how do i create an automation that warns if a certain url is opened?
Am I the only one having that issue with AdGuard, where it takes for ever to get a response after I connect to WiFi?
I’ve a NUC with AdGuard Addon and came across this issue: Whenever I open my macbook, it takes pretty long to resolve names, when using AdGuard. I’ve also dnsmasq on the same NUC and when I use dnsmasq, there are no such issues.
Secondly I have to restart AdGuard automatically once every few days as it stops resolving names.
So basically, my router runs as DHCP and gives the IP of my HASS device as DNS. With dnsmasq thats not an issue. But when I run AdGuard instead (same port 53) it sometimes takes for ever.
There are no strange looking logs.
I’m trying to get the Adguard Home Integration connected to the Adguard Home Add-on. However, the automatic discovery (read this in some release notes above) does not seem to work and adguard is not shown as “Discovered” integration (have I missed enabeling it somewhere?). I’m greeted with the credentials screen when I add the integration manually:
However, here I’m puzzled what to enter. Can anyone help?
SOLVED
see Home Assistant Community Add-on: AdGuard Home - #663 by pigeldi gives the answer. Thanks @pigeldi
This thread is for the community addon and not the integration.
For the integration to work you’ll need a dedicated installation of AdGuard Home.
Are you sure? I use the Adguard Home Add-on and the integration was automatically discovered for me…
At least that’s how I understand it.
