SSH Keys vs Password Login
Short answerPassword login is fine for first access. SSH keys are stronger for ongoing admin: your private key stays on your computer, the server stores only the public key, and you can later disable password SSH to reduce brute-force risk.
Overview
This article compares the two common ways to authenticate over SSH on a VPSGrid Linux VPS. It is not a product comparison (VPS vs dedicated). For setup steps, see How to Enable SSH Key Authentication. SSH basics: What Is SSH?.
Password login
- You type a password when connecting:
ssh root@YOUR_PRIMARY_IP - Pros: simple for first login; works from any machine if you know the password
- Cons: passwords can be guessed/reused; bots constantly try SSH passwords on public IPs
- Best for: initial access right after provisioning, emergency recovery, or short-lived test VMs
SSH key login
- You create a key pair locally; the public key is installed on the VPS; the private key never leaves your machine (except backups you control)
- Pros: much harder to brute-force; convenient with an SSH agent; pairs well with disabling password auth later
- Cons: you must protect the private key; lost keys without a backup can lock you out (use console to recover)
- Best for: day-to-day administration of production Linux VPS servers
Side-by-side
| Factor | Password | SSH key |
|---|---|---|
| First-time ease | Highest | Needs one-time setup |
| Brute-force resistance | Weaker on public SSH | Strong when passwords disabled |
| Phishing / reuse risk | Higher if password reused | Lower (key file + passphrase) |
| Moving to a new laptop | Just remember password | Copy/import private key securely |
| Recommended long-term | No (alone) | Yes |
Practical recommendation on VPSGrid
- Connect once with the welcome password
- Generate and install an SSH key
- Confirm a second SSH session works with the key
- Only then consider disabling password authentication
- Keep console/noVNC available before locking down passwords
# Typical key generation on your computer
ssh-keygen -t ed25519 -C "vpsgrid-vps"
# After the public key is installed on the VPS, test:
ssh root@YOUR_PRIMARY_IPImportant notes
- Windows VPS plans normally use RDP, not SSH password/key login
- A key passphrase protects the private key if the laptop is stolen — use one
- Never paste your private key into tickets, chat, or public repos
Frequently Asked Questions
Can I use both password and key login?
Yes. Many servers allow both until you intentionally disable PasswordAuthentication in sshd_config after keys work.
Is a long password as good as a key?
A strong unique password is better than a weak one, but keys (especially with password auth disabled) are still the better long-term default for internet-facing SSH.
I lost my private key
Use the browser console to log in (if password login still works) or recover access, then install a new public key. Do not disable passwords until you have a working key and console path.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with your service ID and whether key login, password login, or console still works.
Was this answer helpful?
