A lab error indicates that Strigo has failed to start, prepare or connect to the machine assigned to your lab. This guide will walk you through the diagnosis for most common causes of such issues.

The rest of this document applies to customers using custom lab images. If you are using one of our pre-configured lab images and are running into lab errors, please contact our technical support and they will help you resolve the issue.

Common errors

Most errors result from incorrect configuration of custom AMIs:

  • Unauthorized access: Our infrastructure could not connect to the instance with the credentials specified when creating the class template. This usually means the wrong user name was specified for the image.
  • Unsupported marketplace AMI: The specified image is listed on the AWS Marketplace and requires a paid subscription, which we do not currently support.
  • AMI not found: Our infrastructure could not access the specified image. The next section provides some guidance on how to diagnose this issue.

Troubleshooting configuration errors

The following applies to Linux as well as Windows images. Please verify that:

  • The AMI ID you have provided is correct;
  • The AMI resides in the correct region (eu-central-1 by default);
  • The AMI is not an AWS Marketplace image. We do not currently support subscription-based AMIs;
  • If the AMI is private, that it is shared with Strigo's AWS account (214514861431).

If you're setting up a Windows image, please also make sure:

  • That Random is selected for the Administrator password; and
  • If at all possible, not to use sysprep. sysprep not only increases the startup time of your lab significantly but can under some circumstances prevent the image from starting up correctly.

If nothing helps

Please don't hesitate to contact our technical support!

Did this answer your question?