I'm pretty new to AWS. I have created an instance of ec2 and separate RDS. I have deploy my code. Sometimes I'm getting 503 error Service Unavailable (The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later) from API.
Note1: I'm not using load balancer.
Note2: Sometimes I got the my required response (200 status). But most of the time its 503.
How I have to fix that error please?
Help will be appreciated.
Thanks.
We have hosted a laravel based API backend on AWS ec2. It was working fine until this morning when suddenly the mobile app stopped working. I checked the API response on postman and it showed connect ECONNREFUSED error.
I connected to ec2 though putty and realized that the ec2 diskspace was full. I emptied the disk by deleting few project folders which made around 8% space empty. I restarted ec2 but still getting the same error
Can someone please help how to fix this?
Regards
Syed
I have installed Magneto 2 on EC2 with a MySQL database hosted separately on a RDS instance. I have configured the varnish on my EC2 server.
Whenever I open multiple tabs on the website, the varnish server crashes on a couple of product pages with the following error:
Error 503 Backend fetch failed"
Varnish version: 4.0.4 on Centos 6
I had the same problem and finally figured out what the reason was. We had the website silently running for testing without problems for a week. When we pointed our domain to the amazon EC2 instance - varnish crashed after some hours.
But that was maybe a coincidence. I found out someone was scraping the ip to find some access. logs were full of access tries to /sql /phpmyadmin /administrator ...and so on.
That caused varnish crashing.
I am testing the free services from Amazon EC2. I followed the manual and was able to access the server. After one minute inside the server, it crashes and I have to close my console and reboot the instance.
By reading the guides from Amazon, I found that I should set the Route Table, which I was not able to find. Maybe the dashboard has changed.
I am using Amazon EC2 services & and its working correctly but suddenly from 3-days before when we try to access our instance using ssh connection we got following error:
"ssh: connect to host ec2----***.compute-1.amazonaws.com port **: Connection timed out"
when I try to access our sites deployed on our EC2 instance, I received the same error ,
"The connection has timed out
The server at ec2----***.compute-1.amazonaws.com is taking too long to respond"
there is no problem in network connection from our side as we are able to access other web site and services smoothly.
I can't even able to access hosted site without this.
I encountered the same problem.
I followed the troubleshooting in http://alestic.com/2010/05/ec2-move-ebs-boot-instance
Then when I tried to start a new instance, I got an message from Amazon:
Server.InsufficientInstanceCapacity: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1b). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1c, us-east-1a.
Maybe, you have an instance is us-east-1b, too.
You can try to access the System Console (either via the amazon web console or elasticfox) and check for any errors/messages that might help you arrive at the cause of this.
In ~/.ssh/config, add the following lines:
ServerAliveInterval 50
This will keep on pinging the server every 50 seconds to keep the connection alive.