Below is a compilation of issues you may encounter when using Nimbus, and workarounds or solutions where possible. This will be added to as time goes on, so we recommend checking here first if you encounter a problem.

Creating an Instance

Binding failed for port

When creating an instance through the dashboard, it starts to create the instance, but then fails with the following error message in the top right corner:

"Error: Failed to perform requested operation on instance "<instance_name>", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance <instance_id>. Last exception: Binding failed for port <port_id>, please check neutron logs for more information.]."

This usually means that you have attempted to to set "public external" as the primary network for your instance. This will always fail, as you should be using a private network for all of your instances (which you have to set up before creating any instances). For information on setting up a private network (and a virtual router for external access), please refer to Nimbus - Launching an Instance

Accessing an Instance

SSH Access - permission denied

Once your instance is created, when attempting to SSH into the instance, you may receive the following error:

Permission denied (publickey).

There may be a number of possible reasons for this:

• First, ensure that you have added your SSH key (either by generating a new key in the dashboard, or importing an existing one).
• Second, make sure that you have set up a security group to allow SSH access into your instance. For more information on this, refer to Nimbus - Launching an Instance
• Ensure that your SSH key on the machine you are connecting from has suitable permissions set. In particular, make sure that the private key can only be read by your personal account, and no-one else (the SSH key filename in the example below may differ, depending on your setup):

chmod 600 ~/.ssh/id_rsa

• If you have an SSH key par through the Nimbus dashboard, you may instead want to try creating the SSH key on your local machine, then importing the public key into Nimbus. The SSH key par can be generated locally with the command "ssh-keygen". Be sure to ONLY import the public key on Nimbus; the private key must remain where it is.