First boot now authenticates its own `FLUSH PRIVILEGES` (it used to run unauthenticated and die with ERROR 1045), verifies `root` against the running server and only then writes /root/.mariadb-initial-password and the completion marker. The password survives reboots.
If you deployed this VM before 2026-09-16, it came from the older image and is not changed by the new publication — redeploy from the current Marketplace version, or apply the one-time repair below:
sudo mkdir -p /etc/app && sudo touch /etc/app/.firstboot-completeImage change: see the pull request.
Source: the Marketplace live version set for this offer, read from Partner Center on 2026-09-16. New deployments take the newest version by default.
| Application ports | 3306 (MariaDB) |
|---|---|
| Admin credential file | sudo cat /root/.mariadb-initial-password |
| Sign in as | root (root@localhost, password auth) |
| Service(s) | mariadb |
| Configuration | /etc/mysql/mariadb.conf.d/50-server.cnf (bind-address) |
| Logs | journalctl -u mariadb -f; /var/log/mysql/error.log |
| Version | MariaDB 11.4 LTS (MariaDB repository) |
| Platform | Ubuntu 24.04 LTS |
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/.mariadb-initial-passwordSign in as root (root@localhost, password auth).
This is the MariaDB root password set at first boot (root@localhost is switched to password auth, so plain `sudo mariadb` is refused). Connect with `mariadb -u root -p`, change it with ALTER USER, and delete the file once stored securely.
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.