Wordpress on Lightsail goes down daily

0

Hi, I am new to AWS services.

I have bought a domain (on AWS) and created a Wordpress instance on Lightsail (Bundle 0.5GB) and it was working fine. On the second day it went unreachable ("Unhealthy" in the Health Checks). So I have deleted the Wordpress instance and the DNS; then I made all the steps from beginning and the Wordpress website was again up and working. Today, about 4 hours ago, my Wordpress is again unreachable ("Unhealthy" in the Health Checks).

When I try with a "curl -v" I get:

* Trying 3.xx.xxx.x...
* TCP_NODELAY set
* Connected to xxxxxx.org (3.xx.xxx.x) port 80 (#0)
> GET / HTTP/1.1
> Host: xxxxxx.org
> User-Agent: curl/7.64.1
> Accept: */*

and it gets stuck there. The static IP and the domain name are correct.

Can it be a Lightsail failure? What I should check? If useful, I can write IP and domain name in clear.

Since it is a website for helping the Ukraine people, I would really like to get it working asap.

Thanks, Domenico

  • Hi buddy, just wonder if you have solved your problem because I think I ran into something similar.

3 Answers
0

Thanks for the answer John.

Exactly as you wrote: it does work correctly for a while, but then becomes "Unhealthy" and is not reachable any more. I cannot SSH into the instance when it is not responding.

Today it got "Unhealthy" at 13.56: https://i.ibb.co/xmnfXNK/Screenshot-2022-03-01-at-21-28-36.png

In the metrics:

(sorry, I am not able to directly insert images).

Dom
answered 2 years ago
  • Yes, it appears that you are running out of resources on that very small instance. You have two options, bump up to a larger instance that can handle the load, or figure out if there's anything you can eliminate to reduce the resources you are using. The easiest thing to do is option number one. Take a snapshot of your instance and then restore it to a "bigger" Lightsail instance type and see if that keeps you out of the "CPU burstable zone".

  • +1 on John Vold's comment. You might need a bigger instance.

0

Now it is not reachable for 2 days in a row.

Dom
answered 2 years ago
  • Did you try upgrading the instance size per my other comment?

0

Just to be sure, it does work correctly for a while, but then becomes "Unhealthy" and is not reachable any more? Are you able to SSH into the instance when it is not responding? Have you checked the "Metrics" tab to see if anything looks strange in there?

answered 2 years 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