r/AdGuardHome

In case you weren't aware, a new version with the version number of 0.107.75 has now dropped more information on the update can be found here https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.107.75

Has anyone here managed to get SBS On Demand fully working with AdGuard Home and can share exactly what domains/services need to be whitelisted?

I’ve tried a bunch of the commonly suggested domains already, but SBS On Demand still either fails to load content, playback doesn’t start, or streams randomly break.

So far, I’ve tested various combinations of:

• sbs.com.au
• sbsod.com
• akamai/CDN-related domains
• video/ad/tracking exceptions people have mentioned in older threads

None of the previous suggestions I’ve found seem to completely fix it for me.

If you have it working properly, could you please share:

• Your exact whitelist entries
• Whether you’re using additional blocklists (HaGeZi, OISD, etc.) I currently have in play AdGuard DNS filter alongside HaGeZi Normal
• Whether HTTPS filtering, DNS rewrites, or upstream DNS settings affected it
• If the issue was related to ads, DRM, CDN, telemetry, or login/auth domains

Would really appreciate hearing from anyone who has SBS On-Demand working reliably behind AdGuard Home.

I'm trying to install Adguard Home with the Netbird guide. I begin with the following in /home/MYUSERNAME/

mkdir -p ~/adguardhome && cd ~/adguardhome
nano docker-compose.yml

In my yaml file, I insert the following which is slightly modified from the Netbird guide's text

services:
adguardhome:
image: adguard/adguardhome:latest
container_name: adguardhome
restart: unless-stopped
volumes:
- ./adguard/workdir:/opt/adguardhome/work
- ./adguard/confdir:/opt/adguardhome/conf
ports:
- "10.0.0.XX:53:53/tcp"   # the "XX" part is my server's ip
- "10.0.0.XX:53:53/udp"
- "10.0.0.XX:3003:3003/tcp"   # the original port is 3000 but Dockhand uses that already
- "10.0.0.XX:8080:80/tcp"
cap_add:
- NET_ADMIN

I'm using Dockhand here so I go into Stacks, then create, then select my yaml file, and deploy. Here are where the errors start in the logs.

[adguardhome][info] starting adguard home version="AdGuard Home, version v0.107.74"
[adguardhome][info] this is the first time adguard home has been launched
[adguardhome][info] checking if adguard home has the necessary permissions
[adguardhome][info] adguard home can bind to port 53
[adguardhome][info] dhcpd: warning: creating dhcpv4 server err="dhcpv4: invalid IP is not an IPv4 address"
[adguardhome][info] tls_manager: using default ciphers
[adguardhome][info] webapi: initializing
[adguardhome][info] webapi: This is the first launch of AdGuard Home, redirecting everything to /install.html
[adguardhome][info] permcheck: warning: found unexpected permissions type=directory path=/opt/adguardhome/work perm=0755 want=0700
[adguardhome][info] webapi: AdGuard Home is available at the following addresses:
[adguardhome][info] go to http://127.0.0.1:3000
[adguardhome][info] go to http://[::1]:3000
[adguardhome][info] go to http://172.19.0.2:3000
[adguardhome][info] starting plain server server=plain addr=0.0.0.0:3000

Dockhand says that the container is running with a green dot but when I visit http:10.0.0.XX:3003, I am not able to connect to Adguard Home. Unsure what to do from here.

For what it's worth, here's the ownership and permission details when I do ls -l /home/MYUSERNAME/

drwxrwxr-x 3 MYUSERNAME docker 4096 May 10 18:31 adguardhome
drwxrwxr-x 3 MYUSERNAME docker 4096 May 10 15:35 dockhand

When I do -l /home/MYUSERNAME/adguardhome/ I get

drwxr-xr-x 4 root   root   4096 May 10 18:31 adguard
-rw-rw-r-- 1 MYUSERNAME docker  401 May 10 18:31 docker-compose.yml

When I do -l /home/MYUSERNAME/adguardhome/adguard I get

drwxr-xr-x 2 root root 4096 May 10 18:31 confdir
drwxr-xr-x 3 root root 4096 May 10 18:31 workdir

I've been using AGH for nearly two years and sometimes experience weird delays with Apple Safari web browser, both on MacOS and mobile platforms. The AGH logs don't show the problem. Troubleshooting using nslookup or dig won't show the problem.

After two years, I finally discovered the root cause of the problem. A simple misconfiguration of Apple Safari will sneakily bypass your chosen DNS server.

There's an advanced setting in Safari called "used advanced tracking and fingerprinting protection" By default this setting is used only in Private Browsing mode. I had changed it to be used in All Browsing.

What does this setting do? It causes Safari to use Apple's own DNS servers over an encrypted channel, bypassing AGH.

More here: https://cleanbrowsing.org/support/troubleshooting/apple-screen-time

(The article is slightly dated, but the problem still exists in MacOS 26, iOS 26 an iPadOS 26.

I discovered the problem quite by accident. I clicked on a link that I absolutely knew should have been blocked by AGH. It was blocked in Vivaldi browser and blocked in DuckDuckGo browser, but it opened right up in Safari. After some troubleshooting and further investigation, I found the above article and sure enough that explained so many anomalies that were driving me crazy. After disabling that option, the problems have vanished.

I hope this helps someone else.

I made it so you can see a spaceship shoot blocked urls out of the sky. Runs in Docker. https://github.com/matthijsbro/dnsshooter