ZoophostDocs

First login and SSH

Find your credentials in the console, verify the host key fingerprint, sign in over SSH and rotate the root password.

Cloud VPS3 min read

When a VPS is ready, the console shows its connection details and the welcome email repeats them.

Open the server

Console → Servers → your server. The Connection details card lists:

Field Use
IPv4 address The address you connect to
IPv6 address Optional second address
SSH port Usually 22; use it if it differs
Username Usually root
Hostname The machine's hostname
Operating system What was installed
Location Where the machine runs
Bandwidth Monthly transfer allowance
Reverse DNS The PTR record, if configured
Control panel External panel link, when the provider supplies one
VNC console Out-of-band console link, when configured
Host key fingerprint Verify this on first connect

The card also offers the full command with a copy button:

ssh [email protected] -p 22

Sign in

With a password

The initial root password is in the welcome email. On first connect, SSH asks you to confirm the host key fingerprint — compare it with the Host key fingerprint field in the console before accepting.

Change the root password immediately:

passwd

Then create a normal user for day-to-day work:

adduser deploy
usermod -aG sudo deploy

With an SSH key

If the order included an SSH public key, the server has it installed and password login may be disabled. Connect with the matching private key:

ssh -i ~/.ssh/id_ed25519 [email protected]

If the key is not accepted, confirm you are using the private half of the key you supplied, and that the permissions are correct:

chmod 600 ~/.ssh/id_ed25519

Reveal or reset the password

The console stores the password so you can retrieve it later:

  • Show password — owner or admin only. Every reveal is logged.
  • Update password on record — updates the copy in the console. It does not change the password on the machine. Use passwd on the server for that.
  • Reset root password under server actions — asks the team to set a new root password and email it to you. Use it when you are locked out.

Prefer SSH keys over passwords for anything internet-facing. Password authentication on port 22 attracts constant automated attempts.

Harden the server

A short baseline for a new VPS:

# Updates
apt update && apt upgrade -y

# Firewall: allow SSH and HTTP(S), drop the rest
apt install -y ufw
ufw allow 22/tcp
ufw allow 80,443/tcp
ufw enable

# Fail2ban for SSH brute force
apt install -y fail2ban
systemctl enable --now fail2ban

If you change the SSH port, open the new port in the firewall before restarting SSH, or you will lock yourself out.

If you cannot connect

  1. Confirm the server is running. The console state should be active or running.
  2. Ping the address. No reply can mean the provider blocks ICMP; try the SSH port instead.
  3. Check the port. ssh -p <port> or nc -vz <ip> <port>.
  4. Read the error. Connection refused is usually a service/firewall problem; Connection timed out is usually network or firewall dropping packets.
  5. Use rescue mode. If the machine boots but SSH is broken, request Rescue mode from server actions.
  6. Reset the root password. If credentials are the problem, request a reset.

Never reinstall the OS to fix an SSH problem unless you have accepted losing the disk.

Next

  • ssh
  • login
  • root
  • password
  • host key
  • fingerprint
  • credentials

Ready to use this

KVM machines with dedicated vCPU and full root access.

  • Root access from the first tier
  • Backups are a separate add-on
See Cloud VPS plans
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.