To many atempts

i had multiple errors setting up my nextcloud with adguard dedicated server. Now everything is managed but when i want to make the final cert i get this messasge.

Attempting to obtain certificates... error running certbot:

Saving debug log to /var/snap/nextcloud/current/certs/certbot/logs/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours:, retry after 2022-12-26T01:16:24Z: see Duplicate Certificate Limit - Let's Encrypt
Please see the logfiles in /var/snap/nextcloud/current/certs/certbot/logs for more details.

Can i reset this somehow because i know it would work now.

Hello @derleiti, welcome to the Let's Encrypt community. :slightly_smiling_face:

The Rate Limits have been hit.
Testing is best done using the Staging Environment.
And to assist with debugging there is a great place to start is Let's Debug.

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Thank you for assisting us in helping YOU!

1 Like

No, This is explained in the rate limit link in your error message.

But, if you request a Let's Encrypt cert with and that is a new combination of names so should work. This is also described in that rate limit page.

I saw you just got a DigiCert cert with both names so it looks like you intend to want both working. See your cert history (link here)


Yeah it is because i have dedicated server sute ssl funtion which i wanted to have enabled, too. The easiest way would be the nextcloud.enable-https command with the syntax lets-encrypt. With custom settings with the key i can't bring it to work. Till i realised that i just have to run the lets-encrypt command after this. It was out of service.

But i made now a subdomain which i can add by lets-encrypt i guess. But my dedicated server didn't boot last time and ah i see it was out of order but now works. I'll give it a try.

Please test with the Staging Environment - Let's Encrypt first.


Ok i have to wait again long reboot of server but none of the domains accepted the lets-encrypt per ssh on it. I want to make a nextcloud server and a adguard home dns server on dedicated webserver with dns-over-tls with snap on the latest server lts of ubuntu. If someone has a better idea than snap than just tell me.

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