Skip to main content
Claim your .com from $2.99 — free WHOIS privacy included

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.

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.

Network of cloud servers powering VPS infrastructure

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

What you get with every plan

Written from real tickets

Our guides come from the support desk — the gotchas are the ones people actually hit.

The undo is always named

Where a step could bite, the guide says so and gives the reversal.

Automation where it belongs

SSL, backups and installs run themselves here — the guide covers only what's genuinely yours to do.

No jargon tax

Terms are explained in place or linked to the glossary — nothing assumes you already know.

Works as written

Every step tested on our own platform — no 'your host may vary' hand-waving.

Help on standby

Stuck at step three at midnight? Support answers around the clock, mid-guide included.

Getting Started

How to get going

  1. 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. 2

    Change the password immediately

    The emailed initial password's job is one login — passwd sets your own before anything else happens.

  3. 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. 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. 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

  • Email accounts on your own domain
  • 24/7 support from real people
  • Free website migration handled by our team
  • One-click installer for WordPress and 400+ apps
  • 99.9% uptime commitment, monitored around the clock
  • cPanel — the industry-standard control panel
  • Per-site PHP version selection
  • Free domain for the first year on annual plans
  • DDoS protection at the network level
  • Daily automatic backups with self-service restores

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.

Is SSL really included at no cost?

On every plan, with no exceptions — certificates are issued automatically when your domain points to us and renew themselves before expiry. The encryption is identical to paid DV certificates; paid tiers exist only for wildcard convenience or organisation-level validation.

Is there a money-back guarantee?

Yes — try the hosting properly and if it doesn't fit, the refund process is a request, not a retention gauntlet. Domain registrations are the one standard carve-out, since registries make those non-refundable the moment they're placed.

Where is your company based?

HostingAlly is a trading name of Bohzo Ltd, a company registered in England and Wales — a real, verifiable business with published terms under English law, which is worth checking about any host before you hand them your domain.

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.

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.

Start with hosting that has your back.

From your first site to a fleet of servers, the upgrade path is an account change, not a migration.

See Hosting Plans