I’m sorry in advance if my question is stupid but I’m trying to setup DoH, but Home Assistant OS (Raspberry Pi 4) is already using #443 for Nginx Proxy Manager.
Nginx Proxy manager add-on is running at 172.30.33.7 according to AdGuard is AdGuard have a docker IP and if so where can I find it ? (or is just shared with HAOS Host?)
How can I setup DoH ? – worst case I could use DoT as it won’t required 443 but It’s don’t seems to be an option (it’s either DoH by it self or DoH + DoT but not DoT only?)
also, in Encryption settings when I copy/past my CloudFlare certificate (which work just fine with Nginx) I have a error: * Certificate chain is invalid
in the add-on option I setup the certificate like this which should be valid :
ssl
certfile: origin.pem
keyfile : privkey.pem
UPDATE:
I fixed the 443 issue but I still have a certificat issue
I wonder if anyone can help with a weirdness since I just updated AdGuard Home a day or so back. I did the AGH update via the web based UI. Since then whenever I restart HA the integration picks up two AdGuard services - one with current firmware and one with old firmware. Weirdly, neither service can generate data for their sensors.
Once I delete the integration and reinstall it all is well again - one service and functioning sensors.
it’s only a couple of minutes of hassle to set it up again but I’m hoping someone can help me resolve it.
The addon suddenly stops working after a short while for my whole network (via router). Does anyone know how I can fix this? It works at the beginning without problems and then after a 30-60mins I can’t connect to any websites anymore.
I had the same problem the problem is that the upstream DNS is not reacting anymore.
Solution: see the DNS settings within AGH, change the dns upstream server. Replace temporary the https dns server with Google dns or any other dns server.
This is so weird. Setting it to Google DNS works without issues.
But setting them to my dns servers afterwards bugs out after a while again until I tell my router to use its own dns servers again and then go back to adguard home dns again. So for now I can only use Google DNS inside Adguard Home.
Are there special instructions for installing this on Home Assistant Operating System on Raspberry PI?
I have the following configuration:
Core: 2021.5.2
Supervisor: 2021.04.3
OS: Home Assistant OS 5.13
On attempting to install this using Configuration → Integrations → Add Integration, I’m greeted with a screen requesting credentials. In the past when I installed this addon inside of hassio running on top of raspbian via docker, it was simple. However, now that I’m running Home Assistant OS, i’m stuck.
I tried to install the Adguard binaries after using the Terminal & SSH Add-on to connect to the raspberrypi. Once installed and running, it says that the service is available at 127.0.0.1:3000, along with an IP address that looks like it relates to docker (172.30.xxx.xxx). When running ifconfig in the terminal, I see the ethernet interface along with localhost. However, I use wifi to connect the raspberrypi to the network. Any suggestions on how to proceed?
Hi! Actually, the integration is used to connect a pre-existing adguard home installation to HA. You need first to install the addon by going in Supervisor → Store → Search Adguard Home.
Once adguard home is installed, you simply start it then click on “open webui” and follow instructions.
Installing and running it from “Terminal & SSH addon” won’t work as it will install it within this container. Honestly, Home Assistant OS is very simple to use, it’s plug & play. Anything more than plug & play is actually rather complex as the OS can’t be easily accessed and is anyway mostly read only.
I loose internet connection whenever I use my Home Assistant IP address as a preferred DNS server in my Asus AC86U settings. This only recently started happening. Is this the same issue you are describing? If so should I change the address below to 8.8.8.8
Hello there, recently I have an setup to take this AdGuard Home add-on one (tiny) step further - along with pixelserv.
The problem: with the adguard in place, from time to time you would see this gibberish when you browse an website. Here’s an example when I use Google News:
While it’s fine and harmless as is, wouldn’t it be great to get rid of those?
The process
So I searched around, and realized that there is a project called pixelserv-tls out there.
And, then, there’s even a docker for this with the image size at just 7.6MB!! And even better for my HAOS-VM-inside-a-linux-box-with-intel-CPU setup, the docker is compatible to my setup. https://hub.docker.com/r/imthai/pixelserv-tls
So the solution:
I use the portainer add-on, which is also by frenck, pull the docker image, setup the ports, and deploy!
Check the docker. If it is working you should see a blank page.
Change the AdGuard DNS settings and point it to the ip of HAOS, using the “Custom IP” option.
Done!
So most of the time is for me to read read read trying to know what need to be done. The time to actually implement this? It took me like 5 minutes only, and now the gibberish is gone!
Anyways, just want to share. I was lucky that my first attempt was a successful one.
I upgraded from version 4.1.0 to 4.1.2 and now AdGuard doesn’t start. It was working fine before the update.
I am running the latest version of HA on a Rpi4. Below is the log, it crashes and starts over and over again.
[23:15:52] INFO: Starting AdGuard Home server...
2021/05/19 23:15:52.266323 [info] AdGuard Home, version v0.106.3
2021/05/19 23:15:52.279794 [info] Initializing auth module: /data/adguard/data/sessions.db
2021/05/19 23:15:52.280101 [info] auth: initialized. users:0 sessions:0
2021/05/19 23:15:52.280125 [info] Initialize web module
2021/05/19 23:15:52.321811 [info] Go to http://127.0.0.1:45158
2021/05/19 23:15:52.791422 [info] Starting the DNS proxy server
2021/05/19 23:15:52.791465 [info] Ratelimit is enabled and set to 20 rps
2021/05/19 23:15:52.791475 [info] The server is configured to refuse ANY requests
2021/05/19 23:15:52.791483 [info] DNS cache is enabled
2021/05/19 23:15:52.791494 [info] MaxGoroutines is set to 300
2021/05/19 23:15:52.791514 [info] Creating the UDP server socket
2021/05/19 23:15:52.791813 [info] Listening to udp://192.168.XX.XX:53
2021/05/19 23:15:52.791832 [info] Creating the UDP server socket
2021/05/19 23:15:52.801369 [fatal] couldn't start forwarding DNS server: couldn't listen to UDP socket, cause: listen udp [fe80::c009:c97f:37a3:94eb]:53: bind: invalid argument
Same issue for me. Fortunately I saw this post and took a snapshot so I am back on 4.0.0. Is it possible to just upgrade to 4.1.0. I haven’t done that before?
Sames. Mine was at 4.0.0 and upgraded to 4.1.2. In my case it starts fine, but will not resolve and DNS requests. Had to roll-back to 4.0.0 and all is working again.
Same here. Why do never learn to uncheck the auto update!
[fatal] couldn’t start forwarding DNS server: couldn’t listen to UDP socket, cause: listen udp [fe80::b4c3:7b6a:39d1:1017]:53: bind: invalid argument
Seems the Github Issue got closed soon after it was created. I am getting the same problem. So I uninstalled it and reinstalled it and now I’m getting a different line causing an error:
