Troubleshoot instance startup problems

There are several possible reasons for a server operation such as “Server Build”, “Server Start”, “Server Resize” and others to finish with an “Unexpected Error” message or with a server being in the “Pending” state for long period of time. Use the list below to identify what might have gone wrong.

Server remains in “Pending” state

For every server operation executed, Bitnami Cloud Hosting ensures that the server is in the correct, ready-to-run state. This means that the Bitnami Cloud Hosting dashboard has to wait for the server to be in that specific state to continue the process of setting up applications on it. Sometimes, the AWS EC2 API returns a response that the server is “Pending” when in fact the server is available. In these cases, the server operation may take more time than usual. This part of the process depends on the responsiveness of AWS.

Static IP address was assigned to your instance

Once the “change IP address” operation is executed, Bitnami Cloud Hosting waits for the server to respond from new IP address. This sometimes takes additional time and is dependent on the responsiveness of AWS.

Your AWS credentials are not valid

This error could occur if:

  • You use special AWS IAM user credentials and that IAM user account does not have the permissions required by Bitnami Cloud Hosting. As a result, Bitnami will not be able to execute operations on your behalf. To resolve this, use a different IAM account or give the account elevated permissions.

  • You changed or reset your AWS Access Key ID and Secret Access Key. To resolve this, update these credentials in Bitnami Cloud Hosting.

Required ports are not open

Please make sure that ports 22 and 80 are open in your AWS security group settings. If you need to keep those ports closed, you must at least open them for the IP address Bitnami uses these ports to check if the server is available and to collect monitoring data.

For more tips on troubleshooting your Bitnami Cloud Hosting instance, review our troubleshooting guide.

Last modification September 5, 2018