Troubleshooting

You may experience issues when launching Solodev within your AWS account. This can understandably be frustrating and the result of a number of issues ranging from user permission errors within a given AWS account or unavailable AWS services. If multiple stack attempts fail, please use these instructions to further troubleshoot and provide the Solodev team with as much insight into your issues as possible.

CloudFormation Errors

If monitoring your stack creation through CloudFormation, you should be able to see at what specific step the stack fails (EFS, RDS, EC2, etc). Make note of these types of errors for further troubleshooting.

Disabling Rollbacks

For more granular troubleshooting, when launching a stack you can disable rollbacks. For Pro & Enterprise versions, you will then be able to see specific issues in AWS OpsWorks.

Viewing Failure Logs via OpsWorks

If Rollbacks are disabled, you can navigate to OpsWorks in AWS and see the failed stack. From there you can view the "failure log" to see specifically where the stack creation process fails.

Common Cloud Formation Errors

DELETE_FAILED: This error commonly occurs when deleting a stack. To resolve this issue, users should empty and delete the S3 Bucket associated with the stack.