Skip to content

Guide / Getting started

How to connect to your server with SSH

Step-by-step guide to connecting to a Linux server over SSH from macOS, Linux and Windows, and setting up key-based login.

SSH (Secure Shell) is the standard way to manage a Linux server remotely. This guide covers connecting from macOS, Linux and Windows, and switching to key-based login.

What you need

  • The server's IP address (or a hostname pointing to it).
  • A username — often root for the first login.
  • The password or SSH key for that user, from the access details provided when your server is handed over.

Connect from macOS or Linux

Open a terminal and run:

ssh root@203.0.113.10

Replace 203.0.113.10 with your server's IP address. If SSH listens on a non-standard port, add -p:

ssh -p 2222 root@203.0.113.10

Connect from Windows

Current versions of Windows 10 and 11 include an OpenSSH client. Open PowerShell or Windows Terminal and use the same command:

ssh root@203.0.113.10

If the ssh command isn't available, enable "OpenSSH Client" under Optional features in Windows settings, or use a graphical client such as PuTTY.

The first connection

On your first connection you'll be asked to confirm the server's host key fingerprint. Type yes to continue; the key is saved in ~/.ssh/known_hosts. If you later see a warning that the host key has changed, stop and confirm why before continuing — it can indicate a reinstalled server or an interception attempt.

Switch to key-based login

SSH keys are more secure and more convenient than passwords. On your own computer, create a key pair:

ssh-keygen -t ed25519 -C "you@example.com"

Accept the default location and set a passphrase. Then copy the public key to the server:

ssh-copy-id root@203.0.113.10

On Windows, where ssh-copy-id isn't available, append the contents of your .pub file to ~/.ssh/authorized_keys on the server. Test that you can log in without a password, then consider disabling password logins — see First steps to secure a new Linux server.

Never share your private key. Only the .pub file goes on servers. The private key stays on your computer, protected by its passphrase.

Troubleshooting

  • Connection timed out — check the IP address and port, and whether a firewall blocks SSH.
  • Connection refused — the SSH service may not be running, or is listening on another port.
  • Permission denied — check the username, password or key. Run ssh -v for detailed output.

If you're still stuck, email support@theclouders.com with your server's IP address and the exact error message.

Need help with this on your server?

Email support