AWS ELB dualstack alias name throws 502 Bad Gateway exception from CNAME Flattening Setup



We have AWS Elastic cluster configured for a production environment and everything works as expected!

The issue is with setting up DNS CNAME record in CloudFlare.

What we did: Added CNAME record as a root domain and value pointing to AWS ELB alias which is

When you access, , we see 502 Bad Gateway exception. And we contacted the AWS support, they suggest nothing wrong at AWS setup side.

Right now, expect TXT record and CNAME for root, we don’t have anything else in CloudFlare records!

Can someone assist with this?



This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.