My domain - with an elaborate WordPress site has gone missing

0

We created 2 instances and built a WordPress website on one of them - and set it so that 'aarkt.com' "pointed" to that WordPress site.

By mistake we changed the IP address of the 'A' record for aarkt.com to be the IP address of the "empty" instance. The site disappeared (no surprise).

We changed the IP address of the 'A' record for aarkt.com back to the instance where we had built the WordPress site but the website did not return. Various attempts to locate that WordPress install have failed. And aarkt.com still points to "nowhere".

We do not have "AWS CloudTrail console" - but that should be irrelevant given that we know the correct/original IP address anyway.

Detail: The 2 instances that were created were: a) Instance ID i-06a5e30bd17282e83 with Public IPv4 address of 3.12.166.41 b) Instance ID i-0d1bb4797af9333f0 with Public IPv4 address of 3.80.147.131

We changed the 'A' record IP address from 3.12.166.41 to 3.80.147.131 and aarkt.com vanished. Of course: Instance ID i-0d1bb4797af9333f0 (with Public IPv4 address of 3.80.147.131) has nothing in it.

The problem is that when we changed the IP address of the 'A' back to 3.12.166.41, the WordPress install that we set up in Instance ID i-06a5e30bd17282e83 did not re-appear.

Obviously we must have changed something else by accident. We were attempting to set up an SSL certificate at the time, maybe "something got in the middle" so to speak.

The ultimate goal of course is to "get the site back" - to have 'aarkt.com' point to the WordPress site we set up in instance a (see above).

A good start might be getting access to the (rather elaborate) WordPress site that was set up using instance a, and then worry about making aarkt.com point there.

Note: we do not have "AWS CloudTrail console" or any other tracking program set up.

asked a year ago242 views
1 Answer
0

You should login to the AWS console and check the public IP addresses of the instances and compare to your notes. If you stop an instance and then later start the instance the public IP can/will change. If you intend to have a static IP address that does not change when the instance is stopped you will need to allocate an Elastic IP (EIP) and then associate it with the instance. The below link provides deeper info on Elastic IPs.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html

profile pictureAWS
EXPERT
iBehr
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions