How to Self-Host AdGuard Home 2026

TL;DR

AdGuard Home (GPL 3.0, ~24K GitHub stars, Go) is a network-wide DNS ad and tracker blocker — every device on your network (phone, TV, smart home) gets ads blocked without installing anything per-device. Compare AdGuard Home vs Pi-hole: AdGuard Home has a better UI, built-in DNS-over-HTTPS/TLS, per-client rules, and parental controls; Pi-hole has a larger community and more integrations. Both work. AdGuard Home wins for new installs in 2026.

Key Takeaways

AdGuard Home: GPL 3.0, ~24K stars — network-wide DNS blocker, better than Pi-hole UI
DNS-over-HTTPS/TLS: Built-in encrypted DNS server (no need for external dnscrypt-proxy)
Per-device rules: Allow YouTube on the TV but block it everywhere else
Parental controls: Block adult content or specific categories by device
DHCP server: Can replace your router's DHCP (assigns DNS automatically)
Statistics: Detailed query logs, blocked per domain, per client

AdGuard Home vs Pi-hole

Feature	AdGuard Home	Pi-hole
License	GPL 3.0	EUPL 1.2
GitHub Stars	~24K	~48K
Language	Go	PHP + Python
UI	Modern, polished	Functional
DNS-over-HTTPS	Built-in	Via dnscrypt-proxy
DNS-over-TLS	Built-in	Via Unbound
Per-client rules	Yes	Limited (groups)
Parental controls	Yes	Via external lists
DHCP server	Yes	Yes
Regex blocking	Yes	Yes
RAM	~30MB	~150MB
Raspberry Pi	Yes	Yes (default)

Part 1: Docker Setup

# docker-compose.yml
services:
  adguardhome:
    image: adguard/adguardhome:latest
    container_name: adguardhome
    restart: unless-stopped
    network_mode: host    # Required for DNS (port 53)
    volumes:
      - adguard_work:/opt/adguardhome/work
      - adguard_conf:/opt/adguardhome/conf
    # network_mode: host means ports aren't mapped here

volumes:
  adguard_work:
  adguard_conf:

docker compose up -d

Visit http://your-server:3000 → setup wizard.

Without Host Networking (if port 53 is taken)

services:
  adguardhome:
    image: adguard/adguardhome:latest
    restart: unless-stopped
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "3000:3000/tcp"    # Admin UI
      - "80:80/tcp"        # HTTP
      - "443:443/tcp"      # HTTPS
      - "853:853/tcp"      # DNS-over-TLS
    volumes:
      - adguard_work:/opt/adguardhome/work
      - adguard_conf:/opt/adguardhome/conf

If port 53 is in use (systemd-resolved on Ubuntu):

# Disable systemd-resolved's DNS stub:
sudo sed -i 's/#DNSStubListener=yes/DNSStubListener=no/' /etc/systemd/resolved.conf
sudo systemctl restart systemd-resolved

Part 2: HTTPS Web UI with Caddy

adguard.yourdomain.com {
    reverse_proxy localhost:3000
}

Part 3: Setup Wizard

Visit http://your-server:3000
Set admin username and password
Set listen interfaces
Finish setup

Then visit http://your-server:3000/install or the main dashboard.

Part 4: Point Your Network at AdGuard Home

Option A: Router DNS (Entire Network)

Log into your router → DHCP settings → Set DNS server to your AdGuard Home IP:

DNS Server 1: 192.168.1.X   (your server's LAN IP)
DNS Server 2: 1.1.1.1       (Cloudflare as fallback)

Every device that uses DHCP now uses AdGuard Home for DNS.

Option B: Per-Device DNS

Configure specific devices to use your server's IP as DNS:

# macOS:
# System Preferences → Network → Advanced → DNS → add your server IP

# iPhone:
# Settings → Wi-Fi → [Network] → Configure DNS → Manual → add IP

# Linux:
# /etc/resolv.conf or systemd-resolved configuration

Option C: AdGuard Home as DHCP Server

Replace your router's DHCP with AdGuard Home:

Settings → DHCP → Enable DHCP server
Set IP range, gateway, DNS (itself: 192.168.1.X)
Disable DHCP on your router

Every device auto-receives AdGuard Home as DNS.

Part 5: Blocklists

Settings → Filters → Blocklists → Add Blocklist

Recommended lists:

AdGuard DNS filter (built-in — good default)
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts   # Steven Black's combined list
https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/pro.txt  # HaGeZi Pro
https://adaway.org/hosts.txt                                         # Mobile ads
https://raw.githubusercontent.com/DandelionSprout/adfilt/master/GameConsoleAdblockList.txt  # Gaming

After adding lists: Settings → Filters → Update Now

Custom block rules:

# /etc/adguardhome/conf/AdGuardHome.yaml
# Or in the UI: Filters → Custom Filtering Rules

# Block a domain:
||analytics.example.com^

# Allow a domain (override blocklist):
@@||youtube.com^$important

# Block all subdomains:
||*.ads.example.com^

# Regex block:
/tracking|analytics|telemetry/

Part 6: DNS-over-HTTPS (DoH)

Enable encrypted DNS for privacy:

Settings → Encryption → Enable HTTPS / DNS-over-HTTPS
Add your domain certificate (or let AdGuard use Let's Encrypt)
DoH URL: https://adguard.yourdomain.com/dns-query

Configure on clients:

iOS 14+: Settings → Wi-Fi → DNS → DNS-over-HTTPS
Firefox: Network Settings → Enable DNS-over-HTTPS → Custom → your URL
macOS: .mobileconfig profile installation

Or use DNS-over-TLS on port 853: adguard.yourdomain.com:853

Part 7: Per-Client Rules

Set different rules for different devices:

Client Settings → + Add Client
Identify by: MAC address, IP, or client name (from DHCP)
Per-client settings:
- Use custom upstreams: Point to a different DNS resolver
- Safe search: Force safe search on Google/YouTube
- Parental control: Block adult content categories
- Custom filter rules: Allow/block specific domains only for this device

Example setup:

TV (192.168.1.10): Block social media, allow streaming services
Kids' iPad (MAC: AA:BB:CC:DD:EE:FF): Parental control: on, safe search: on
Work laptop: No restrictions

Part 8: Query Log and Statistics

Dashboard → Statistics:

Total DNS queries per day
% blocked
Top blocked domains
Top clients by query count
Top queried domains

Query Log → Filter by client, status, domain:

# Find what a specific device is querying:
Filter: client = 192.168.1.15

# Find all blocked queries:
Filter: status = blocked

# Find if a domain was blocked or allowed:
Filter: domain = analytics.google.com

Maintenance

# Update AdGuard Home:
docker compose pull
docker compose up -d

# Logs:
docker compose logs -f adguardhome

# Backup config:
tar -czf adguard-config-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect adguardhome_adguard_conf --format '{{.Mountpoint}}')

# Update blocklists:
# Filters → Update Now (or set auto-update schedule)

# Check DNS resolution:
dig @192.168.1.X ads.google.com    # Should return 0.0.0.0
dig @192.168.1.X google.com         # Should return real IP

Why Self-Host AdGuard Home?

The case for self-hosting AdGuard Home comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting AdGuard Home means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying AdGuard Home, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives AdGuard Home headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent AdGuard Home data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running AdGuard Home without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing AdGuard Home's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your AdGuard Home backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for AdGuard Home's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose AdGuard Home's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep AdGuard Home's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to AdGuard Home's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f adguard-home

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change AdGuard Home's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats adguard-home. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping AdGuard Home Updated

AdGuard Home follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm AdGuard Home is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source privacy and networking tools at OSSAlt.com/categories/privacy.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)