MinIO on Ubuntu 24.04 LTS — Support & Quick Start

At a glance

Application ports	9000 (S3 API), 9001 (Console) — plain HTTP; add TLS or a fronting proxy before exposing
Open in browser	http://<VM-IP>:9001/
Admin credential file	sudo cat /var/lib/minio-firstboot-credentials
Sign in as	minioadmin-<random> (MINIO_ROOT_USER in the credential file — not `admin`)
Service(s)	minio
Configuration	/etc/default/minio (MINIO_VOLUMES=/var/lib/minio/data, /mnt/data on images built before 2026-09-17; console on :9001; root credentials). /mnt is the Azure temporary disk on sizes that have one — never point MINIO_VOLUMES there; attach a data disk for large stores
Logs	journalctl -u minio -f
Version	SILO RELEASE.2026-09-16T00-00-00Z, the maintained AGPL-3.0 fork of MinIO by PGSTY (github.com/pgsty/silo), compiled from source and installed under the MinIO names and paths; MinIO-compatible S3 and admin API, Console and configuration; single node, data in /var/lib/minio/data on the OS disk. Security status: upstream community MinIO is archived and gets no security fixes; its final release leaves CVE-2026-41145 and CVE-2026-40344 (CVSS 8.8, unauthenticated object write with any valid access key) unpatched, and the fork fixes both plus CVE-2026-39414, CVE-2026-34204, CVE-2026-33322, CVE-2026-33419 and CVE-2026-42600 (fork advisories: silo.pgsty.com/about/security-advisories/). Images built before 2026-09-17 ship upstream MinIO RELEASE.2025-09-07T16-13-09Z with those CVEs unpatched and data in /mnt/data.
Platform	Ubuntu 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): 9001 (Console) to your IP; 9000 (S3 API) to your clients — 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 the MinIO Console at http://<VM-IP>:9001/ and sign in with the generated root user (see First login below).
4. Create your first bucket and an access key in the Console (or with `mc admin accesskey create` on the VM); point S3 clients at http://<VM-IP>:9000/.

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/minio-firstboot-credentials

Sign in as minioadmin-<random> (MINIO_ROOT_USER in the credential file — not `admin`).

1. Print the credential file: MINIO_ROOT_USER (per-VM root user name) and MINIO_ROOT_PASSWORD, generated at first boot.
2. Open the Console at http://<VM-IP>:9001/ and sign in with those values. The SILO Console is the full administration UI: buckets, objects, users, policies and Access Keys.
3. Create access keys for applications in the Console (Access Keys) or with the bundled client on the VM: `mc alias set local http://127.0.0.1:9000 <MINIO_ROOT_USER> <MINIO_ROOT_PASSWORD>`, then `mc admin accesskey create local/`. (On images built before 2026-09-17 the upstream Console is an object browser without an access-key screen, so use `mc`.) Rotate the root credentials in /etc/default/minio and delete the file.

The root user is per-VM (minioadmin-xxxxxxxx), not `admin`; both lines are in the file. Point S3 clients at http://<VM-IP>:9000/ with an access key from the Console or `mc admin accesskey create`.

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.