Skip to main content

Domain not getting a LetsEncrypt certificate but not showing errors

ssnc-simon
I have a client who adds a lot of domains to a single account, but AutoSSL usually works. However, I set up a domain on their server on Saturday and it isn't getting a certificate. One issue was that adding it was failing to be created with the `Could not determine the nameserver address` error, but installing jwhois as suggested in other threads fixed that and the domain was added correctly. The domain and www subdomain are showing as managed in the AutoSSL logs and there are no errors relating to them. The domain was registered at and served from Squarespace and resolves correctly both on the server and elsewhere.

Comments

6 comments

Date Votes
  • ssnc-simon
    I've fixed this now but in a fairly extreme kind of way. The domain had been added to the primary certificate for the account, and I tried to install a certificate for the new domain only generated using acme.sh and DNS verification, but this had the effect of invalidating the certificate for all the other domains. However, running AutoSSL again then replaced that certificate including the new domain. However, I would still like to know why the domain couldn't be updated in any other way and why DNS resolution failed in a way that hasn't happened before.
    0
  • cPRex Jurassic Moderator
    Hey there! You mentioned there were "a lot" of domains on the single account - do you know how many exactly? It's possible you are exceeding the certificate limits from either provider as outlined here:
    0
  • ssnc-simon
    That's definitely possible. We're using LetsEncrypt but I'd have to work out exactly how many domains (and subdomains) the account has. There's definitely some cleaning up needed. Is there a rate limit error logged anywhere?
    Hey there! You mentioned there were "a lot" of domains on the single account - do you know how many exactly? It's possible you are exceeding the certificate limits from either provider as outlined here:
    0
  • cPRex Jurassic Moderator
    Yes, if you are reaching the ratelimit you'll see something like a "429 Too many requests" error in the log. You can check these from WHM >> Manage AutoSSL under the "Logs" tab.
    0
  • ssnc-simon
    No 429 errors in the logs. I wonder if ti was necessary to invalidate the existing certificate.
    Yes, if you are reaching the ratelimit you'll see something like a "429 Too many requests" error in the log. You can check these from WHM >> Manage AutoSSL under the "Logs" tab.

    0
  • cPRex Jurassic Moderator
    It's hard to say now that things have been fixed, but I am glad to hear you got it working.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post