An error may be recieved stating “A Problem Occurred (500)” when restoring an instance with multiple NIC’s
When trying to restore an AWS instance that utilizes multiple NIC’s, sometimes an error will return stating the below:
“A Problem Occurred (500) Sorry, but there was an error while processing your request”
Below is a screenshot of the error being exhibited:
Resolution: Please install the patch attached to this KB article. Please note the instance will not be restored with the additional NIC's,
they will need to be re-attached to the restored instance manually.
Related Articles
CPM Server may display error "Problem Occurred (500)" during initial configuration
CPM Server may display error "Problem Occurred (500)" during initial configuration: A Problem Occurred(500) Sorry, but there was an error while processing your request The most likely reason for this is lack of some of the permissions required for ...After restoring a RHEL 7.x instance, yum update stops working
After restoring a RHEL 7.x instance, yum update stops working: [root@hostname~]# yum update Loaded plugins: amazon-id, rhui-lb, search-disabled-repos epel/x86_64/metalink ...Instance restore may be marked "successful", despite failing to restore a volume
Issue: A cross account restore of an encrypted volume or instance may be marked successful, however a Volume has failed to restore. Fix: If you face this issue, please upgrade to latest 2.X.X version Reference defect number – N2WS-1168, fixed in ...Volume/instance restore may fail with Exception "The volume vol-12345678 does not exist"
If Volume/instance restore of an existing volume fails with the following exception in the Recovery log: "Exception: The volume '<volume-id>' does not exist", please upgrade to latest 2.X.X to resolve the issue. Reference defect number - ff4e8ae447, ...Restoring an instance may not restore tags
If a restored instance is created without its tags, please search the server log for the following print: ERROR: add_tags_to_resource(aws_utils.py:<line_number>) Add tag failed for Instance (<instance_id>). Exception: EC2ResponseError: 400 Bad ...