Custom domain stuck on SSL config / Err 403 / All DNS records look good

[badvik83]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Frontend builds

Is your feature request related to a problem? Please describe:

I have a domain with namecheap.com and I don't use Route53. I successfully deployed my custom domain (nadiahope.com) with Amplify and it's opening at:
https://dev8901.djaiq6dooqujo.amplifyapp.com/
However, it's stuck at SSL Configuration (although SSL certificate is shown as issued when I go to https://nadiahope.com) and the site itself won't open, pointing at cloudfront. A DNS CNAME check returns all green checks.

p.s. I also have WorkMail and the MX record set up and this works properly.

Describe how you'd like this feature to work

Site should open

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[arundna]

@badvik83 - 👋 I'm unable to locate your app ID - djaiq6dooqujo in our service. I did see that https://nadiahope.com/ is rendering correctly. Do you have the right app ID for your app that can help to investigate further?

[badvik83]

@badvik83 - 👋 I'm unable to locate your app ID - djaiq6dooqujo in our service. I did see that https://nadiahope.com/ is rendering correctly. Do you have the right app ID for your app that can help to investigate further?

Thank you for checking and getting back to me. But I moved the site to my trusted hosting service with a quick and free support (this not to you but AWS in general).

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.