GLWS · LINUX LEARNING PATH
Your first VPS.
One checked step at a time.
A practical route from your first login to a domain with HTTPS. Follow one distribution's commands, verify each checkpoint and keep a tested recovery route.
Use an Ubuntu 24.04 LTS or AlmaLinux 9 server you administer. Before starting, record its login details and confirm that your provider's recovery console is available. Each lesson explains its own prerequisites; this sequence does not replace them.
Keep your original SSH session open while creating an account, installing a key or adjusting firewall rules. A fresh connection must work before you remove an older access method. The directory, editor and permissions guides are useful optional preparation if the terminal is new to you.
Your route from login to HTTPS
Complete the checkpoint before moving to the next lesson. Follow the commands for your distribution.
Connect and identify your server
Open SSH, verify the host fingerprint and check which account and operating system you reached.
Checkpoint: Your terminal is connected to the intended VPS and you can identify the account, hostname and distribution.
Open lesson →Create and test an administrator account
Set up a separate daily account and test sudo from a second connection before changing root login.
Checkpoint: A fresh login as the new account works and sudo id -u prints 0. Keep the original session open.
Open lesson →Install and independently test an SSH key
Keep the private key on your computer, install its public half and prove that the new account can log in using the key.
Checkpoint: A second key-only connection and sudo both work. Review any optional authentication-policy changes only after that test.
Open lesson →Protect access and add a firewall
Allow the SSH port you actually use before enabling the appropriate firewall for your distribution.
Checkpoint: A new SSH connection still works with the firewall active, and you have reviewed the resulting rules.
Open lesson →Update the operating system
Use APT or DNF to install trusted packages and apply available updates with a recovery plan.
Checkpoint: Package-manager operations complete successfully and you have checked whether a planned reboot is needed.
Open lesson →Understand the address and DNS path
Learn which interface, route and resolver your server uses so you can separate network problems from application problems.
Checkpoint: You can inspect the server's addresses and route, and resolve a public host name.
Open lesson →Bring up a basic Apache site
Install Apache, add the necessary web firewall rules and verify HTTP from outside the VPS.
Checkpoint: Apache's service is healthy and your server responds on HTTP from another network.
Open lesson →Connect your domain and enable HTTPS
Add apex and www records, a named Apache virtual host and a certificate with tested automatic renewal.
Checkpoint: Both host names serve your site over verified HTTPS, and the certificate renewal dry run succeeds.
Open lesson →Make an independent backup and test a restore
Keep another copy outside the VPS and prove that the files you need can be restored before they become irreplaceable.
Checkpoint: You have restored a sample into a separate directory and verified the recovered contents; your live files remain intact.
Open lesson →
Use your provider's documentation for its console, recovery tools and account-specific access details.
Browse all Linux guides