Adguard 2.2.3 (661)
Elis Riebow
The standard AdGuard DNS servers "only" provide standard filtering. You can't configure the filters/blocklists/whitelists/web services (Facebook, WhatsApp, Amazon, ...) that are to be blocked. Furthermore you have to use an adguard server as dns server. with the home variant you can use secure dns over tls servers which do not log.
I found a nice, functional luci-app-adguardhome ( -app-adguardhome). The development appears to be in Chinese, however, the web UI itself shows in English on my device and works great for configuring many options for AdGuardHome. After you install it, you just have to change the luci-app-adguardhome to match the settings that you have for AdGuardHome (binary locations, work dir, port, etc.) and it will recognize everything from that point and you can make changes as needed.
luci-app-adguardhome:
I had mentioned this in my most recent post. I used it briefly but have since removed it. It is quite complex but I prefer simplicity myself. Anyway, it used an init.d script to facilitate in being able to change the work-dir, bin path, config path, etc. Much of these can be changed with command line arguments anyway. It can also compress the AdGuardHome binary as well. So while it is quite neat and comprehensive, I prefer to do many things manually myself and keep things simple.
For all has problem how to remover adguard or to continue in ads or you want to delete adguard first you need to go activity monitor>search for adguard>quir or press the x sign in upper leftside then thats it you can continue in the site you want to go and you can delete the app now. thank me later your friendly neighborhood wenskie
Recently, I decided to revisit AdGuard Home. I have been trying more and more to put my self-host workloads on my Kubernetes cluster. When you search for \u201Chow to run adguard home on Kubernetes\u201D some old and not so helpful articles pop up. I decided it was time for me to dive deep and figure out how I could get this running on my cluster.
I had a few years Nextcloud and Piholr running on the same raspberry pi. So far no issue you just have to give the adguard/pihole webUi another port. Did this via docker which makes it easy to give the container different ports
If you have configured TLS on LuCI, there's no need to use TLS on AdGuard Home. Set allow_unencrypted_doh to false in adguardhome.yaml to allow AdGuard Home respond to DoH requests without TLS encryption.
I found out what the issue was: applying the various YAMLs for the first time spin up the pod/stack - this creates an AdGuardHome.yaml file using the template/params from the adguard-config.yml. Applying changes using the web UI and successively doing a cat /path/to/AdGuardHome.yaml, you can see that the file's content changes (i.e. changes in the web UI get written to that file). I found out that ConfigMaps are generally immutable in k8s unless you set up an automatic reloading mechanism, which basically means that each time you reboot your system, destroy/re-deploy the pod, the original ConfigMap gets applied.
As a minor addendum: I think that a viable workaround would be to add an initContainer which checks if the file already exists in the given path; if it doesn't, create it applying the contents of the adguard-config.yml.
thanks for this useful and detailed guide, I have a problem in updating adguard, it does not update when there is a new version. I remember before we were be able to click "update" and get it updated, now you can only see the message "AdGuard Home v0.107.4 is now available! Click here for more info." and that is it. any idea ?
btw I'm using v0.107.3 thanks
Verify your download Run this command in your terminal in the directory the iso was downloaded to verify the SHA256 checksum:
echo "e6ce0e3485c8916ab3c1f820643fb1a69efc50380e72bbdc4f481a162b2eccf8 *adguard-home-core18-pi.img.xz" shasum -a 256 --check
You should get the following output:
-core/appliances/adguard-home-core18-pi.img.xz: OK
Or follow this tutorial to learn how to verify downloads
Go to File Station and open the docker folder. Inside the docker folder, create one new folder and name it adguard. Follow the instructions in the image below.
Note: Be careful to enter only lowercase, not uppercase letters.
Now create two new folders inside the adguard folder that you created at STEP 3 name them config and data. Follow the instructions in the image below.
Note: Be careful to enter only lowercase, not uppercase letters.