Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / VictoriaMetrics on Ubuntu 24.04 LTS

VictoriaMetrics on Ubuntu 24.04 LTS — Support & Quick Start

VictoriaMetrics on Ubuntu 24.04 LTS — VictoriaMetrics is a fast, resource-efficient time-series database and long-term store, compatible with Prometheus remote_write, PromQL/MetricsQL and Grafana. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure sub…

At a glance

Application ports8428 (HTTP API + vmui — Basic Auth on every endpoint except the /health and /ping liveness checks)
Open in browserhttp://<VM-IP>:8428/vmui/
Admin credential filesudo cat /root/victoriametrics-admin-credentials.txt
Sign in asvmadmin (VM_AUTH_USER) with the generated password (Basic Auth)
Service(s)victoriametrics
Configuration/etc/default/victoriametrics (VM_AUTH_USER; on images before 21 October 2026 also VM_AUTH_PASSWORD); images from 21 October 2026 onward read the password from /etc/victoriametrics/httpauth-password (root:victoriametrics 0640); data in /var/lib/victoriametrics/
Logsjournalctl -u victoriametrics -f
VersionVictoriaMetrics 1.147.0 (single node)
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): 8428 — to your collectors and dashboards 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>:8428/vmui/ with the generated Basic Auth credentials (see First login below).
  4. Add VictoriaMetrics as a Prometheus data source in Grafana (URL http://<VM-IP>:8428 with Basic Auth).

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 /root/victoriametrics-admin-credentials.txt

Sign in as vmadmin (VM_AUTH_USER) with the generated password (Basic Auth).

  1. Print the credential file: username vmadmin and the generated password.
  2. Open http://VM-IP:8428/vmui/ and sign in with Basic Auth. To test the password from a shell, query a protected endpoint: `curl -u 'vmadmin:PASSWORD' 'http://VM-IP:8428/api/v1/query?query=up'`. /health and /ping answer without a password, so they prove nothing about it.
  3. Point Prometheus remote_write / vmagent at http://VM-IP:8428/api/v1/write with basic_auth, and put TLS in front before sending real data.
  4. Rotate the password. Images from 21 October 2026 onward (image version 2026.1021.230 or later): replace the contents of /etc/victoriametrics/httpauth-password (keep it root:victoriametrics 0640); VictoriaMetrics re-reads the file every 2 seconds, so no restart is needed. Older images: change VM_AUTH_PASSWORD in /etc/default/victoriametrics and run `sudo systemctl restart victoriametrics`; those images pass the password on the service's command line, where `ps` shows it to every local account. Then update or delete the credential file.

Basic Auth as vmadmin with the generated password, on every endpoint except /health and /ping. Rotate the password (last step above) and put TLS in front before real use.

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.