Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / ERPNext 15 on Ubuntu 24.04 LTS

ERPNext 15 on Ubuntu 24.04 LTS — Support & Quick Start

ERPNext 15 on Ubuntu 24.04 LTS — ERPNext is a full-featured open-source ERP: accounting, inventory, manufacturing, CRM, HR, and projects in one integrated system. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

Known issue on the current image (as of 2026-09-15)

First boot cannot create the site: `bench new-site erpnext.local` fails because bench's Redis Queue (127.0.0.1:11000) is not running yet, so there is no site, no Administrator password and no /var/lib/erpnext/admin-password. (image build tested: 2026.822.232 (newest build at sweep time; the version the Marketplace publishes today is 2026.05.121, not separately booted))

What you will see: http://erpnext.local/ (or http://<VM-IP>/) shows Frappe's "site not found" page or nothing; the credential file is absent; `sudo journalctl -u firstboot` shows `Error 111 connecting to 127.0.0.1:11000`.

Fix status: Fix merged 2026-09-16 (image-factory PR #220, proven on a rebuilt image) — first boot starts bench's own Redis services before creating the site (four further defects cured on the way) and proves the Administrator login before it reports done. Re-publication of this offer is held on a plan/image-definition change we have to make first, so the image you deploy today is still the one described above. No proven workaround on it. Track the fix.

Source: our 2026-09-15 image sweep of the newest published build. This notice is removed when a build that passes the same test is live on the Marketplace.

At a glance

Application ports80 (web UI), 443
Open in browserhttp://erpnext.local/ (add `<VM-IP> erpnext.local` to your hosts file first)
Admin credential filesudo cat /var/lib/erpnext/admin-password
Sign in asAdministrator
Service(s)nginx, supervisor (frappe-bench workers), mariadb, redis-server
Configuration/home/frappe/frappe-bench/sites/erpnext.local/site_config.json (site `erpnext.local`); bench commands run as the `frappe` user
Logs/home/frappe/frappe-bench/logs/; journalctl -u nginx -f
VersionERPNext 15 / Frappe 15 (bench, production mode: nginx + supervisor)
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): 80 (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. Wait for first boot to finish (5–10 minutes), map erpnext.local to the VM's IP in your hosts file, open http://erpnext.local/ and sign in as Administrator (see First login below).
  4. Complete the setup wizard (company, fiscal year, chart of accounts), then attach your domain and enable HTTPS (bench setup lets-encrypt).

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/erpnext/admin-password

Sign in as Administrator.

  1. Print the generated Administrator password from the file (first boot takes several minutes: it creates the site and runs `bench setup production`).
  2. The site is served for the host name erpnext.local: add `<VM-IP> erpnext.local` to your hosts file (or a DNS record), open http://erpnext.local/ and sign in as Administrator, then complete the ERPNext setup wizard. A bare http://<VM-IP>/ may answer with Frappe's "site not found" page.
  3. Change the Administrator password and delete the file. The bench's MariaDB root password is in /etc/mysql/.frappe_root_pw (root-only). To serve your real domain: `bench setup add-domain <domain>` then `bench setup nginx` and reload nginx.

The login is `Administrator` (not `admin`). The nginx site is named erpnext.local — reach it by that host name (hosts file or DNS) until you add your own domain. First boot can take 5–10 minutes before the site answers.

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.