Hi @dr1602,
Thanks for following up. I’ve checked the domains DNS settings and everything looks correct. I initiated a pressing of the Verify DNS configuration button and the SSL Certificate has now been provisioned. You should be all set.
Hi @dr1602,
Thanks for following up. I’ve checked the domains DNS settings and everything looks correct. I initiated a pressing of the Verify DNS configuration button and the SSL Certificate has now been provisioned. You should be all set.
Now it works, thanks Melvin!!! Not enough exclamation marks to say thanks!!
Hi there!
I am having issues with the SSL/TLS certificate for the following website: atelier1064.com (using Netlify DNS).
I followed all the instruction in this guide, everything seems to be working OK on DNSchecker.org and on Let’s Debug.
Thanks for your help
Hi @sercas88,
Thanks for reaching out and welcome to Netlify’s Support Forums!
I am showing that the SSL Certificate has been provisioned. Visiting the domain is also resolving correctly with a valid Let’s Encrypt Certificate.
Additionally, I do see that Netlify’s Name Servers are correctly configured:
dig atelier1064.com NS +trace | tail -n 6
atelier1064.com. 3600 IN NS dns1.p09.nsone.net.
atelier1064.com. 3600 IN NS dns2.p09.nsone.net.
atelier1064.com. 3600 IN NS dns3.p09.nsone.net.
atelier1064.com. 3600 IN NS dns4.p09.nsone.net.
;; Received 133 bytes from 198.51.45.9#53(dns2.p09.nsone.net) in 30 ms
Are you still having issues or were you able to resolve it?
Hi Melvin. Thanks for the quick answer. Everything seems to be resolved! Have a good one
Hi @Melvin
I checked through all the guide here and I can see that my domain is pointing to Netlify DNS.
However, https is not provision as Waiting for DNS propagation keeps spinning and it over 48 hours.
The domain name is abisalde.dev
I look forward hearing from you soon.
Cheers,
Hi @abisalde,
Thanks for reaching out!
I’ve double checked your DNS configuration and do see that you’re using the Netlify name servers and don’t have any conflicting records, everything looks good, so I did a Verify DNS configuration and the SSL Certificate has been provisioned. You should be all set.
Genius.
Thanks Melvin
Hello! I am setting up my first custom domain, and running into an issue with the provisioning of the Let’s Encrypt certificate.
Here, my DNS was validated, however in the screenshot there is an error in getting the cert issued.
My domain is thirdcoast.dev
It looks like the domain was issued a cert now. I am not sure what happened there. I did try going to the domain, but that is not resolving to my website yet.
It appears this domain is not registered.
Apologies, dig, I typed it in wrong.
thirdcoast.dev is the right domain name.
I think I am squared away, though. I think there was some propagation time that I had not accounted for.
Hi @Keys,
Thanks for following up. It does look like you’re all set. The DNS for the domain is configured correctly for Netlify DNS:
dig thirdcoast.dev NS +trace | tail -n 6
thirdcoast.dev. 3600 IN NS dns1.p07.nsone.net.
thirdcoast.dev. 3600 IN NS dns2.p07.nsone.net.
thirdcoast.dev. 3600 IN NS dns3.p07.nsone.net.
thirdcoast.dev. 3600 IN NS dns4.p07.nsone.net.
;; Received 132 bytes from 198.51.45.7#53(dns2.p07.nsone.net) in 30 ms
I see that the SSL Certificate has been successfully provisioned and visiting the domain resolves properly.
Let us know if you have any issues.
@melvin Thanks for confirming that for me! I appreciate it.
Hi, my domains are verified but I got similar issues.
The domains are stellaria.id
& stellaria.moe
.
Thank you very much.
Hi @Melvin!
Could you please check this domain for me? meetings.real-dev.com
same issue, SSL/TLS certificate. I got the real-dev.com
domain and put with subdomain on netlify but it’s not working with SSL/TLS yet.
I really appreciate it!
Hi, @shenwilly. The issue for your domain was due to time to live issues and the SSL is working now.
The issue for you, @Mauricio-Natacci, is different. The issue in this case is that you made a DNS zone for the subdomain meetings.real-dev.com
here:
https://app.netlify.com/account/dns/meetings.real-dev.com
However, when I check your domain’s configuration, you have delegated the apex to Netlify (meaning real-dev.com
) , not just the meetings
subdomain. This means the domain is currently misconfigured.
The steps to fix it are:
meetings.real-dev.com. 3600 IN NS dns1.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns2.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns3.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns4.p08.nsone.net.
Note, the TTL values on the current NS records for the apex are 172800 seconds. This means it may be 48 hours before the these changes are detected by downstream DNS resolvers.
https://app.netlify.com/sites/meetings-management/domain-management#ssl-tls-certificate
The SSL provisioning will succeed if those steps are taken. You may not need to wait 48 hours but it is possible and that is the longest you would need to wait for the TTL to expire. However, if those instructions don’t work as promised, please let us know.
Ello,
I followed the steps but still my client’s domain has no ssl.
Here is the domain https://alixlacloche.com/
Thx
Hi I’m seeing a cert for this domain and the site is secure. Are you still having issues? If so I recommend you give this doc a read.