Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / AdGuard Home on Ubuntu 24.04 LTS

AdGuard Home on Ubuntu 24.04 LTS — Support & Quick Start

AdGuard Home on Ubuntu 24.04 LTS — AdGuard Home is a network-wide DNS server that blocks ads and trackers for every device on your network, with a web console for rules, clients and query logs. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscr…

Email support Product page Azure Marketplace listing

At a glance

Application ports3000 (web UI, sign-in required), 53 tcp+udp (DNS, answering from first boot)
Open in browserhttp://<VM-IP>:3000/
Admin credential filesudo cat /var/lib/adguardhome-firstboot-admin-pw
Sign in asadmin (created at first boot, with a password generated on your VM)
Service(s)adguardhome
Configuration/var/lib/adguardhome/AdGuardHome.yaml (written at first boot by the completed setup); binary /usr/local/bin/AdGuardHome; Ubuntu's systemd-resolved stub listener is disabled so AdGuard Home owns port 53
Logsjournalctl -u adguardhome -f
VersionAdGuard Home 0.107.77
PlatformUbuntu 24.04 LTS

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself plus the application port(s): 3000 (web UI) and 53 tcp/udp (DNS) — to your own networks only — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
  3. Open http://<VM-IP>:3000/ and sign in as admin with the generated password (see First login below).
  4. Point your devices or VNet DNS at the VM's IP and review the query log in the console.

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /var/lib/adguardhome-firstboot-admin-pw

Sign in as admin (created at first boot, with a password generated on your VM).

  1. Setup is already complete — there is no wizard to finish. First boot submitted AdGuard Home's setup itself (web UI on port 3000, DNS on port 53), created the `admin` account with a password generated on your VM, and proved the sign-in and a DNS lookup before writing the file. Print it with `sudo cat /var/lib/adguardhome-firstboot-admin-pw`.
  2. Open http://<VM-IP>:3000/ and sign in as admin. Anonymous API calls are refused.
  3. DNS on port 53 (TCP and UDP) is answering already: test with `dig @<VM-IP> example.com`, then point your devices or VNet DNS at the VM. Scope 53 and 3000 in the NSG to your own networks — an open resolver on the internet will be abused for DNS amplification.

Sign in as admin with the password from the file. To change it later, follow AdGuard Home's own password-reset procedure (a bcrypt hash in AdGuardHome.yaml).

Troubleshooting

SymptomCheckFix
http://<VM-IP>:3000/ shows the setup wizard, and /var/lib/adguardhome-firstboot-admin-pw does not existThe image version your VM was deployed fromImages up to 2026.914.1904 left AdGuard Home's setup wizard undone: the FIRST visitor to :3000 creates the admin account, and DNS on port 53 starts only after the wizard. Keep 3000 scoped to your own IP in the NSG and finish the wizard yourself now. Images from 2026.917.0257 complete it at first boot.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.