Instance will no longer connect to Bitnami/website MIA

Question

Hello,my name is Justin and I own a smaller company in Virginia, and thank you in advance for your help and guidance. I started working on a new domain/website several weeks back after getting the technical end set up first and surprisingly I've had no issues until now. My set up is Google domain to AWS (basic plan/$3.99/month), using Lightsail and WordPress. I followed the set up for my instance from an AWS certified specialist on YouTube. That said, I have not set up anything for storage/containers/etc tho I do have my static page set up for my landing page.

So, Sunday night I finished working on the site on wordpress with no issues outside of a jetpack warning that had been up for 2 days. It stated that my domain name and IP address were both fighting for the same spot and I needed to select one or it would go into safe mode. Outside of this, my primary updates outside of verbage was in installed a few plug ins. The last one was PayPal which was around $60 for the year. I went thru the process of setting all the pages up and everything worked great.

The following morning I had planned on fixing the jetpack issue but once I logged on, or attempted to, I realized that the website was down. All pages refused to load and a few times I got a 504 gateway timeout error message. I attempted to log in thru WordPress but I had the same issue, no loading.

I then attempted to relaunch the instance via AWS; however, the instance wouldnt connect correctly to Bitnami. Basically, the black terminal screen comes up but is empty. I then created a second instance (can only have 2 max) and attempted to connect to Bitnami again. This time, it was a success. Circle back to verify and my instance 1 still has the same results of not completely connecting to Bitnami.

I'm new, and have a basic account,meaning no technical support. Any help would be GREATLY appreciated!!

Sincerely,
Justin

Answer

Hi Justin,
         
        It sounds like there is a connectivity issue with your first EC2 instance. Here are a few recommended things you can check. Try reconnecting after each troubleshooting step to verify if the fix works.
         
        - Make sure EC2 Security groups allow the right IP addresses and ports of the service you are connecting to
        - If you are using an ALB, follow the guide linked below to see if that is the issue
        - Attempt to connect to the first EC2 instance via the command line or via the Management Console using EC2 connect to verify connections can be made
        - Check if your EC2 is using an elastic IP address, as EC2's without an EIP change their IP after reboot.
        - Verify that any route tables/NACLs in your VPC allow the type of traffic you need
         
        If there are no issues with your second EC2, you may try creating an AMI and relaunch another EC2 with that AMI.
         
        Guides:
        - https://aws.amazon.com/premiumsupport/knowledge-center/504-error-alb/
        - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
        - https://docs.aws.amazon.com/toolkit-for-visual-studio/latest/user-guide/tkv-create-ami-from-instance.html

Instance will no longer connect to Bitnami/website MIA

Relevant content