Introduction

This article addresses the issues related to not being able to SSH into Crusoe Cloud VMs. In some cases, after restarting a VM, you may be unable to SSH into the instance due to errors such as -

port 22 (tcp) failed: Connection refused

Prerequisites

• CLI
• Serial-console
• SSH access to the compute VMs 

Solution

1. Serial-console into the VM using the CLI. More information on serial-console access can be found here.

crusoe compute vms serial-console --name $VM_NAME --project-id $project_id

2. If you are able to get in without a prompt for a password, the VM has likely booted in emergency mode. Refer to How-To-Recover-a-VM-booting-in-Emergency-Mode article to resolve the issue.

Connecting to serial console... 
Press ENTER to continue and ~. to exit. 
user@hostname:~#

3. If the VM has not booted in emergency mode, check the status of sshd service.

sudo systemctl status sshd

4. You can also try restarting the sshd daemon. 

sudo systemctl restart sshd

5. If the sshd daemon starts successfully, verify you can connect to the VM via SSH.

ssh ubuntu@<IP_ADDR>

If you are still experiencing issues connecting to your Crusoe Cloud VM, please reach out to customer support.