Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Flowise on Ubuntu 24.04 LTS

Flowise on Ubuntu 24.04 LTS — Support & Quick Start

Flowise on Ubuntu 24.04 LTS — Flowise is a visual, drag-and-drop builder for LLM workflows and AI agents — connect models, tools, vector stores and memory without writing glue code. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

Email support Product page Azure Marketplace listing

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

flowise.service crash-loops on the current image (Node.js CommonJS loader error), so http://<VM-IP>:3000/ never answers even though /var/lib/flowise/admin-password is written. (image build tested: 2026.628.1945)

What you will see: `systemctl status flowise` shows a restart loop; `sudo journalctl -u flowise` shows a `node:internal/modules/cjs/loader` error; first boot reports "Flowise never responded after 10 attempts".

Fix status: Fix merged 2026-09-16 (image-factory PR #221, proven on a rebuilt image) — a fresh build of the current Flowise release whose first boot waits long enough for Flowise's slow first start (about 6.5 minutes on a 4-vCPU VM) and verifies the sign-in the way the Flowise UI does. Re-publication is blocked on a certification failure we are working through, so the image you deploy today is still the one described above (and 79 days stale). 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 ports3000 (web UI + API)
Open in browserhttp://<VM-IP>:3000/
Admin credential filesudo cat /var/lib/flowise/admin-password
Sign in asthe e-mail address in FLOWISE_ADMIN_EMAIL (Flowise 3.1.4 images); dcaadmin (FLOWISE_USERNAME) on earlier 2.2.7 images
Service(s)flowise
Configuration/etc/default/flowise (root-only); database, uploads and Flowise's generated auth secrets in /opt/flowise/data/
Logsjournalctl -u flowise -f
VersionFlowise 3.1.4 on Node.js 24 in image 2026.917.1902 and later; Flowise 2.2.7 in earlier images
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) — 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 with the generated credential (see First login below).
  4. Add your model provider credentials (Credentials) and build your first chatflow; put TLS in front before real use.

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

Sign in as the e-mail address in FLOWISE_ADMIN_EMAIL (Flowise 3.1.4 images); dcaadmin (FLOWISE_USERNAME) on earlier 2.2.7 images.

  1. Print the credential file. Flowise 3.1.4 images (2026.917.1902 and later) hold FLOWISE_ADMIN_EMAIL and FLOWISE_ADMIN_PASSWORD: Flowise 3.x signs in by e-mail, and first boot has already created that owner account, so the setup page is never offered to a visitor. Earlier 2.2.7 images hold FLOWISE_USERNAME=dcaadmin and FLOWISE_PASSWORD.
  2. Open http://<VM-IP>:3000/ and sign in with those values.
  3. Change the password from your account settings in the Flowise UI (2.2.7 images: edit FLOWISE_PASSWORD in /etc/default/flowise and `sudo systemctl restart flowise`), then delete the file once stored securely. REST API calls need an API key from the dashboard's API Keys page, sent as Authorization: Bearer <key>.

Sign in as admin (unless noted), then change the password immediately. The file is root-only and can be deleted once the password is stored securely.

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.