Cannot get certificate to generate

I have been working on getting certs to work with my Windows Server 2016 website and mail server. Overall it has been successful. I was working on the host headers for my mail server, not sure if I was using the correct ones. I deleted the cert for webmail.pixel8.com (with another host header of mail.pixel8.com), but when I tried to create a new one I got the error: Failed to create certificate order: Failed to begin certificate order.

I use the method of selecting the IIS website and accepting all defaults.

By the logs it looks like I’ve hit a limit certs. Is this a limit in Certify The Web or Letsencrypt?

Log file from Certify The Web
2019-12-28 18:15:30.346 -06:00 [INF] [Preview Mode] Completed certificate request and automated bindings update (IIS)
2019-12-28 18:15:36.296 -06:00 [INF] Certify/4.1.6.0 (Windows; Microsoft Windows NT 6.2.9200.0)
2019-12-28 18:15:36.296 -06:00 [INF] Beginning Certificate Request Process: webmail.pixel8.net using ACME Provider:Certes
2019-12-28 18:15:36.296 -06:00 [INF] Registering Domain Identifiers
2019-12-28 18:15:36.296 -06:00 [ERR] BeginCertificateOrder: creating/retrieving order. Retries remaining:2
2019-12-28 18:15:36.443 -06:00 [ERR] BeginCertificateOrder: error creating order. Retries remaining:1 :: Certes.AcmeRequestException: Fail to load resource from ‘https://acme-v02.api.letsencrypt.org/acme/new-order’.
urn:ietf:params:acme:error:rateLimited: Error creating new order :: too many certificates already issued for exact set of domains: mail.pixel8.net,webmail.pixel8.net: see https://letsencrypt.org/docs/rate-limits/
at Certes.Acme.IAcmeHttpClientExtensions.d__01.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Certes.AcmeContext.<NewOrder>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Certify.Providers.Certes.CertesACMEProvider.<BeginCertificateOrder>d__26.MoveNext() 2019-12-28 18:15:37.444 -06:00 [ERR] BeginCertificateOrder: creating/retrieving order. Retries remaining:0 2019-12-28 18:15:37.617 -06:00 [ERR] BeginCertificateOrder: error creating order. Retries remaining:-1 :: Certes.AcmeRequestException: Fail to load resource from 'https://acme-v02.api.letsencrypt.org/acme/new-order'. urn:ietf:params:acme:error:rateLimited: Error creating new order :: too many certificates already issued for exact set of domains: mail.pixel8.net,webmail.pixel8.net: see https://letsencrypt.org/docs/rate-limits/ at Certes.Acme.IAcmeHttpClientExtensions.<Post>d__01.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certes.AcmeContext.d__19.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certify.Providers.Certes.CertesACMEProvider.d__26.MoveNext()
2019-12-28 18:15:38.622 -06:00 [INF] Failed to create certificate order: Failed to begin certificate order.
2019-12-28 18:15:39.141 -06:00 [INF] Failed to create certificate order: Failed to begin certificate order.
2019-12-28 18:15:41.103 -06:00 [INF] [Preview Mode] Completed certificate request and automated bindings update (IIS)
2019-12-28 18:15:48.670 -06:00 [INF] [Preview Mode] Completed certificate request and automated bindings update (IIS)

Thanks,

Mike

Hi, this is a rate limit at the Let’s Encrypt side, if you check the certificate transparency logs you can see you’ve generated a bunch of certificates recently: https://transparencyreport.google.com/https/certificates?hl=en&cert_search_auth=&cert_search_cert=&cert_search=include_subdomains:false;domain:mail.pixel8.net&lu=cert_search

This rate limit will reset within 7 days: https://letsencrypt.org/docs/rate-limits/