Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Gitea on Ubuntu 24.04 LTS

Gitea on Ubuntu 24.04 LTS — Support & Quick Start

Gitea on Ubuntu 24.04 LTS — Gitea is a lightweight self-hosted Git service: repositories, pull requests, issues, and CI integration under your own control. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

At a glance

Application ports3000 (web UI); Git over SSH uses the VM's port 22
Open in browserhttp://<VM-IP>:3000/
Admin credential filesudo cat /var/lib/gitea/admin-password
Sign in asdcaadmin
Service(s)gitea
Configuration/etc/gitea/app.ini (open registration disabled); data in /var/lib/gitea/
Logsjournalctl -u gitea -f
VersionGitea 1.22.6
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 as dcaadmin (see First login below).
  4. Create your first organization and repository; push over HTTPS on :3000 or over SSH on port 22.

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

Sign in as dcaadmin.

  1. Print the credential file: GITEA_ADMIN_USER=dcaadmin and GITEA_ADMIN_PASSWORD.
  2. Open http://<VM-IP>:3000/ and sign in as dcaadmin.
  3. Change the password (Settings → Account) and delete the file once stored securely.

Sign in as dcaadmin (site administrator). Self-registration is disabled in app.ini; create users from Site Administration.

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.