Trying to have multiple subdomain URLs as separate sites on Netlify. Let's Encrypt not issuing certificates

Support
,
1

My site located at therapy2000.nclr.io is set up now to use Netlify DNS, but isn’t working properly. I can connect to the page, but no SSL certificate is able to be generated for it. I have multiple other subdomains for nclr.io that I am trying to set up as separate websites for different uses on Netlify, but do not yet have a site for nclr.io itself set up.

I am using Google Cloud DNS and have my NS record pointed correctly toward the Netlify name servers at p01.

I successfully was able to provision a certificate for t2k.nclr.io a week or two ago, but the other site mentioned and all other subdomains now refuse to issue certificates. The CNAME records for all the subdomains are pointing toward the appropriate auto-generated URLs on their respective Netlify site areas. I have even set the A record to point toward Netlify’s address of 75.2.60.5, but to no avail.

The error message I get when trying to provision the HTTPS TLS certificate for therapy2000 is only: " We could not provision a Let’s Encrypt certificate for your custom domain.
Please read our troubleshooting guide for some tips on what might be happening."

Will Let’s Encrypt not allow me to provision multiple TLS certificates to different subdomains of the same root domain? I currently have been manually deploying the sites, so should I instead use a git repo and create branch subdomains?

Any help would be greatly appreciated!

2

Hi @eric-nicular :wave:t6: ,

Thanks so much for reaching out to us and welcome to the forums. Can you confirm the following has been completed?

  1. Please Verify that your SSL certificate is correctly configured.
  2. Make sure that your domain is set up to use HTTPS.
  3. Check if there are any conflicts with existing certificates. It’s possible that you might have reached a limit on the number of certificates you can issue for your domain. Let’s Encrypt has a rate limit of 5 certificates per week per domain.

I would consider using a git repo and create branch subdomains it’s also easier for automatically updating your site with the latest code changes. I recommend you read more about our continuous deployment here.

3

Thanks for responding! I managed to get my issue resolved using Firebase Hosting, but am a fan of Netlify, so I would love to continue using the service for my project.

  1. The SSL certificate hasn’t generated yet, so I would need to manually allocate one
  2. The domains should be set up to use HTTPS
  3. I believe that the rate limit being reached may have been the issue.