Skip to main content

Change to Lets Encrypt -- Rate Limiting

Comments

6 comments

  • Vinnie Murdico

    That's a shame. This change has the potential to severely impact my business if my customers' sites start losing their SSL certificates and they can't be renewed due to the rate limits of the only provider cPanel will support.  I wish cPanel had considered these limitations and their impacts on customers before deciding to make Lets Encrypt their sole provider.  

    2
  • cPRex Jurassic Moderator

    Hey there!  From our side, there currently isn't a way to avoid the ratelimit.  I know we're discussing increasing that limit with them as we shift them to be our main SSL provider, but I don't know for sure if or when that will actually happen at this point.

    0
  • Konrad Olszewski

    disabling sectig/cpanel certs and switching to letsencrypt literally destroyed the idea because of rate limit... main accounts named as user.hoster.com are also ratelimited because not only requester ip but hoster domain too !

    0
  • Vinnie Murdico

    This.  I have hundreds of accounts that are hosted under subdomains of my primary domain.  Those customers don't want to have a unique registered domain; they are content to use a free subdomain for their sites.  Those are all falling under the domain rate limit which I didn't have to worry about under Sectigo.  Not to mention all the potential customers who start trial accounts to eval my service.  Those are under a subdomain and get an SSL certificate during the trial, even if it won't be used long term.  But it counts against the rate limits...

    On the bright side, Let's Encrypt has typically been more reliable at issuing certificates quickly.

    0
  • cPRex Jurassic Moderator

    Let's Encrypt has a form where you can request an increase for a common domain:

    https://isrg.formstack.com/forms/rate_limit_adjustment_request

    While this isn't a global solution for all domains, it would solve issues similar to what Vinnie Murdico is seeing where one domain has a very large number of subdomains.

    0
  • AmedeoSca
    Today I reached the number of 34 domains parked in my main account and this message came out... not how to do it.
    This is really a big problem
     
    WARN Provider’s per-certificate domain count limit: 100
     WARN “Let’s Encrypt™” cannot secure all of “example.com”’s domains. Remove domains from “example.com” to fix this.
    0

Please sign in to leave a comment.