Instance recovery may fail with the "Address xxx.xx.xx.xx is in use" error
Issues:
When attempting instance recovery, it may fail with the following error in the recovery log:
Error - First step (launching instance) failed. Reason: Address xxx.xx.xx.xx is in use.
Solution:
This usually happens because you are trying to restore an existing instance, and its original IP is still in use.
To resolve this issue, please select "Basic Options" in the Instance Recovery screen, and clear the "VPC Assign IP" field.
Once you have cleared this field, a new IP will be assigned to the restored instance automatically.
Related Articles
Recovery fails with "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is enabled for ENA."
When attempting a windows instance recovery with ENA enabled, it may fail with the following error: "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is ...VPC Clone may fail with "Template validation has failed"
VPC Clone may fail with the error "Template Validation Failed. Failure reason: S3 error. The bucket you are attempting to access must be addressed using the specified endpoint. Please Send all future requests to this endpoint. For more ...Instance recovery may fail with the error "You are not authorized to perform this operation"
Instance recovery may fail with the error "You are not authorized to perform this operation" : ERROR: recover_ebs_based_instance(.\cpmserver\cpm\recovery.py:749) Run_instance failed. Exception: EC2ResponseError: 403 Forbidden <?xml version="1.0" ...Instance recovery may fail with the following error: "Recovery Operation Failed. Reason: EBS-optimized instances are not supported for your requested configuration."
Issue: Instance recovery may fail with an error: Recovery Operation Failed. Reason: EBS-optimized instances are not supported for your requested configuration. Please check the documentation for supported configurations. Cause: This issue may appear ...Recovery of an encrypted volume may fail: "Not authorized to use key"
Performing a cross account recovery of an encrypted volume, or of an instance containing an encrypted volume may not work if the target account cannot access the encryption key from the source account. Error may appear in the CPM Server log as below: ...