【Add-on Guide】Adguard Home - Network-wide ads & trackers blocking DNS server

eWeLink CUBE
1

Hello,

iHost is capable of running an Adguard server, which enables you to have a small adguard local server, possibly enabling other LAN devices to have some ad protection.
Here is how:

  1. Create a volume named adguardhome or similar.

    image
    image769×83 1.64 KB

  2. In the add-on list, search for adguard/adguardhome and add it to your local list.
    image

  3. After adding, go to it on the list and click Run.
    image

  4. As Optional settings:
    Network: host
    Volume:
    Host volume: adguardhome, or whatever you created in step (1)
    Add-on volume: /opt/adguardhome
    image

  5. In filebrowser/filebrowser add-on, map the adguard volume to a browse-able folder.
    image

  6. Open filebrowser and edit file adguardhome > conf > AdGuardHome.yaml.
    Change http > address property, choosing a not used port (3001 in my case). The default port 3000 is already used by the add-on itself.
    image image

  7. Restart the adguardhome docker instance.
    After that you can access web ui in http://[ihost]:3001

    image
    image789×1020 30.1 KB

    (maybe you can run it as bridge and choose which ports to open)
    image
    image947×834 35.5 KB

    image
    image1101×1082 64.2 KB

2 Likes
2

Nice one, thx! :heart:

1 Like
3

Since eWeLink CUBE 2.2.0 this Adguard Home image doesn’t work anymore because eWeLink CUBE uses port 53 now :frowning: :frowning: :frowning:

2024-08-29T16:54:25 2024/08/29 19:54:25.350533 [fatal] couldn't start forwarding DNS server: starting listeners: listening to tcp socket: listen tcp 192.168.3.13:53: bind: address already in use

4

Hello,

After update 2.2.0 port 53 is apparently in use by eWelink CUBE.

Is there any specific reason for that?
Would it be possible to set if free?

PS: I use it to host an Adblock Home instance from iHost.

Thanks

5

Moved your post here and pinged @SuiKa, our dev, for advice.

Thx for your feedback.

6

53 port is occupied by us.
Can you use bridge network and map the 53 port to other port of your machine?

7

Yes, I’ve considered that, but the problem is figuring out how to use that alternative port for DNS on other devices.
I mapped port 54 on iHost to port 53 on the container and tried using <IP>:54 as the DNS on iOS and Windows 10, but it doesn’t seem to be working.

8

Are you monitoring the CPU and Memory usage?

Depending of the size of your blocklists, ADGuard Home will demand a reasonable amount of memory and CPU