Why can't I reach my VM?

Work through a connection problem step by step, from the panel down to your VM. What each PuTTY error means, and when to open a ticket.

Updated 6 November 2026

Work down from the top. Each step rules out one part of the path, and most problems turn up early on.

1. Check the panel

Open the VM's page and look for:

  • Is it running? If not, press Start.
  • Is it being worked on? A backup, restore or another power action can hold things up. Give it a minute.
  • Is it in rescue? Look at the Boot tab. A VM in rescue mode isn't running your system.
  • Does it have an SSH port? The Ports tab should show the address. If it says This VM has no SSH forward, press Add SSH forward.
  • Are you using the right address? Use the public address and port from the Info tab, not the private one.

2. Find your error

What PuTTY says What it means What to do
Connection timed out Nothing answered Go to step 3
Connection refused You reached the VM, but nothing is listening on that port SSH isn't running. Go to step 4
Network error: Software caused connection abort The connection was cut off Often a firewall or a restart. Try again, then go to step 3
Server refused our key You reached SSH, but it didn't accept your key Go to step 5
No supported authentication methods available Password login is off, and you didn't offer a key Pick your .ppk under Connection > SSH > Auth > Credentials
Access denied Wrong username or password Check the Username on the Info tab
Potential security breach / host key mismatch The server's identity has changed See step 6

3. Check the firewalls

  1. The panel: on the VM's Firewall tab, is TCP port 22 allowed, above anything that would block it? Remember, it's 22 here, not your public port. See firewall rules.
  2. Check the status on that same tab says Applied and confirmed.
  3. Inside the VM: use the console and see if your own firewall is blocking it, with sudo ufw status or sudo firewall-cmd --list-all.

4. Look inside the VM

Open the Console tab. It works even with no network. If you can't log in, because you've no password set, rescue mode can set one.

systemctl status ssh
ip addr
ip route
ping -c 3 1.1.1.1

Some systems call the service sshd. Check that:

  • SSH is running. If not, try sudo systemctl restart ssh, and read the error if it won't start.
  • Your VM has its private address, as shown on the Info tab.
  • It has a default route via the gateway, ending in .1.
  • The ping works, which shows the VM can reach the internet.

If the network looks wrong and you've changed it recently, change it back. If you can't see the problem, cloud-init can write the settings again.

If the console shows that the VM hasn't finished booting, or is stuck on an error, you need rescue mode.

5. If your key is refused

  • The username. You need the one on the Info tab, not root.
  • The right file. Check that PuTTY is pointed at the right .ppk.
  • The key is on this VM. Keys only reach a VM when it's built. SSH keys on the Info tab says how many it was given. A key you added to your account later has to be added by hand.
  • File permissions. On the VM, ~/.ssh must be 700 and authorized_keys must be 600, and both must belong to your user.

To get in meanwhile, use Turn on SSH password login on the Info tab.

6. If the host key has changed

PuTTY warns you when a server's identity changes. There's normally an innocent reason:

  • You've just reinstalled the VM.
  • You're in rescue mode, which has its own key. Check it against Rescue's SSH host key on the Boot tab.
  • You've restored a backup, which can make the system create new keys.

If you haven't done any of those, don't accept it until you know why. Check through the console, with ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub.

7. Opening a ticket

If everything on your side looks right, open a ticket on the panel and choose your VM on the form. Tell us what you tried, and the exact error.

Cloud support covers connectivity only, meaning your VM can't be reached because of a problem on our side. We can't configure your system, install software or fix what runs on it. Cloud is also a beta on shared hardware at home, so check whether the site notice or our Discord mentions an outage.