So you’ve got access to a Linux server for the first time. Maybe it’s a VPS you’ve just set up, maybe someone’s handed you access to one. Either way, the terminal is staring at you, and you’re not entirely sure where to start.
This guide covers the essentials: not everything there is to know about Linux, just the things that actually matter when you’re getting started!
What Linux Administration Actually Means
Administering a Linux server means managing it. Installing software, keeping it up to date, controlling who can access it, and ensuring it stays running. You don’t need to know everything upfront. Most people learn Linux by doing things on a real server, making mistakes, and figuring out why.
The command line is how most Linux administration gets done. It looks intimidating at first, but it becomes second nature quickly. Every command you run is just an instruction you’re giving the system.
Getting Connected
Most Linux servers are managed remotely over SSH. It’s a secure way of connecting to your server from your own machine and running commands as if you were sitting in front of it.
To connect, you need:
- Your server’s IP address – Provided when you set up your VPS or server
- A username – Usually root on a fresh server, though you’ll change this shortly
- An SSH client – Terminal on Mac and Linux has this built in, Windows users can use PuTTY or the built-in Windows Terminal
The basic command looks like this: ssh username@your-server-ip
Once you’re in, you’ll see a command prompt. That’s your starting point for everything.
The First Things to Do on a Fresh Server
Before anything else, run through these steps on any new Linux server:
- Update the system – Run sudo apt update && sudo apt upgrade on Ubuntu or Debian to make sure everything is current
- Create a new user – Avoid working as root. Create a regular user with adduser yourusername and give it sudo access
- Set a strong password – Use passwd to set or change passwords for any account
- Note your timezone – Run timedatectl to check and set it correctly, it matters when reading logs later
These take under ten minutes and give you a much cleaner foundation to work from.
Understanding the File System
Linux organises everything into a single directory tree starting at /. A few locations worth knowing early on:
- /etc – Configuration files for the system and installed software
- /var/log – Log files, useful when something goes wrong
- /home – Home directories for users
- /tmp – Temporary files, cleared on reboot
Navigation is done with a handful of commands. ls lists files, cd changes directory, pwd shows where you currently are, and cat displays file contents. These four will carry you a long way.
Installing and Managing Software
On Ubuntu and Debian-based systems, software is installed through apt. The commands you’ll use most often are:
- sudo apt update – Refreshes the list of available packages
- sudo apt install packagename – Installs a package
- sudo apt remove packagename – Removes a package
- sudo apt upgrade – Updates all installed packages
Keep your system updated regularly. Unpatched software is one of the most common ways servers get compromised, and running updates takes two minutes.
SSH Security From the Start
The default SSH setup works, but it’s worth improving early. One of the most impactful changes is adjusting your Linux SSH port away from the default. Port 22 is constantly scanned by automated tools looking for weak credentials. Moving to a different port won’t make you invisible, but it cuts down on a significant amount of background noise.
Beyond that, setting up SSH key authentication instead of passwords is strongly recommended. It’s more secure and more convenient once it’s in place.
Reading Logs When Something Goes Wrong
Logs are your best friend when something isn’t working. The main place to look is /var/log/. The syslog file covers general system events, and most services write their own logs to this directory too.
The tail command is useful for watching logs in real time: tail -f /var/log/syslog shows new entries as they appear. When something breaks, this is usually the first place to look.
You Learn Linux by Using It
The best thing you can do as a beginner is spend time on a real server. Break things, fix them, read the error messages carefully. Linux rewards curiosity, and the fundamentals covered here are enough to get you moving confidently. The rest follows naturally from there.
