Guides

SSH for Beginners: Connecting to Your Server

What SSH is, how to connect to your server for the first time, and how to set up key login so you never type a password again.

Virtualized Team·June 18, 2026·3 min read
SSH for Beginners: Connecting to Your Server

The first time you rent a server, you get an IP address and some login details, and then you have to actually get into the thing. The tool for that is SSH. It sounds technical and it is genuinely simple once you have done it once. This walks you through it from zero.

What SSH actually is

SSH stands for Secure Shell. It is a way to open a command line on a computer that is somewhere else, securely, over the internet. When you SSH into your server, you are typing commands on your own machine but they run on the server. Everything that travels between the two is encrypted, so nobody in the middle can read it.

That is the whole concept. It is a secure remote terminal. Almost everything you do to manage a server happens through it.

What you need

Three things: your server's IP address, a username (often root to start with), and either a password or an SSH key. Your provider gives you all of these when you order the server.

You also need a terminal, and you already have one. On Mac and Linux it is the built in Terminal app. On Windows, the modern Terminal or PowerShell both have SSH built in now, so you do not need to install anything extra.

Connecting for the first time

Open your terminal and type this, swapping in your own details:

ssh root@your-server-ip

So if your server is at 203.0.113.10, that is ssh [email protected].

The very first time you connect, you will see a message asking if you trust this server, with a long string of characters. Type yes and press enter. This only happens once per server, and it is your computer remembering this machine so it can warn you if anything ever looks different later.

Then it asks for your password. Type it and press enter. One thing that throws everyone the first time: the password does not show up as you type, not even dots. That is normal and intentional. Just type it and hit enter.

If it worked, the prompt changes, and you are now typing commands on the server. That is it. You are in.

Set up key login so you stop typing passwords

Passwords work, but SSH keys are both more convenient and far more secure, and setting them up takes a couple of minutes. A key is a pair of files, one public and one private. The public one lives on the server, the private one stays on your computer, and they only work together. Nobody can log in without your private key, which is why key login shuts down the constant automated password guessing that every public server gets hit with.

Make a key on your own computer:

ssh-keygen -t ed25519

Press enter to accept the default location. You can set a passphrase or leave it blank. Now copy the public half up to your server:

ssh-copy-id root@your-server-ip

It will ask for your password one last time. After that, try connecting again:

ssh root@your-server-ip

This time it should let you straight in with no password. That is the key doing its job.

A few things that make life easier

Once you are comfortable, a couple of small habits help.

If you find yourself typing the same long connection details constantly, you can set up a shortcut in a file called ~/.ssh/config so you just type ssh myserver instead. Worth looking up once you are connecting often.

To leave the server and return to your own machine, just type exit. The server keeps running, you are simply disconnecting from it.

And once key login is working, the strong recommendation is to turn off password login entirely on the server, which removes the single most common way servers get attacked. That is a small edit to the SSH config on the server, and it is the natural next step after you have keys working.

You have the main skill now

That is genuinely most of what you need. Connect with SSH, set up a key, and you can get into your server reliably and securely from anywhere. Everything else you do, installing software, running services, managing files, happens through this same connection. The first login feels like a milestone because it is one. After that it becomes second nature.