Your DNS set up is perfect. Our system should have issued you a wildcard SSL certificate since you are using Netlify DNS but that had not yet happened. I went it and got that working for you and now offline-master.sf-goso.org is covered by the certificate. And any new subdomains you add should also be covered by that cert automatically.
Please let us know how things are looking on your end now.
As far as I can tell, no DNS is configured for that hostname, nor is it applied to a Netlify site, both of which are required for us to get a certificate for it. What site of ours do you intend to show at that hostname, and have you configured it both in DNS and by adding that name to the list of sitenames in your site’s custom domains settings page?
I have a branch subdomain staging and I’ve configured the DNS by following this post.
Is there any way to have that subdomain with https automatically?
I’ve tried adding it to the Custom domains and renewed the certificate but then it seems it sometimes points to the production branch instead of the staging.
@joewoodhouse, please create a new “topic” (aka post) in the Admin category. If you want to keep the domain name secret (because it is preview/testing or otherwise not ready for the public) then ask for a direct message (DM) in the topic and we’ll exchange information privately that way.
dashbud.dev. 21600 IN NS curitiba.porkbun.com.
dashbud.dev. 21600 IN NS salvador.porkbun.com.
dashbud.dev. 21600 IN NS maceio.porkbun.com.
dashbud.dev. 21600 IN NS fortaleza.porkbun.com.
This means the Netlify DNS zone above must be deleted. This can be done using the “Delete DNS zone” button at the bottom of the page linked to above.
Inactive DNS zones do prevent SSL certificate renewals.
Once the inactive zone has been deleted, please let us know and we can get the SSL certificate updated to include react.dashbud.dev. The instructions for domains not using Netlify DNS (like this domain) can be found here:
You don’t need to do anything (except delete the inactive DNS zone).
All the required steps listed in the “[common issue]” topic above are complete already. The only thing blocking our support team from updating the SSL certificate is the inactive DNS zone. Once it is deleted, we can complete the setup of the certificate.
Hi @html5cat . I’ve setup a new site cape-sh.netlify.app with a custom domain of cape.sh and also a branch subdomain on stg.cape.sh. Would it be possible to fix the SSL certificate for stg.cape.sh? Appreciate it.