How-to · Intermediate · 20 minutes
How to Connect to a VPS With SSH
Everything you need to a first login done properly, and no password at all by the time you finish — the steps in order, the snag to watch, and the tip our support desk gives everybody.
Straight answer first
The job: a first login done properly, and no password at all by the time you finish. Time to allow: 20 minutes. Skill needed: intermediate.
Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.
Written by the Hosting Seller staff · Checked 1 August 2026
Intermediate
Skill needed
5
Stages to finish
Free
Help included
Tested
On our own kit
You do not need to be technical for this. The walkthrough is written for first-timers, tested on our own platform, and honest about which parts are genuinely fiddly and which are merely unfamiliar.
Rule of the road: read the snag section before you begin rather than after. It is harvested from the tickets of people who did it the other way round.
The whole job at a glance
From start to finish, you will log in with the details you were sent, change that password at once, set up key authentication, test the key before you lock the door and make a normal user for daily work.
Each stage is a few minutes of steady clicking — the time it takes depends mostly on how familiar the control panel already feels. The detailed steps sit further down this page; skim the whole route once before you begin.
The classic snag
Disabling password authentication before checking key login in a separate session. The configuration works perfectly and locks its author out. Keeping a second terminal open is the immunisation, and it costs nothing at all.
It is worth learning because it is not some rare edge case — it is the single most common reason this task turns into a support ticket. Knowing it up front turns the whole job from risky into routine.
The trick worth borrowing
Add the server to ~/.ssh/config with a short alias, the key path and the username. It is 'ssh myvps' forever after, and that file is the difference between using SSH and fighting it.
Small habits like this are the real difference between people who find hosting easy and people who find it stressful. The tools are identical; the working method is not.
What you can skip on a Hosting Seller plan
Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.
And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.
The hosting this guide is written against
Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.
What you pay on day one is what you pay at renewal, so the year-two invoice holds no surprises worth opening early.
- Step by step, tested exactly as printed
- The snag flagged before you reach it
- The dull steps are already automated
- People on hand at any hour if you stall
Why Hosting Seller
On every plan, as standard
Written from real tickets
Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.
Help on the counter
Stuck on step three at midnight? Support answers at any hour, mid-guide included.
Automation where it belongs
SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.
The snag, named early
The classic mistake for this exact job is flagged before step one, so 20 minutes stays 20 minutes.
Works exactly as written
Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.
The undo is always named
Where a step could bite, the guide says so and tells you how to put it back again.
First Steps
From choosing to live
- 1
Log in with the details you were sent
ssh root@your-server-ip from any terminal, Windows included. Accepting the host fingerprint on the first connection is normal — that is the server introducing itself.
- 2
Change that password at once
The initial password that arrived by email has exactly one job: this login. Run passwd and set your own before you do anything else on the machine.
- 3
Set up key authentication
ssh-keygen on your own machine, then ssh-copy-id to the server. Keys are both more convenient than passwords and in a different league for security.
- 4
Test the key before you lock the door
Confirm key login works in a second terminal, then set PasswordAuthentication no. That order is the whole reason people do not lock themselves out.
- 5
Make a normal user for daily work
A sudo-capable non-root account for everyday work, with root kept for emergencies. The audit trail improves the moment you do it.
In the Box
Packed with every plan
- A 99.9% uptime commitment, watched by monitoring day and night
- A domain free for year one when you order annually
- NVMe SSD storage on every shelf, not just the top one
- The renewal price printed on the tag matches the order price
- DDoS filtering handled out at the network edge
- Spam and virus filtering fitted to every mailbox
- Webmail in the browser plus IMAP, POP and SMTP for your own client
- PHP versions picked per site from the panel
- Upgrades apply to the account in place, with no move between plans
- SSH, Git and Composer on the plans built for developers
Across the Counter
The questions we get asked most
What do I use for SSH on Windows?
Windows Terminal and PowerShell include OpenSSH already, so the ssh commands are identical to everywhere else. PuTTY is still there if you prefer it, but nothing needs installing any more.
What is that fingerprint prompt on first connection?
First-contact verification. SSH memorises the server's identity and warns you if it ever changes, which could mean somebody is intercepting the connection. Accept it on the genuine first connect, and investigate properly if it ever warns you later.
Does the price climb when the term is up?
No. What you pay to order is what you pay to renew, year after year. We do not run teaser rates, so there is no year-two ambush waiting in the calendar, and your bookkeeping can treat the hosting line as a fixed number.
How do I pay, and does it bill again on its own?
Orders go through a secure checkout by credit or debit card, and the renewal is taken at the same price you first paid. Every invoice sits in the client area for you to read, and switching auto-renewal off is a toggle in your account rather than a phone call.
What uptime do you commit to, and who is watching?
We commit to 99.9% uptime and watch it continuously. That figure is an operational target rather than a poster line, and the alerting behind it usually has an engineer on a problem before the first customer notices anything is wrong.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Can one plan hold more than a single website?
From the Pro tier upward, yes — several sites, each with its own domain, mailboxes and certificate, all under one account. If those extra sites belong to clients rather than to you, reseller hosting is the better fit: it gives each one proper separation.
Read next
WordPress SEO First Steps
Get the groundwork right so a new site can be found in the first place — beginner level, about an hour.
How to Send Email From WordPress Reliably
Make form notifications and order confirmations actually reach the inbox — beginner level, about 20 minutes.
Domain Names
Search, register and transfer names — year one free with annual hosting.
Laravel Hosting
Composer, SSH and Git deploys on hosting shaped for Laravel apps.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Get online, with no games at checkout.
Every plan carries the essentials other hosts ring up as extras — and support that actually replies.
See the plans