AdGuard Home showing all clients as the same

[thedinz]

Hello

I installed adguard home on docker on my network, it's working as I can see by what it's blocking. The only issue I see is there is only 1 client being identified and that's the machine running docker, adguard is acting as if every query is coming from that machine.

What did I do wrong and how do I fix this? I even went into settings a manually added a few clients but still only shows the docker-machine as the client making all requests rather than the actual devices that are..

[alexpovel]

Just a guess, but you are probably running it with the --port option to docker run? This will run it through docker-proxy. I am also using the built-in DHCP server, for which running the container that way is not possible in the first place.

Therefore, I run it with the network_mode: host option set (docker-compose). For example:

version: "3.2"

volumes:
  work:

services:
  main:
    # For configs, see https://hub.docker.com/r/adguard/adguardhome
    image: adguard/adguardhome
    container_name: adguard
    network_mode: host  # Required for DHCP server
    volumes:
      - work:/opt/adguardhome/work
      - ./conf:/opt/adguardhome/conf
    restart: unless-stopped

This will show up as:

$netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 :::80                   :::*                    LISTEN      11192/AdGuardHome
tcp6       0      0 :::53                   :::*                    LISTEN      11192/AdGuardHome
...
udp        0      0 0.0.0.0:67              0.0.0.0:*                           11192/AdGuardHome
udp        0      0 0.0.0.0:68              0.0.0.0:*                           594/dhcpcd
...
udp6       0      0 :::53                   :::*                                11192/AdGuardHome

Now, AGH runs less isolated, but no longer behind the docker proxy. It would say docker-proxy for you (presumably) where it now says AdGuardHome. This allows your AGH instance to also see all real source IPs. It won't map them to hostnames properly. For that, you would also need to use it as your DHCP server (unless you make the effort to map everything manually -- not a great idea).

Note that I've never run your setup (docker run with --port), so my guess might be off.

[thedinz]

This gets a little over my head I hate to admit, I am willing to use the DHCP server but no idea how to configure it I read the docs but still makes 0 sense to me, I found where my DHCP is set up in my fios router.

Back to the issue at hand, I did as you suggested and added network_mode: host

to my docker-compose file this, unfortunately, made the admin panel not load on any of the crazy (docker internal I assume) ip's it said I could access it on, including 127.0.0.1.

Not sure what the issue is there

[alexpovel]

It should come up at your machine's address (IP/hostname) under port 80, so just browsing to hostname of that machine should work. Only if you run it on the same machine you're also trying to browse to it from will 127.0.0.1 ( = localhost) work. I remember something about port 3000 on initial setup, but my setup is reachable at 80, so no port specification needed.

[thedinz]

I did not try on port 80, the console outputs a bunch of ways to access it and they all had :3000 attached. I could try port 80 but I am also running a webserver on that box on port 80 so not sure how that would work.

[alexpovel]

You wouldn't have been able to open AGH on 80 if it was already in use, so we can assert that that's not it. You can't have your webserver and also AGH on 80, you will need a reverse proxy for that. So try 3000, that should be it, or set e.g. 8080 in the YAML config file and go that route.