Overview
AdGuard Home is useful for network DNS filtering. Better-PaaS gives it a practical home on your own server with a one-click app workflow, domain routing, HTTPS, logs, and persistent storage habits.
Catalog image and ports
Better-PaaS deploys AdGuard Home from adguard/adguardhome:latest on container port 3000.
- Image: adguard/adguardhome:latest
- Port: 3000
- Volumes: /opt/adguardhome/work, /opt/adguardhome/conf
Production notes for this catalog app
DNS services may need additional port exposure beyond the web UI depending on your network design.
Why host AdGuard Home with Better-PaaS
Better-PaaS is designed for apps like AdGuard Home: small services that need reliable routing, a domain, persistent data, and quick redeploys without manually editing reverse proxy files.
Deployment checklist
Before going live, decide the domain, persistent volume, backup cadence, and any environment variables AdGuard Home needs. For AdGuard Home, pay special attention to ad blocking and local DNS management.
- Choose the app catalog template or Docker image
- Add required environment variables
- Attach a persistent volume if data must survive redeploys
- Deploy and inspect logs
- Add a custom domain after the app is healthy
Operations after launch
Watch logs during the first deploy, confirm storage survives a redeploy, and include the app data in server backups. If the service exposes an admin area, use a strong password and restrict access where appropriate.
FAQ
Can AdGuard Home run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does AdGuard Home need persistent storage?
Most security apps need some persistent storage or database plan. Treat app data and config as something to back up.