- Newest
- Most votes
- Most comments
They would have stopped and restarted your EC2 where your website is hosted.
I suspect either it didnt get powered back on OR its come up with an issue. Check the EC2 where your website is hosted and make sure
- The box came back up
- Its not powered off
- Your IIS, Apache, httpd services are running etc. Check your webserver logs etc.
You don't say how your service is configured but the simplest option here is that you're running a single server without a load balancer.
If that's the case and you're receiving a 503 error it means that the web server (and therefore the instance itself) is running but there is something wrong in the setup of the web server - it's something you'd need to correct by logging into the instance. The error message you're seeing is being generated by the web server software.
If you're using a load balancer then the same is probably true - you need to check that the server is passing health checks and that the load balancer thinks it is healthy - only then will it pass requests to the web server.
Relevant content
- asked 3 months ago
- Accepted Answerasked 10 months ago
- asked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 years ago
Thanks very much. I checked the system logs and found an entry that read "Failed to start The PHP FastCGI Process Manager.See 'systemctl status php-fpm.service' for details". I then re-installed php, and rebooted the server. That seems to have done the trick.