Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.98 minutes in June 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

How to fix let’s encrypt new auth status 429 error?

by | Jan 24, 2021

Generally, the Let’s encrypt new auth status 429 error occurs when too many certificates are created for a domain on a specific period of time. As a result, it exceeds the Let’s Encrypt’s rate limit on limit Certificates per Registered Domain.

As a part of our Server Management Services, we help our Customers to fix SSL related errors regularly.

Today, let’s discuss the possible causes and fixes for this error.

 

What causes the Let’s encrypt new auth status 429?

Let’s Encrypt has a limit for the number of certificates requests that we can place per domain name known as  ‘Certificates per Registered Domain’. For a single domain, this is set as 50 per week. Since this limit is per each registered domain. ie, a request for www.example.com and test.example.com will be counted against example.com itself. Exceeding the Certificates Per Registered Domain limit commonly triggers Let’s encrypt new auth status 429 error.

In case, if there is a lot of subdomains, we can combine them into a single certificate, up to a limit of 100 Names per Certificate. Considering the above limit, that means we can issue certificates containing up to 5,000 unique subdomains per week. A certificate with multiple names is called a SAN certificate, or sometimes a UCC certificate.

The most common rate limit of 50 certificates per domain per 7 days in a place that is set by Let’s Encrypt. Let’s Encrypt directly defines this limit.

Also, there are two other limits:

  • User can create a maximum of 10 Accounts per IP Address per 3 hours.
  • User can create a maximum of 500 Accounts per IP Range within an IPv6 /48 per 3 hours.

For instance, the error appears as below.

let’s encrypt new auth status 429 error

 

How we resolve the let’s encrypt new auth status 429 error

Now let’s take a look at the suggestions our Support Engineers provide to get rid of this error.

1. In order to reset the limits, we add a new alias to the domain and re-issue the SSL Let’s Encrypt certificate

2. Wait for the time period to pass and reissue the certificate

[Need any further assistance with Let’s Encrypt errors? We can help you]

 

Conclusion

In short, this 429 error occurs due to creation of multiple certificates for a domain. Today, we saw the suggestions our Support Engineers provide to overcome this error message.

1 Comment

  1. Thanks for the detailed explanation, helped me alot.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF