Hi Alejandro thanks for your replay I was waiting for you I received an answer from AWS as well, I would like to share it with you, it is a bit long but I find it interesting and if you think that I should also disable the PageSpeed, I have had a very bad time with this problem and I do not want to do something that makes me go back.
From the configuration i could see the HC is configured on Port 80 and i could also see the Port 80 is open in security group however the HC are Timeout when performed by ALB. I believe the issue is with instance not responding to HC request.
• 504: gateway time out could be caused due to below reasons.
The load balancer failed to establish a connection to the target before the connection timeout expired (10 seconds).
The load balancer established a connection to the target but the target did not respond before the idle timeout period elapsed.
The network ACL for the subnet did not allow traffic from the targets to the load balancer nodes on the ephemeral ports (1024-65535).
The target returns a content-length header that is larger than the entity body. The load balancer timed out waiting for the missing bytes.
The target is a Lambda function and the Lambda service did not respond before the connection timeout expired.
• i also see the instance has Public ip attached to it. When i try to curl that ip as well it ends in 504: gateway timeout.
But Finally I got another email that says:: "the issue is not just backend not responding to Health check. The issue with the backend target not responding at all."
I think some bugs were fixed, but if the error is not just the one mentioned above, as you say, I should disable page speed anyway, this can't cause a new error on my site right?
Just out of curiosity, do you speak Spanish? I'm Chilean from Latin America