Learning Hub · Intermediate · 20 minutes
How to Connect to a VPS With SSH
Everything you need to first login done right — and passwordless by the end — the steps, the gotcha, and the tip the support desk gives everyone.
The short answer
Goal: first login done right — and passwordless by the end. Time needed: 20 minutes. Difficulty: intermediate.
Below: the exact steps, the classic pitfall, and a pro tip from the support desk. Where our platform automates a step, the guide says so rather than making you do robot work.
Written by the HostingAlly team · Last revised 27 July 2026
Intermediate
Skill level
5
Steps to done
Free
Support included
Tested
On our platform
You don't need to be technical for this — the walkthrough is written for first-timers, tested against our own platform, and honest about which parts are genuinely fiddly versus merely unfamiliar.
Rule of the road: read the gotcha section before you begin, not after — it's harvested from the support tickets of people who didn't.
What you'll do, at a glance
Start to finish, you'll connect with the provisioning credentials, change the password immediately, generate and install ssh keys, test the key, then disable password auth and create a working user.
Each stage is a few minutes of focused clicking — the elapsed time mostly depends on how familiar the control panel already feels. The detailed steps are listed further down this page; skim the whole route once before starting.
The classic gotcha
Disabling password authentication before verifying key login in a separate session — the configuration works perfectly and locks its author out; the second-terminal test is the immunisation ritual.
It's worth internalising because it's not a rare edge case — it's the single most common way this task generates a support ticket. Knowing it in advance converts the whole job from risky to routine.
The pro tip worth stealing
Add the server to ~/.ssh/config with a short alias, key path and user — 'ssh myvps' forever after; the config 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 workflow isn't.
The parts you can skip on our hosting
Several steps in this guide exist because hosting historically made you do them — on our plans, SSL issues itself, backups run daily without being asked, and one-click installers replace manual setup entirely. What remains is the genuinely-yours part of the task.
And when a step misbehaves anyway, support answers around the clock — with the actual fix, not a knowledge-base link and a shrug. Half our best guides started as patterns in the tickets.
The platform this guide assumes
Tutorials age badly when they're written against imaginary hosting. These are written against ours — the same panel, installer and defaults you'll actually see.
Renewal prices match signup prices, so the year-two invoice is the most boring email you'll get from us.
- Step-by-step, tested as written
- The gotcha flagged before you hit it
- Automation covers the boring steps
- 24/7 support if you get stuck
Why HostingAlly
Every plan includes this, whatever you pay
Written from real tickets
Our guides come from the support desk — the gotchas are the ones people actually hit.
Help on standby
Stuck at step three at midnight? Support answers around the clock, mid-guide included.
Automation where it belongs
SSL, backups and installs run themselves here — the guide covers only what's genuinely yours to do.
The gotcha, named early
The classic mistake for this exact task is flagged before step one — so 20 minutes stays 20 minutes.
Works as written
Every step tested on our own platform — no 'your host may vary' hand-waving.
The undo is always named
Where a step could bite, the guide says so and gives the reversal.
Getting Started
How to get going
- 1
Connect with the provisioning credentials
ssh root@your-server-ip from any terminal (Windows included) — accepting the host fingerprint on first connect is normal; it's the server introducing itself.
- 2
Change the password immediately
The emailed initial password's job is one login — passwd sets your own before anything else happens.
- 3
Generate and install SSH keys
ssh-keygen locally, then ssh-copy-id to the server — key authentication is both more convenient and categorically stronger than any password.
- 4
Test the key, then disable password auth
Confirm key login works in a second terminal before setting PasswordAuthentication no — the order that never locks anyone out.
- 5
Create a working user
A sudo-capable non-root user for daily work — root stays for emergencies, and the audit trail improves immediately.
Included
What's covered on our plans
- 99.9% uptime commitment, monitored around the clock
- Free domain for the first year on annual plans
- NVMe SSD storage as standard
- Renewal prices that match signup prices
- DDoS protection at the network level
- Spam and virus filtering on every mailbox
- Webmail plus IMAP, POP and SMTP access
- Per-site PHP version selection
- Upgrades apply in place — no migrations between plans
- SSH, Git and Composer access on developer-friendly plans
FAQ
Your questions, answered
I'm on Windows — what do I use for SSH?
Windows Terminal/PowerShell includes OpenSSH natively — the same ssh commands as everywhere. PuTTY remains available preference, but the built-in client means no installation is needed anymore.
What's the server fingerprint prompt about?
First-contact verification — SSH remembers the server's identity and alerts if it ever changes (which could indicate interception). Accept on the genuine first connect; investigate if it ever warns unexpectedly later.
Do prices go up at renewal?
No — the price you sign up at is the price you renew at. We don't run teaser-rate economics, so there's no year-two ambush to plan around, and your bookkeeping can rely on the number staying put.
How do I pay, and is billing recurring?
Plans are billed by credit or debit card through our secure checkout, with the renewal price matching the signup price. You can see every invoice in the client area, and cancelling auto-renewal is a setting, not a phone call.
Do you monitor uptime, and what do you commit to?
We commit to 99.9% uptime and monitor continuously — not a marketing number but an operational one, with alerting that usually has us fixing issues before customers notice them.
Where are your servers located?
Our hosting infrastructure runs from European datacentres with London at the core, behind server-level caching that keeps cached pages fast worldwide. For most sites, platform quality — NVMe storage, LiteSpeed, sensible server density — matters far more than the datacentre's postcode.
Can I host more than one website on a plan?
On the Pro tier and above, yes — multiple sites with their own domains, email and SSL under one account. If the extra sites belong to clients rather than you, reseller hosting gives each one proper isolation instead.
Planning to switch hosts? Grab the checklist here.
The steps that keep a site migration dull rather than dramatic: what to back up first, how to shift email across without losing a single message, when to touch DNS, and the two mistakes behind nearly every hour of downtime we come across.
Get online without the games.
Every plan includes the essentials others sell as extras — and support that actually answers.
View Domain Names plans