DumbMonit

IntegracionesSeguridad e identidad

Monitorizar AdGuard Home con DumbMonit

The DNS filter: protection on or paused, queries and blocks, filter lists that stopped updating, upstream servers that fail, updates.

DocumentaciónSitio web oficial: AdGuard Home

Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.

Qué vigila DumbMonit

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.

Uso habitual. DNS filter: protection, blocks, filter lists, upstream servers, updates

Ejemplos

  • AdGuard Home
  • AdGuard Home on OpenWrt or a NAS

Cómo se conecta

Qué necesita

  • User name / passwordThe dedicated user added to AdGuardHome.yaml, sent as HTTP basic authentication.

No hace falta ninguna cuenta.

Puertos de red que abrir

  • 80/TCPWeb interface and API (HTTP, default)
  • 3000/TCPOnly with the web interface left on port 3000, the first-run default
  • 443/TCPOnly with the https scheme option
Pasos de configuración: Add a user for DumbMonit to AdGuard Home
  1. 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'
  2. 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" }
  3. In DumbMonit, enter the address of the AdGuard Home web interface, then the user dumbmonit and its password.

Ojo. 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.