503 Service Temporarily Unavailable #47
Comments
Hi @harshjain2, Thanks for reaching out. Unfortunately we no longer actively support or develop MageCloudKit so I am unable to help you with this issue. You can read more about this change in the following blog post. You are welcome to investigate this issue yourself and submit any code changes via a pull request and we'll review your contribution. I'll leave this issue open as a reminder it still needs to be investigated either by yourself or the community. Regards, Rob |
@robmorgan I will surely investigate this issue and if I am able to find a solution, I will raise the PR aa well. Based on your experience, please guide me a bit so that I can start investigating this issue. |
@harshjain2 sure! I'll answer inline, based on my experience:
This likely sounds like none of the ECS tasks are successfully running on the ECS cluster. As a result, none have been added into the ALB (Application Load Balancer) target group as 'healthy'. This is likely causing the 503. It probably has been caused by an empty database. I.e. You can fix it by running the Magento installer somehow or importing a Magento 2 database dump into the RDS database.
Sounds like an empty database. Same issue as above.
This sounds like PHP is having trouble connecting to the database host. Was the host name modified or entered incorrectly? was it not passed via the ECS task definition correctly? Check the details in the ECS console and see what is in the task definition. |
|
@robmorgan I am just wondering how the updates will work in magecloudkit? |
Issue
Getting
503 Service Temporarily Unavailable
on deploying the example https://github.com/magecloudkit/magecloudkit/tree/master/examples/magecloudkit-simple-vpcIntermittently, I have also observed these errors :
Terraform version : Terraform v0.11.8
Let me know if you are aware about this issue. Or point me to right direction, so that I can fix this issue.
The text was updated successfully, but these errors were encountered: