Stupidity of using certificate generation from docker temporary machine

My domain is:

I ran this command:

certbot --nginx -n --agree-tos -d meak-stories.com -m {my e-mail}

It produced this output:

An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: meak-stories.com: see https://letsencrypt.org/docs/rate-limits/
Please see the logfiles in /var/log/letsencrypt for more details.

My web server is (include version):
Using docker image nginx

The operating system my web server runs on is (include version):
Inside docker...?

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

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

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

I make something I just discovered was stupid: I was running the certbot inside my docker machine, while testing uploading my image and adding it to ECS of AWS.

I know, I was punished because I deserve that, but I would like to know: when this period ends? Can I cleanup my mess some way? The certificates are gone, with docker images (already read this was the wrong way to do this)

2 Likes

The next time this certificate can be issued is 19 Feb 2021 21:12:40 UTC.

That's 5-ish days from now.

You could evade the limit by including a subdomain:

-d meak-stories.com -d www.meak-stories.com

But remember to save the contents of /etc/letsencrypt this time!

4 Likes

WOW! Thanks for the quick answer!!!

I will add some lines to the script in a way that the certificate is safe and sound now.

1 Like

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