Common issues
This page addresses some issues you might encounter when using Nimbo. Some of the errors you encounter might be coming from the AWS SDK directly, so read the error messages carefully.

"Something failed while waiting for the instance to be ready for ssh" or "I can't ssh into the instance"

If this happens, the first thing to rule out is if the security group and instance key you are using give you the permissions to ssh into this instance (if you are unsure about this, ask your AWS admin). If everything is OK on this front, network issues can cause an instance to take longer to be ready for SSH than usual. We recommend just trying again to see if the issue persists.
If you still don't get it to work, get in touch with us so we can look into your setup and help you get back to launching instances non-stop!

"I can't connect to Jupyter on my localhost even though the instance is still running"

If you can't connect to Jupyter lab, it means that the ssh connection used to pipe the remote jupyter server to your localhost has died for some reason. If this is the case, you can restart it with the following command:
ssh -i <instance_key> -o 'StrictHostKeyChecking no' \
-o ServerAliveInterval=5 -o 'ExitOnForwardFailure yes' \
[email protected]<host_address> -NfL 57467:localhost:57467 >/dev/null 2>&1
You can find the host address of your running instances with nimbo list-active.
Last modified 6mo ago