First SSH login to your VPS

In this guide: First SSH login to your VPS. How to connect and common errors.

Commands below target a typical Linux setup (Ubuntu/Debian). On other distros, package/service names may differ.

If something goes wrong: check the service is running, listening on the expected port, and that your firewall allows the connection. For web services, `nginx -t` and `journalctl -u nginx` are good starting points. Tip: if it fails, add `-v` to SSH (e.g. `ssh -v root@IP`) to see where the connection breaks.

After completing the steps below, verify the result: service status, logs, and network reachability. This saves hours when an issue shows up later.

Below you’ll find a quick checklist, verification commands, and common pitfalls. This helps you not only “do it”, but also confirm what a correct outcome looks like.

Quick checklist

• Confirm you are connecting to the correct IP.
• Ensure SSH is reachable (port 22) and not blocked by a firewall.
• After first login, update the system and create a non-root user.
• Make one small change at a time and verify the result immediately.
• Keep notes of what you changed (file/command/time).

Verify the result

# Verify / sanity checks
whoami
uname -a
ip a | head -n 50
ss -lntup | head -n 50

Common pitfalls

• Mixing up IP/username when using SSH.
• Skipping updates/basic hardening after first login.

Linux servers are typically accessed via SSH.

ssh root@YOUR_SERVER_IP

• Permission denied: wrong credentials or password auth disabled.
• Connection timed out: port 22 is not reachable (firewall/routing/wrong IP).
• REMOTE HOST IDENTIFICATION HAS CHANGED: OS reinstall or MITM risk. Only fix known_hosts if you are sure.