In effect, we can make a partial certificate for you if your DNS is only partly propagated when you configure hostnames in our system, and the “fix” is to hit the “renew certificate” button in our UI, at the bottom of the Domain Settings page as shown in this screenshot:
In this case, I went ahead and renewed it for you, but for others who have this problem, you can self-solve (though DNS does need to be correctly configured and propagated first!).
My site was deployed and was waiting on DNS propagation for the SSL certification. I checked back a bit later and my site is now https enabled. I get the same warning from Chrome and when i click “Renew certificate” I get “mydomain.com doesn’t appear to be served by Netlify” even though I have added the nameservers to the domain. I would suggest Netlify not install certificates until everything is fully propagated so the user can indeed “Renew certificate”.
There’s no way to go back to just HTTP so i don’t know what to do here except hit “Renew certificate” throughout the day and hope(??)
UPDATE: I was able to “Renew certificate” but the warning persists. I’m afraid to keep renewing in fear of hitting the let’s encrypt request limit.
FINAL UPDATE: I guess it was a dns propagation thing. Checked my site after a few hours after clicking the Renew Certificate button and everything was good to go. No more browser warning.
Had this issue, when examining the cert it was issued by Netlify instead of Let’s Encrypt. Clicking on Renew certificate like @fool says did it for me. But you have to wait a little bit.