- Newest
- Most votes
- Most comments
Are you monitoring the CPU/memory/disk utilization? Moving to a larger instance would be a first step.
Likewise, are you monitoring the network requests coming in? You may be getting hit with a Denial of Service (DoS) attack. If this is the case, you can use an Application Load Balancer (ALB) with a Web Application Firewall (WAF) attached to it to filter out unwanted and excessive request.
Next steps would be to host the site on more than one instance behind a load balancer or an auto-scaling group of instances behind the load balancer to grow and shrink with demand. These options would likely require rearchitecting depending on the type of site you are running and if it is static/dynamic content.
Hope this helps!
Hi no i do not have a solution yet. I will discuss this with a aws expert aswell But i do not understand why the instance is going down all the time. Should not be possible i thought. It is running for a few months now and we did not have these issues before.
Do you have an solution after checking our instance?
re:Post is a community forum. All members here (including AWS employees) are volunteers and provide each other best effort assistance with resources from the community. If you would like official support from AWS you would need to open a support case in the AWS console. There is a link in the Resources menu at the top right of this page. That said, there will be a limit to the support that can be provided -- your Lightsail instance is up and running and issues appear to be resource or software configuration based. Have you looked in the documentation and resource consumption on your instance?
500 Bad Gateway points to software configuration in the server being wrong. Perhaps the app is crashing and restarting? As I mentioned in my first post yesterday, you should look at CPU and Memory utilization on the server. Either one being maxed out could cause such issues. I know you verified network traffic was not the cause. Also, you should look at the CPU credit balance. On low-end instances you are paying for a low baseline CPU with the ability to burst higher for a limited amount of time. If you are bursting higher on a regular or ongoing basis, CPU may look "low" on the instance but be maxxed out against what you are paying for. Read the documentation here (and each of Topics linked on this page) regarding CPU baseline and bursting for Lightsail. https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity.html
Bot really no. Is there an option by aws to figure out where the problem might be?
Thank you for your quick answer. I will check the DoS issues. We have a dynamique site, data comming in by API calls (xml) Wenn upgrading to larger instance by snapshot i only see a double option with double costs… Wen adding loadbalancer would this help?
I have checked the incomming data. Its not equal large Can i send a printscreen here?
Good day Our website is going down all the time. Can’t find large traffic We do have 2 cronjobs running. But changing interval does not effect at all. Why is rhe instance going to 50. Bad gateway all the time? Do we have an issue with the server itself?
Greetings rob ozinga Freestays.eu
500 Bad Gateway points to software configuration in the server being wrong. Perhaps the app is crashing and restarting? As I mentioned in my first post yesterday, you should look at CPU and Memory utilization on the server. Either one being maxed out could cause such issues. I know you verified network traffic was not the cause. Also, you should look at the CPU credit balance. On low-end instances you are paying for a low baseline CPU with the ability to burst higher for a limited amount of time. If you are bursting higher on a regular or ongoing basis, CPU may look "low" on the instance but be maxxed out against what you are paying for. Read the documentation here (and each of Topics linked on this page) regarding CPU baseline and bursting for Lightsail. https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity.html
I know you also posted about the next larger instance being double the cost. Yes, at the low end, each larger instance type is double the size and price but based on the demands of your site may be required.
Hope this helps.
Relevant content
- asked 7 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
500 Bad Gateway points to software configuration in the server being wrong. Perhaps the app is crashing and restarting? As I mentioned in my first post yesterday, you should look at CPU and Memory utilization on the server. Either one being maxed out could cause such issues. I know you verified network traffic was not the cause. Also, you should look at the CPU credit balance. On low-end instances you are paying for a low baseline CPU with the ability to burst higher for a limited amount of time. If you are bursting higher on a regular or ongoing basis, CPU may look "low" on the instance but be maxxed out against what you are paying for. Read the documentation here (and each of Topics linked on this page) regarding CPU baseline and bursting for Lightsail. https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity.html
I know you also posted about the next larger instance being double the cost. Yes, at the low end, each larger instance type is double the size and price but based on the demands of your site may be required.
Hope this helps.