TL;DR – first 30 minutes on Ubuntu Server
- Patch first: Update the box before you start adding your own complexity to it.
- Create proper access: Named admin user, SSH keys, and a verified login path beat rushing straight into application setup.
- Baseline the box: Hostname, timezone, firewall and a few small tools save time later.
- Verify now: Check disk, network and service state while the system is still simple.
Start here: If this server will be remotely managed, pair this checklist with Linux SSH Hardening Checklist and Ubuntu Remote Access: SSH vs XRDP vs VNC
| Topic | When | Command |
|---|---|---|
| Update packages | Immediately after first boot | sudo apt update && sudo apt upgrade -y |
| Create admin user | Before disabling bad habits | sudo adduser opsadmin |
| Enable firewall | After you know required ports | sudo ufw enable |
| Check disk and time | Before workload install | df -h and timedatectl |
A fresh Ubuntu server is at its easiest to understand in the first half hour. That is exactly why the first half hour matters. If you do the housekeeping early, the box stays easier to trust and easier to recover later.
Patch before you personalise
I do not like building on top of an unpatched baseline unless there is a very specific reason not to. It keeps the first-boot assumptions honest and reduces the chance that later behaviour is tied to outdated packages rather than your actual configuration.
Create proper admin access
Named accounts, SSH keys and one clean admin path beat temporary shortcuts. If the box is going to stay around, treating access properly from minute one removes a lot of future cleanup work.
Baseline the box
This is also the stage where I install a few tools that nearly always earn their keep: `curl`, `vim` or `nano` depending on the box, and whatever monitoring or shell helpers the environment expects.
Verify storage, network and the small quality-of-life wins
You do not need a long acceptance test for a new Ubuntu server, but you do need to prove the basics are what you think they are. Disk layout, addresses, failed services and listening sockets are the fast checks that catch bad assumptions early. If you want the dedicated disk-capacity walkthrough after this first-pass check, use How to Check Disk Space in Linux.
If you want the quality-of-life touch that makes shell access friendlier on long-lived hosts, How to Create a Custom Linux MOTD is the next stop.
The checklist I would sign off before moving on
- Packages updated and reboot completed if needed.
- Named admin user created and tested.
- SSH access working the way I intend to use it.
- Firewall enabled with only the required ports.
- Hostname, time and basic network state verified.
- Disk space and failed services checked before workload install.