Hello there,
I understand the frustration involved in the custom domain getting stuck while the Let’s Encrypt SSL certificate for that custom domain is being provisioned. So, according to what you’ve told me, the DNS for the site seems to be set right, the website works fine under the subdomain with the extension of netlify.app.
Some steps to be followed to resolve the situation include:
1. Double-check DNS
For external DNS: You must have the A record pointing to your apex domain (example.com) at 75.2.60.5 and the www subdomain (www.example.com) pointing somewhere else, which has a CNAME record pointing to [sitename].netlify.app
For Netlify DNS: Verify that your registrar is using the correct name servers for Netlify.
2. Troubleshooting potential blockers
Verify if there are any CAA records that may prohibit Let’s Encrypt from issuing a certificate.
If you have AAAA/IPv6 records for your apex domain, remove these since they conflict with the load balancer of Netlify.
Ensure that there are no left-over old A records from the previous hostings. If DNSSEC is enabled, disable it for domains hosted by Netlify.
3. Retry certificate issuance
Go to Settings > Domain management > HTTPS in the Netlify dashboard.
Click on the Renew certificate and make sure that all “Force HTTPS” switches are correctly set.
Let Netlify automatically retry the issuance (it retries every 10 minutes for 24 hours, then hourly for 2 more days).
However, in case the certificate is still not issued even after this, it could be a situation where Netlify support will have to re-provision the certificate for us. And, as a matter of fact, since your netlify.app subdomain is already working, your site is already live, and as such, you are only concerned about HTTPS for your custom domain.
Hope this helps get your site fully secured!
Best regards,