Djeex/docudjeex
1
1
Fork 0
Code Issues Pull Requests Actions Projects Wiki Activity

Add Uptime-Kuma introduction, write descriptive alt text site-wide, and fix brand capitalization and filenames with spaces

Browse Source
This commit is contained in:
Djeex
2026-09-07 14:35:25 +02:00
parent eff68287f2
commit 67d593cb73
90 changed files with 380 additions and 376 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/3.serveex/9.apps/1.adguard.md
+11 -11
View File
@@ -1,5 +1,5 @@
---
title: Adguard Home
title: AdGuard Home
description: Install AdGuard Home for network-wide ad and tracker blocking with DNS-over-HTTPS, client management, and custom filtering rules.
---
@@ -10,9 +10,9 @@ description: Install AdGuard Home for network-wide ad and tracker blocking with
It works as a DNS server that redirects tracking domains to a “black hole,” preventing your devices from connecting to them.
In practice, once it's in place, all you need to do is set your devices to use Adguard as their DNS server.
In practice, once it's in place, all you need to do is set your devices to use AdGuard as their DNS server.
![adguard](/img/serveex/adguard.png)
![AdGuard](/img/serveex/adguard.png)
**Quick reminder of how DNS works:**
@@ -20,14 +20,14 @@ When you visit a site or use an app, it makes requests to various domains to loa
By default, your device uses your ISP's DNS server, which is usually configured in your router or, for mobile devices, at the carrier’s CGNAT level. You can change this in your browser settings, your device’s system settings, or even directly in your router, depending on your ISP.
Adguard will act as a middleman between your device and the upstream DNS servers. If you configure your devices to use Adguard:
AdGuard will act as a middleman between your device and the upstream DNS servers. If you configure your devices to use AdGuard:
- If the domain is not in a blocklist, Adguard queries the upstream DNS servers and returns the correct IP to your device.
- If the domain *is* in a blocklist, Adguard will block the request and return nothing, so the associated content won’t load.
- If the domain is not in a blocklist, AdGuard queries the upstream DNS servers and returns the correct IP to your device.
- If the domain *is* in a blocklist, AdGuard will block the request and return nothing, so the associated content won’t load.
This is how ads and malicious domains are blocked: Adguard blocks only the bad domains, allowing the rest of the page to load normally.
This is how ads and malicious domains are blocked: AdGuard blocks only the bad domains, allowing the rest of the page to load normally.
![Picture](/img/serveex/adguard.svg)
![Diagram of AdGuard filtering a DNS request against a blocklist](/img/serveex/adguard.svg)
## Installation
@@ -47,7 +47,7 @@ tree:
::note
We will also mount the `/srv/docker/swag/config/etc/letsencrypt` folder to access Swag's SSL certificate.
We will also mount the `/srv/docker/swag/config/etc/letsencrypt` folder to access SWAG's SSL certificate.
::
::steps{level="3"}
@@ -102,7 +102,7 @@ The setup wizard asks you to pick an admin interface port. Keep it at `3000`: th
### Done!
::
That’s it! Adguard is deployed.
That’s it! AdGuard is deployed.
## Exposing AdGuard with SWAG
To make AdGuard usable from outside your home network, you need to expose it.
@@ -363,7 +363,7 @@ To configure encryption:
- Go to _Settings_ then _Encryption_.
- Set the options as follows:
![Picture](/img/serveex/adguard-chiffrement.png)
![AdGuard Home encryption settings screen](/img/serveex/adguard-chiffrement.png)
- Below, in the _Certificates_ section, check _Use file path for certificate_
- In the input field, enter `/swag-ssl/live/mydomain.com/fullchain.pem`, replacing `mydomain.com` with your actual domain.