DumbMonit
IntegrationsSecurity and identity
Monitor AdGuard Home with DumbMonit
The DNS filter: protection on or paused, queries and blocks, filter lists that stopped updating, upstream servers that fail, updates.
DocumentationOfficial website: AdGuard Home
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
The DNS filter itself: whether protection is on, whether its DNS server runs, what it answered and blocked, whether its filter lists still update, whether its upstream servers answer, and whether a newer version is out.
Typical use. DNS filter: protection, blocks, filter lists, upstream servers, updates
Examples
- AdGuard Home
- AdGuard Home on OpenWrt or a NAS
How it connects
What you need
- User name / passwordThe dedicated user added to AdGuardHome.yaml, sent as HTTP basic authentication.
No account needed.
Network ports to open
80/TCPWeb interface and API (HTTP, default)3000/TCPOnly with the web interface left on port 3000, the first-run default443/TCPOnly with the https scheme option
Setup steps: Add a user for DumbMonit to AdGuard Home
Make a bcrypt hash of a long random password (htpasswd comes with apache2-utils or httpd-tools).
htpasswd -B -C 10 -n -b dumbmonit 'LONG-RANDOM-PASSWORD'Stop AdGuard Home, add this line under users: in AdGuardHome.yaml with HASH replaced by the printed hash, then start it again.
- { name: dumbmonit, password: "HASH" }In DumbMonit, enter the address of the AdGuard Home web interface, then the user dumbmonit and its password.
Heads-up. AdGuard Home has no read-only user, so dumbmonit can change every setting: keep its password to DumbMonit alone, and turn on HTTPS in Settings → Encryption settings across an untrusted network.