WordPress Site on AWS Not Available Anymore

I am using AWS in combination with Bitnami. On top of that I’ve installed WordPress

Please do not create duplicate topics; continue with this. Your other topic has been removed.

My AWS instance is running again, but I can’t reach the site. Even if I click on and open “public IPv4 address” shown in the instance I get this error “Hmmm… can’t reach this page <<my_site_ip_adress>> refused to connect.”
I noticed IP address has changed. Not only that it is not available over browser.

Note that, by default, AWS EC2 (and LiteSail) instances have ephemeral IP addresses. This means that the IP addresses are not permanently assigned to the instance: they are pulled from a pool of IPs, and the IP may change when you stop/restart/hibernate the instance.

But there’s a simple solution to prevent this: simply attach an Elastic IP to your instance. Please see: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html

I don’t know how Bitnami works, especially how it uses the instance’s IP address and how the change in IP affects it. But if your instance is unavailable even via its supposed IP address, that’s unrelated to WordPress. That’s an infrastructure problem, I’ll suggest you seek help from your infrastructure provider.

If you can provide your domain name as well as both the old and new IPv4 addresses, I could run some basic connectivity tests to better understand how the change in IP may be contributing to your problem.

Good luck!

@gappiah thanks for your reply.

I’m not infrastructure expert. However, what I see in EC2 instance is elastic IP (18.158.222.3). I find this same IP in “Route 53 -> Hosted zones” as “A record”.
Now I don’t know what was my old IP so I cannot tell if it changed.
And I can’t tell if AWS somehow automatically updates “Route 53” when an instance is stopped and then started.

Unfortunately, the moderator removed my topic regarding the same issue. The topic contained more information about the issue and the tests I made.
Nevertheless, I’ve posted the question on StackOverflow and over there you can get more information: WordPress on Bitnami and AWS unavailable – Unit httpd.service could not be found – Stack Overflow

In your StackOverflow post, you said “all traffic allowed”.

Yet, a basic ping to the IP address you provided gets no response (“Request timed out”).

Since ping is a basic reachability test and doesn’t require WordPress, Bitnami, or even a webserver, this means you have a fundamental problem unrelated to any of these services: and this can only be one of these three possibilities:

1) The host is not up (not likely)
2) IP address provided is wrong
3) Traffic is blocked on server or AWS.

Unless you’re explicitly blocking incoming ICMP echo requests, I’ll recommend you work to establish basic reachability by getting a ping reply before doing anything else.