Stage 8 · Lesson 9 of 9

A method for debugging your environment

Most setup problems give way to the same calm method. Think of it as an . Read the whole error message, especially the first line and any file path in it.

Ask what changed since it last worked. Then check the usual suspects in turn. Which program actually runs (which, type -a)?

Is PATH right? Are permissions and file owners right? Are the set?

Is the disk full? Which and are in use? What do the logs say?

Reproduce the problem with the smallest possible command. Change one thing at a time and write down what you tried. When you ask for help, include the command, the full error and what you already checked.

Common trapcopying fixes from search results until something works, without learning why it broke.

A question to check yourself, an AI practice session and 2 cheat sheet entries come when you add the roadmap to your account. Add it

Resources for this stage

Start with· follow one of these

GuideFree
Initial Server Setup with Ubuntu (DigitalOcean)
DigitalOcean · Beginner
A clear, widely used checklist for a new user, sudo, SSH access and a firewall on Ubuntu
CourseFree
The Missing Semester of Your CS Education
MIT · Beginner
The command-line environment lecture covers SSH, tmux, job control and dotfiles

Practise

Linux Upskill Challenge
A free month of daily sysadmin tasks on your own server, from SSH to logs and scheduling
OverTheWire: Bandit
Its later levels need SSH keys, ports and network tools to move on

Keep handy

Everything curl
The free book on curl by its creator, for every option you will need
VS Code Remote Development
Edit files on your server (or in WSL) from VS Code over SSH

Also worth your time

roadmap.sh: LinuxGo deeper
The server, networking and troubleshooting branches of the Linux map