Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Jenkins LTS on Ubuntu 24.04 LTS

Jenkins LTS on Ubuntu 24.04 LTS — Support & Quick Start

Jenkins LTS automation server on Ubuntu 24.04 LTS with per-VM initial admin password and setup wizard ready on first boot.

Email support Product page Azure Marketplace listing

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

Signing in as admin with /root/.jenkins-initial-password returns HTTP 401: the Configuration-as-Code admin user was never created (plugin pre-install is best-effort at build), so Jenkins is waiting in its standard setup wizard instead. (image build tested: 2026.822.344 (newest build at sweep time; the version the Marketplace publishes today is 2026.05.30, not separately booted))

What you will see: http://<VM-IP>:8080/ shows "Unlock Jenkins" (anonymous requests get 403); admin + the documented password → 401; /var/lib/jenkins/secrets/initialAdminPassword exists.

Workaround:

  1. Unlock the wizard: `sudo cat /var/lib/jenkins/secrets/initialAdminPassword`, paste it at http://<VM-IP>:8080/, install the suggested plugins and create your first admin user (standard Jenkins first run). The sweep proved the wizard is active and the file exists; the unlock itself was not sweep-run.
sudo cat /var/lib/jenkins/secrets/initialAdminPassword

Fix status: Fix merged 2026-09-16 (image-factory PR #224, proven on a rebuilt image) — first boot creates the admin user itself (no Configuration-as-Code dependency), verifies the sign-in and removes the setup wizard. The rebuilt image is in Marketplace certification and becomes the published version when it clears; VMs from the image you deploy today still need the wizard unlock above. 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 ports8080 (Jenkins web UI)
Open in browserhttp://<VM-IP>:8080/
Admin credential filesudo cat /var/lib/jenkins/secrets/initialAdminPassword
Sign in asnone until you create it: unlock the setup wizard with the password above, then create the first admin user (see Known issue — /root/.jenkins-initial-password is NOT accepted on the current image)
Service(s)jenkins
Configuration/var/lib/jenkins/ (JENKINS_HOME); /var/lib/jenkins/casc_configs/jenkins.yaml (Configuration as Code seed)
Logsjournalctl -u jenkins -f
VersionJenkins LTS (official apt repository, current at build)
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): 8080 (Jenkins 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>:8080/, unlock the setup wizard with `sudo cat /var/lib/jenkins/secrets/initialAdminPassword`, and create your first admin user (see First login below).
  4. Create your first pipeline (New Item → Pipeline) or connect agents; put Jenkins behind HTTPS before exposing it beyond your network.

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/jenkins/secrets/initialAdminPassword

Sign in as none until you create it: unlock the setup wizard with the password above, then create the first admin user (see Known issue — /root/.jenkins-initial-password is NOT accepted on the current image).

  1. Print the setup-wizard unlock password: `sudo cat /var/lib/jenkins/secrets/initialAdminPassword`. (First boot also writes /root/.jenkins-initial-password for a Configuration-as-Code `admin` user, but on the current image that user is never created — signing in as admin with it returns HTTP 401.)
  2. Open http://<VM-IP>:8080/ (Jenkins takes a minute or two to start): the Unlock Jenkins page appears — paste the initialAdminPassword value, install the suggested plugins, and create your first admin user when the wizard asks.
  3. Sign in with the user you just created; delete both password files once done (`sudo shred -u /root/.jenkins-initial-password`). Add plugins from Manage Jenkins → Plugins.

On the current image the setup wizard is ACTIVE and the Configuration-as-Code admin does not exist: unlock the wizard with /var/lib/jenkins/secrets/initialAdminPassword and create your own admin user. This is the standard Jenkins first-run flow; /root/.jenkins-initial-password is not a working login (image fix pending).

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.