SSH Basics for a New VPS Owner

This page contains affiliate links. If you make a purchase through one, we may earn a commission at no extra cost to you.

SSH is how you actually control a VPS — it’s the secure command-line connection between your computer and your server, and unlike shared hosting’s point-and-click control panel, a VPS expects you to use it at least occasionally. If the terminal is unfamiliar territory, here’s what you actually need to know to get started safely.

What SSH Actually Is

SSH (Secure Shell) is an encrypted connection protocol that lets you send commands to your server from your own computer’s terminal application, as if you were typing directly on the server itself. Everything you type — and everything the server sends back — is encrypted in transit, which is what makes it safe to manage a server remotely over the internet rather than needing physical access to the machine.

Password vs. SSH Key Login

You can connect to a VPS with a username and password, the same way you’d log into most websites, but SSH key authentication is the real security upgrade worth setting up early. An SSH key pair consists of a private key that stays on your computer and a public key that goes on the server — the server checks that your private key matches before granting access, without a password ever being transmitted at all. This is both more secure (immune to password-guessing attacks) and more convenient once it’s set up, since you’re not typing a password every time you connect. Most VPS providers, including Contabo, let you add your public key directly during server setup.

The Handful of Commands You’ll Actually Use Most

• Navigating folders and listing files — moving around your server’s file system and seeing what’s in a directory, the command-line equivalent of opening folders in a file browser.
• Editing a file directly on the server — using a built-in text editor to make a quick configuration change without downloading and re-uploading the whole file.
• Checking running processes and resource usage — seeing what’s actually consuming CPU and RAM in real time, which is the first thing to check if a site feels slow.
• Restarting a specific service — like the web server software itself, without rebooting the entire machine, when something needs a fresh start.

One Real Safety Habit: Don’t Work as Root by Default

Your VPS comes with a “root” account that has unrestricted access to do absolutely anything on the server, including commands that can break it irreversibly with a single typo. Best practice — genuinely followed by experienced server admins, not just a theoretical recommendation — is to create a separate user account for day-to-day work and only use root-level access (via a command like sudo) for the specific tasks that actually require it. This isn’t about distrust of yourself; it’s that a mistyped command under an unrestricted account has no safety net, while the same typo under a limited account is far less likely to cause real damage. This kind of habit is exactly what our VPS beginner mistakes guide covers in more depth.