When deploying - I have a custom domain proxied through Cloudflare. CNAME are correctly added on Cloudflare and everything works well.
However, when deploying, the step “Resolution of CNAME” takes veeeeery very long (too many retries), and it fails in the end. I am a bit confused about this resolution step - since the console fails but the website works.
Indeed, it’s a known “issue” and we’ll provide a solution to make it faster to deploy when using a Cloudflare CDN.
Explanation
Qovery makes sure that your application is really live and custom domain resolution works before marking the app RUNNING. The reason why it takes so long is that Qovery has no clue to know that your domain foo.bar is behind a proxy and when trying to resolve the domain foo.bar it will get a DNS response that does not reflect the expected CNAME
Yes, It never resolves DNS, failing after a very long time. When you mentioned solution is coming I figured you meant a different way of checking that wont fail. It’s not a big deal it’s just a rough edge, there’s opportunity for a better UX here.