Skip to content

Connect to your server

You manage a VPSTitan server over SSH as root. VPSTitan servers are self-managed: the operating system and everything you install on it are yours to look after, unless you added Managed Support.

Your welcome email has everything you need. You can also find it in the client portal:

  1. Sign in to the client portal and open the server from your list of services.

  2. On the service’s overview, the Server card shows its Hostname, IP addresses, Location, Operating System and Username (root).

  3. If the server has a generated password, select Show beside Server Password to reveal it, and Hide when you are done.

If you added an SSH key when you ordered or reinstalled, there is no root password: root signs in with your key only.

Open a terminal on your computer. macOS, Linux and Windows 10 or later include an SSH client.

Terminal window
ssh root@203.0.113.10

Replace 203.0.113.10 with your server’s IPv4 address or its hostname.

  • With an SSH key, your computer offers the key automatically. If it is not in the default location, add -i and the path to your private key, for example ssh -i ~/.ssh/my_key root@203.0.113.10.
  • With a password, paste the root password when asked. Nothing appears on screen while you type or paste it.

The first time you connect, SSH shows the server’s fingerprint and asks whether to continue. Type yes.

A reinstalled server has a new fingerprint, so SSH warns that the host key has changed. After a reinstall, remove the old entry with ssh-keygen -R 203.0.113.10 (your address), then connect again. If you see that warning without having reinstalled, stop and contact support before you sign in.

Every new or reinstalled server starts with:

  • SSH access for root: with your SSH key and password logins turned off, or with the generated root password if you did not add a key
  • fail2ban, which temporarily blocks addresses that repeatedly fail to sign in over SSH
  • Automatic security updates, installed daily. On Arch Linux and Alpine Linux, the daily job installs all available updates, not only security fixes
  • The hostname from your welcome email

A new server also gets reverse DNS set to that hostname. Reinstalling leaves reverse DNS as it was.

The setup does not change the firewall, so its starting state depends on the distribution. Check it before you rely on it, for example with ufw status on Ubuntu or firewall-cmd --state on the Red Hat family.

New servers are scanned by bots within hours of going online. Do these in your first session:

  1. Update the system. Install all pending updates with your distribution’s package manager, for example apt update && apt upgrade on Ubuntu and Debian, or dnf upgrade on AlmaLinux, Rocky Linux, CentOS Stream and Fedora.

  2. Sign in with a key, not a password. If you used a password, add your public key to /root/.ssh/authorized_keys (or run ssh-copy-id root@203.0.113.10 from your computer), then open a new terminal and check that the key works before you go further.

  3. Turn off password logins. Once the key works, set PasswordAuthentication no in the SSH configuration and restart the SSH service. Keep your current session open until a new key login succeeds.

  4. Set up a firewall. Allow only the ports you use, and always allow SSH (port 22) before you enable it, for example with ufw allow OpenSSH then ufw enable on Ubuntu, or firewalld on the Red Hat family.

  5. Plan your backups. Add automatic backups, and keep your own copy of important data off the server.

Sheernox cannot recover a lost private key, and the password on the overview is only the one generated at setup. If you can no longer sign in:

  • If you still have another working login, add a new key or set a new password from there with passwd.
  • Otherwise, open a support ticket, or reinstall the server with a new key or a new generated password. Reinstalling erases all data on the server.