Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Uptime Kuma on Ubuntu 24.04 LTS

Uptime Kuma on Ubuntu 24.04 LTS — Support & Quick Start

Uptime Kuma on Ubuntu 24.04 LTS — Uptime Kuma is a self-hosted uptime monitor with a clean dashboard, status pages and dozens of notification integrations (HTTP, TCP, ping, DNS, Docker and more). Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subs…

Email support Product page Azure Marketplace listing

Fixed on image version 2026.917.1756 (published 2026-10-12)

First boot completes Uptime Kuma's first-run setup itself: it chooses the embedded SQLite database, creates `admin` with a password generated on your VM (`sudo cat /var/lib/uptime-kuma-firstboot-admin-pw`), proves the sign-in against the running service while :3001 is still bound to 127.0.0.1, and only then opens :3001 to the network.

If you deployed this VM before 2026-10-12, it came from the older image and is not changed by the new publication — redeploy from the current Marketplace version, or apply the one-time repair below:

  1. VMs deployed from image 2026.914.1905 or earlier have no credential file: their setup screen was left to the first visitor. If you completed it yourself, nothing changes. If http://<VM-IP>:3001/ still shows the setup screen, finish it now with 3001 scoped to your own IP in the NSG.

Image change: see the pull request.

Source: the Marketplace live version set for this offer, read from Partner Center on 2026-10-12. New deployments take the newest version by default.

At a glance

Application ports3001 (web UI)
Open in browserhttp://<VM-IP>:3001/
Admin credential filesudo cat /var/lib/uptime-kuma-firstboot-admin-pw
Sign in asadmin (created at first boot, with a password generated on your VM)
Service(s)uptime-kuma
Configuration/opt/uptime-kuma/ (SQLite database and uploads in /opt/uptime-kuma/data/ — back it up); quick-start notes: sudo cat /root/UPTIME-KUMA-README.txt
Logsjournalctl -u uptime-kuma -f
VersionUptime Kuma 2.4.0 on Node.js 20
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): 3001 (web UI) — 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>:3001/ and sign in as admin with the generated password (see First login below).
  4. Add your first monitors and a notification channel; publish a status page if you want one.

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/uptime-kuma-firstboot-admin-pw

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

  1. Setup is already complete: first boot chose the embedded SQLite database and created the `admin` account on your VM, then proved its password against the running service. Print it with `sudo cat /var/lib/uptime-kuma-firstboot-admin-pw`.
  2. Open http://<VM-IP>:3001/ and sign in as admin; change the password in Settings → Security.
  3. Enable two-factor auth (Settings → Security) and put TLS in front before real use.
  4. The optional "real browser" monitor type needs Chromium (not bundled): sudo apt-get install chromium-browser, then set the executable path in Settings.

Sign in as admin with the password from the file. Until first boot has proven that credential, :3001 listens on 127.0.0.1 only, so an unclaimed instance is never reachable from the network.

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.