Cannot get SSL certificate provisioned for external domain

Support
1

I have a domain name provisioned by GoDaddy and followed the approach described in this doc How to Set Up Netlify DNS - Custom Domains, CNAME, & Records to use that domain name for my site (named maratrilla.netlify.app) from an external DNS (not a domain from Netlify DNS), so I:

  1. Set the A DNS record in GoDaddy DNS for the apex domain (maratrilla.com) pointing to 75.2.60.5
  2. Set the CNAME record in GoDaddy DNS for the www subdomain pointing to maratrilla.netlify.app
  3. Verified that there are no issues that Let’s Encrypt could have been found in Let’s debug. See the reports https://letsdebug.net/maratrilla.com/2431646 and https://letsdebug.net/www.maratrilla.com/2431647
  4. I can see in the Domain Management page Netlify that “DNS verification was successful”

However it’s been over 24 hours since I requested Netlify to use the custom domain and Netlify says it’s still waiting for the DNS changes to propagate:

image
image1446×534 40.9 KB

Thanks in advance for your help.

2

There’s no production deploy for your site yet: Deploys | maratrilla | Netlify. No SSL without a prod deploy.

3

Oh, didn’t know that. If I do a production deploy, would it be a period of time where the site would be accessible without an SSL certificate until Netlify gets the certificate? I would want to avoid users accessing the site during that period of time receiving the insecure site warning.

4

Besides that I’d like to set the primary domain to be the www subdomain to get the performance benefits suggested in this blog How to Set Up Netlify DNS - Custom Domains, CNAME, & Records.
But changing the primary domain requires the SSL certificate being generated first:

image
image1232×680 40.3 KB

Would I be able to make those changes after I do the production deploy?

5

Netlify will not serve the custom domain (www.maratrilla.com) until the SSL certificate is ready. So, there’s no risk of users seeing an insecure site warning.

You need to publish a production deploy on Netlify. This is required before SSL can be issued.

After the SSL certificate is provisioned (which completes shortly after a production deploy), you can set www.maratrilla.com as the primary domain. Ensure that Netlify automatically redirects all traffic from maratrilla.com → www.maratrilla.com.

6

This is not true. The page will be accessible without SSL.

1 Like
7

Thanks both for your answers! I did a production deploy overnight (at least on the timezone I am mostly interested in), then within the next 1.5 hours aprox. Netlify provisioned the SSL certificate and I changed the production domain domain to point to the www subdomain.

1 Like