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…

At a glance

Application ports3001 (web UI)
Open in browserhttp://<VM-IP>:3001/
Sign in ascreated by YOU in the setup wizard — the first visitor to :3001 becomes the administrator
Service(s)uptime-kuma
Configuration/opt/uptime-kuma/ (data in /opt/uptime-kuma/data/); quick-start notes: sudo cat /root/UPTIME-KUMA-README.txt
Logsjournalctl -u uptime-kuma -f
VersionUptime Kuma 2.4.0 (Node.js)
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) — to your IP until setup is complete — 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 create the admin account in the wizard (see First login below).
  4. Add your first monitors and a notification channel; publish a status page if you want one.

First login

  1. Open http://<VM-IP>:3001/ immediately after deployment and complete the setup wizard — the FIRST visitor creates the admin account, so keep the NSG scoped to your IP until you have.
  2. Enable two-factor auth (Settings → Security) and put TLS in front before real use.
  3. The optional "real browser" monitor type needs Chromium (not bundled): sudo apt-get install chromium-browser, then set the executable path in Settings.

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.