I'm just trying to launch EC2 instance with open litespeed wordpress. Once everything is setup and the instance sayings running, the IP still loading and finally shows timed error. This happens only with the openlitespeed wordpress image.
I don't think this is something we as a community can fix but don't quote me on that, have you tried contacting AWS support and running through troubleshooting? That could fix your issue.
Related
it seems I've run though everything and it will not connect,
I've verified my firewall is not blocking anything, I reset my ssh keys, I've set my user roles, and I've tried resolving it through the cloud shell.
Code: 4003
Reason: failed to connect to backend
You may be able to connect without using the Cloud Identity-Aware Proxy.
Anyone have any ideas? I just need this to work.
vm instance- OpenLiteSpeed Wordpress
zone- us-east4-b
machine type- n1-standard-1
cpu platform- Intel Broadwell
It seems you already tried to troubleshoot issue , I had similar issue so just want to know below
what is your role in project ( owner/editor)?
VM instance having external ip or not?
If firewall blocking it will give timeout error, its not timeout error.
I have a problem with my Amazon EC2 instance (that did not happened when I was using DigitalOcean).
I've several EC2 instances that are managed by me. My personal EC2 has about 5 Wordpress sites running on a t2.micro instance and the traffic is not high so it is working well in load speed.
Also I have another 2 instances for one of my clients, one t2.micro (running only one Wordpress site) and a t3a.micro (running 4 Wordpress sites). The issue is with all 3 instances (mine and all the 2 of my client).
I have a CloudWatch alarm to notify me by email when Error 504 happen. Since I get the alarm, the website becomes unavailable (Cloudflare shows me Error 504), but I can get into SSH or Webmin. I do service nginx status and all seems to be fine, same to service php7.2-fpm. I do pkill nginx && pkill php* and then service nginx start && service php7.2-fpm start correctly but when I try to enter to the site, the Error 504 is still there.
To test, I decided to install and configure Apache with and without PHP-FPM enabled, same problem. Instance going well and websites running fast but after X amount of hours, it becomes unaccessible via web and the only solution is rebooting...
What's the only thing that solve the issue? Well, rebooting the instance.... After it boots, the websites are available again. Please note that I moved from DigitalOcean to AWS because it is more useful but I can't understand why the problem is happening here and not there since I've a similar instance configured very similar...
In all of the instances I've a setup with:
OS: Ubuntu 18.04
Types: Two t2.micro and one t3a.micro
ELB: Enabled
Security Groups: only allow ports 80, 443 from all the sources.
Database: In a RDS, not on the same instance.
I can provide the logs of everything that you probably can ask but I review all the Nginx and PHP-fpm logs and I can't see any anomalies. Also with syslog and kern.log, but I can provide if it can helps.
Hope you can give me a hand. Thanks for your advice!
EDIT:
I already found the origin of the issue. The problem wasn't in the EC2, all my headache was because I have the RDS set with only one Security Group attached to allow access from my IP to remote management of the databases and the public IPs of the EC2 that runs Wordpress, but I figured that I also need to whitelist the private IPs of those EC2s... Really noob mistake but that was the solution.
I have a site hosted on AWS EC2 instance. I stopped the instance and started it up again and noticed the IP address had changed. Due to complications with this happening posts I read online suggested using an elastic IP. I allocated one and associated it with my EC2 instance. I also made sure that my hosted zone is pointing to my elastic IP. Now when I try to go to my domain I get the error "[site] refused to connect". I am able to ssh into my instance via terminal using the elastic IP. I am lost on where to go next. Any advice would be greatly appreciated. Thank you in advance!
Thanks to #strongjz I have the answer to the question. Hopefully this will help someone else in the future. Once you stop an amazon EC2 instance, not only do you need to check your IP address as it will change but also make sure to ssh into your instance and run sudo service httpd start to make sure that your web server is running. This was the problem for me. Took me days to figure it out. Big thanks to #strongjz for helping me with this!
I am running Bitnami WordPress on AWS server website working since two days but suddenly it stop showing anything and connection timeout is showing. The instance EC2 is running perfectly fine, and I have also seen IP logs, and nothing suspicious has come up.
Based on the above comments I guess the issue is with the internal web server
Make sure that the web server is running perfectly fine. And I do not mean just checking the EC2 instance state, because it is possible that the EC2 instance is running but the web server is down, causing the issue
I recently set up a new site on AWS EC2 instance. It works fine from the office, but when I go to the site from my phone it hangs and then times out. I'm new to AWS, so maybe I missed something during the setup. It's a basic lamp stack. Nothing in the logs. I don't think requests are even getting to the server. Any suggestions appreciated.
Thanks.
The issue from your question and comments is that you do not have http port 80 open to public. Please add below rule to your EC2 security group and your website will work everywhere.