Kubernetes TLS Certificate Acquisition Issue via cert-manager Integration with Clou

Dear support team

I hope this message finds you well. We are currently encountering a critical issue in our efforts to obtain a TLS certificate using cert-manager integration with Cloudflare, utilizing the dns01 challenge. Unfortunately, we have hit a rate limit and have been unable to receive the certificate from Let’s Encrypt.

Given the importance of this TLS certificate for our operations, we urgently seek your assistance in resolving this matter. Is there any feasible solution or workaround available to circumvent the rate limit imposed by Let’s Encrypt?

Your prompt attention and support in resolving this issue would be greatly appreciated. Please let us know if there’s any additional information or steps we can provide to expedite the resolution process.

Thank you very much for your assistance.

Hello l.klingelhoeffer,

To resolve the rate limit issue with Let’s Encrypt, you can try the following steps:

  1. Check the specific rate limit you’ve hit on the Let’s Encrypt documentation to understand the limitation.
  2. If possible, wait for the rate limit to reset (usually a week).
  3. Consider using a different domain or subdomain to bypass the rate limit.
  4. Explore using a staging environment for testing to avoid hitting the production rate limits.
  5. If urgent, consider obtaining a certificate from an alternative CA that does not have such strict rate limits. e.g. GST.

Remember to review your certificate issuance process to prevent hitting rate limits in the future.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.