How to Log In to Your PingRack VPS Using SSH

Overview

SSH (Secure Shell) is the standard protocol for remotely managing Linux-based VPS instances. At PingRack, every VPS is provisioned with SSH enabled on port 22 by default, allowing you to administer your server from anywhere.

This guide covers connecting to your PingRack VPS using both password and SSH key authentication across Windows, macOS, and Linux.

Prerequisites

Before you begin, gather the following details from your PingRack Client Area → Services → My VPS:

• VPS IP Address (IPv4 or IPv6)
• SSH Username (typically root for new deployments)
• Root Password or SSH Private Key (if you added one during provisioning)

Note: If you deployed your VPS with an SSH key, password authentication may be disabled for security. Use the corresponding private key to connect.

Connecting from Windows

Option 1: Windows Terminal / PowerShell (Recommended)

Modern Windows includes OpenSSH client natively.

• Open Windows Terminal, PowerShell, or Command Prompt.
• Run:

ssh root@YOUR_VPS_IP

• On first connection, type yes to accept the host fingerprint.
• Enter your root password when prompted (characters won't be visible).

Option 2: PuTTY (Legacy)

• Download and open PuTTY.
• Enter your VPS IP in Host Name (or IP address).
• Ensure Port is 22 and Connection type is SSH.
• Click Open.
• Accept the security alert on first connect.
• Login as root and enter your password.

Option 3: Using an SSH Key with PuTTY

• Convert your OpenSSH private key (.pem or id_rsa) to PuTTY's .ppk format using PuTTYgen.
• In PuTTY: Connection → SSH → Auth → Credentials → browse to your .ppk file.
• Save the session for future use, then connect.

Connecting from macOS / Linux

• Open Terminal.
• Run:

ssh root@YOUR_VPS_IP

• Accept the host fingerprint on first connection.
• Enter your password or, if using a key, ensure the private key is in ~/.ssh/ with correct permissions:

chmod 600 ~/.ssh/id_rsa
   ssh -i ~/.ssh/id_rsa root@YOUR_VPS_IP

Using SSH Keys (Recommended for Security)

SSH keys eliminate password brute-force risk. To set up key-based access on an existing PingRack VPS:

• Generate a key pair (on your local machine):

ssh-keygen -t ed25519 -C "your_email@example.com"

• Copy the public key to your VPS:

ssh-copy-id root@YOUR_VPS_IP

Or manually append ~/.ssh/id_ed25519.pub to ~/.ssh/authorized_keys on the server.

• Disable password authentication (optional but recommended):

Edit /etc/ssh/sshd_config on the VPS:

PasswordAuthentication no
   PubkeyAuthentication yes

Then restart SSH: systemctl restart sshd.

Common Issues & Troubleshooting

| Issue | Solution | |-------|----------| | Connection timed out | Verify VPS is running in PingRack panel. Check firewall: PingRack's cloud firewall allows port 22 by default; ensure you haven't blocked it. Also confirm your local ISP/firewall permits outbound port 22. | | Permission denied (publickey) | Ensure you're using the correct private key (-i flag). Check ~/.ssh/authorized_keys on the VPS for the matching public key. | | Host key verification failed | The VPS was reinstalled or IP changed. Remove the old entry: ssh-keygen -R YOUR_VPS_IP. | | Password not working | Confirm you're using the current root password from the PingRack Client Area. If you reset the password via the panel, allow a minute for it to propagate. | | SSH service not responding | Reboot the VPS from the PingRack dashboard or use the VNC Console to check systemctl status sshd. |

PingRack-Specific Tips

• VNC Console: If SSH is completely inaccessible, use the VNC Console button in the PingRack Client Area for out-of-band access.
• Firewall Management: Manage cloud-level firewall rules under Networking → Firewall in the PingRack panel. Ensure TCP port 22 is allowed for your IP or 0.0.0.0/0.
• OS Reinstall: Reinstalling the OS via the PingRack panel regenerates SSH host keys—expect a fingerprint warning on next connect.
• IPv6: PingRack VPS instances support IPv6. You can connect via ssh root@YOUR_IPv6_ADDRESS if your local network supports IPv6.

Next Steps

Once logged in, consider:

• Creating a non-root sudo user for daily administration.
• Configuring a firewall (UFW, firewalld, or PingRack's cloud firewall).
• Setting up automatic security updates.
• Installing monitoring agents.

Need Help?

If you continue to experience SSH connectivity issues, open a Support Ticket from your PingRack Client Area or email support@pingrack.com with your VPS ID, the error message, and steps you've already tried.