AdGuard Home¶

References¶

Either AdGuard Home or PiHole, but not both¶

AdGuard Home and PiHole perform similar functions. They use the same ports so you can not run both at the same time. You must choose one or the other.

Quick Start¶

When you first install AdGuard Home:

Use a web browser to connect to it using port 3001. For example:
```
http://raspberrypi.local:3001
```
Click "Getting Started".
Change the port number for the Admin Web Interface to be "8089". Leave the other settings on the page at their defaults and click "Next".
Enter a username and password and click "Next".
Click "Open Dashboard". This redirects to port 8089.
After the initial setup, you connect to AdGuard Home via port 8089:
```
http://raspberrypi.local:8089
```

About port 8089¶

Port 8089 is the default administrative user interface for AdGuard Home running under IOTstack.

Port 8089 is not active until you have completed the Quick Start procedure. You must start by connecting to port 3001.

Because of AdGuard Home limitations, you must take special precautions if you decide to change to a different port number:

The internal and external ports must be the same; and

You must convince AdGuard Home that it is a first-time installation:

 $ cd ~/IOTstack
 $ docker-compose stop adguardhome
 $ docker-compose rm -f adguardhome
 $ sudo rm -rf ./volumes/adguardhome
 $ docker-compose up -d adguardhome

Repeat the Quick Start procedure, this time substituting the new Admin Web Interface port where you see "8089".

About port 3001:3000¶

Port 3001 (external, 3000 internal) is only used during Quick Start procedure. Once port 8089 becomes active, port 3001 ceases to be active.

In other words, you need to keep port 3001 reserved even though it is only ever used to set up port 8089.

About Host Mode¶

If you want to run AdGuard Home as your DHCP server, you need to put the container into "host mode". You need edit the AdGuard Home service definition in docker-compose.yml to:

add the line:
```
network_mode: host
```
remove the ports: directive and all of the port mappings.

Note:

It is not really a good idea to offer DHCP services from a container. This is because containers generally start far too late in a boot process to be useful. If you want to use AdGuard Home for DHCP, you should probably consider a native installation.