Your Fast Hive VPS comes with full root access and deploys in around 55 seconds. SSH is how you reach it. This guide covers connecting from Windows, macOS and Linux, setting up key-based authentication so you can stop using passwords entirely, and diagnosing the handful of errors that account for nearly every failed connection.

What you need
  • Your VPS IP address - shown on the service page in My Products & Services.
  • The root password from your deployment email, or an SSH key you supplied at order time.
  • A terminal. Windows 10 and 11 include one; macOS and Linux have one built in.

Connecting for the first time

macOS, Linux, and Windows PowerShell or Terminal

ssh root@your.vps.ip.address

On the first connection you are asked to accept the server's host key fingerprint. Type yes. This fingerprint is remembered, and a warning if it ever changes is a genuine security signal, not noise.

Windows with PuTTY

  1. Download and open PuTTY.
  2. Enter the VPS IP address in Host Name, leave the port as 22, and make sure SSH is selected.
  3. Type a name under Saved Sessions and click Save so you do not retype it every time.
  4. Click Open, accept the host key, and log in as root.

Set up key-based authentication

Keys are both more secure and more convenient than passwords. A password can be guessed; a key practically cannot.

Step 1 - Generate a key pair on your own machine

ssh-keygen -t ed25519 -C "your-email@example.com"

Accept the default location and set a passphrase. The passphrase protects the key file if your laptop is stolen; it is not sent to the server.

Step 2 - Copy the public key to the VPS

# The easy way
ssh-copy-id root@your.vps.ip.address

# If ssh-copy-id is unavailable
cat ~/.ssh/id_ed25519.pub | ssh root@your.vps.ip.address \
  "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"

Step 3 - Test before you lock anything down

Open a second terminal and connect with the key while the first session stays open. Only once the key login works should you consider disabling password authentication.

Always keep one working session open while changing SSH configuration. If a change breaks logins, the open session is how you undo it. Without it, you are locked out of your own server.

Windows: converting a key for PuTTY

PuTTY uses its own format. Open PuTTYgen, click Load, select your private key file, then Save private key as a .ppk. In PuTTY, point Connection → SSH → Auth → Credentials at that file.

Making life easier with an SSH config file

Create ~/.ssh/config on your own machine:

Host myvps
    HostName your.vps.ip.address
    User root
    Port 22
    IdentityFile ~/.ssh/id_ed25519
    ServerAliveInterval 60

You can then connect with just ssh myvps, and the same alias works for scp and rsync.

Transferring files over SSH

# Upload a file
scp ./local-file.tar.gz root@your.vps.ip.address:/root/

# Download a file
scp root@your.vps.ip.address:/var/log/nginx/error.log ./

# Sync a directory
rsync -avz ./site/ root@your.vps.ip.address:/var/www/site/

Graphical clients such as FileZilla and WinSCP also speak SFTP over the same port 22 connection, using the same key.

Troubleshooting

Error Cause and fix
Connection refused Nothing is listening on that port. The SSH service is stopped, or the port was changed. Reboot from the client area, or use the console to check systemctl status sshd.
Connection timed out A firewall is dropping the packets - either the server's own firewall after a misconfigured rule, or your office network blocking port 22. Test from mobile data to tell them apart.
Permission denied (publickey) Password authentication is disabled and your key is not accepted. Check you are offering the right key with ssh -i ~/.ssh/id_ed25519 -v root@ip.
Permission denied (password) Wrong password, or root login is disabled. Reset the root password from the client area.
REMOTE HOST IDENTIFICATION HAS CHANGED Expected after a rebuild or reinstall. Remove the stale entry with ssh-keygen -R your.vps.ip.address. If you did not rebuild, stop and investigate.
UNPROTECTED PRIVATE KEY FILE Your private key is readable by others. Run chmod 600 ~/.ssh/id_ed25519.
Key set up correctly, still asks for a password Permissions on the server are wrong. ~/.ssh must be 700 and authorized_keys 600, owned by the user. SSH silently ignores loose permissions.
Session drops after a few minutes idle Add ServerAliveInterval 60 to your SSH config.
Locked out completely Use the console access in the client area, which connects below the network layer and works even when SSH does not.

When a connection fails for no obvious reason, add -vvv for verbose output. It usually names the exact step that failed:

ssh -vvv root@your.vps.ip.address

Frequently asked questions

Where do I find my VPS IP address and root password?

On the service page under My Products & Services, and in the deployment email sent when the server was created.

Can I change the SSH port?

Yes, and it meaningfully reduces automated scanning noise. Change Port in /etc/ssh/sshd_config, open the new port in the firewall before restarting SSH, and keep a session open while you test.

Should I log in as root?

For initial setup, yes. After that, create a normal user with sudo rights and disable direct root login. The VPS hardening article covers this.

Can I use SSH from a phone or tablet?

Yes, with any of the common mobile SSH clients. Import your private key rather than storing the root password on the device.

Does my VPS have cPanel?

Only if you ordered it with the server. A plain VPS gives you a bare distribution - Ubuntu, Debian, AlmaLinux, Fedora or CentOS Stream - and SSH is your primary interface.

Cannot reach your server? Open a ticket with Technical Support at My Support Tickets with the VPS IP, the exact error, and the output of ssh -vvv. Never include your private key or root password in a ticket.
Помог ли вам данный ответ? 0 Пользователи нашли это полезным (0 голосов)

Powered by WHMCompleteSolution