We're having a problem where we can't access our site over HTTPS when using a valid certificate.
We have a domain, registered in Route53, and a certificate.
We have a load balancer:
We have two target groups, with targets managed by ECS:
We have two listeners on the load balancer:
HTTP : 80, forwarding to our-production-target-group-http HTTPS : 443, forwarding to our-production-target-group-https
We have a certificate applied to the https listener:
I have run logs on the actual instance, http requests get through fine whereas https requests don't show at all.
When I use the real certificate for the https listener, I get a 502 error. If I use a self-signed certificate it works fine with a security warning in chrome.
Does anyone have any ideas what could be happening?